diff options
author | Luc Van Oostenryck <luc.vanoostenryck@gmail.com> | 2019-11-08 02:35:44 +0100 |
---|---|---|
committer | Luc Van Oostenryck <luc.vanoostenryck@gmail.com> | 2019-11-08 02:43:51 +0100 |
commit | 2ec21ceee59e08813403bd0425e493a31e750b00 (patch) | |
tree | 9f06044b072081fb1bbdc90dec815b9895992197 | |
parent | b31adacc241f5fb4b0421d6727f6dedb847fffd0 (diff) | |
download | sparse-2ec21ceee59e08813403bd0425e493a31e750b00.tar.gz |
cgcc: remove _STRING_ARCH_unaligned
As far as I can see, the macro '_STRING_ARCH_unaligned' may
be defined by glibc, not gcc. So, there is no reason for
cgcc to define it.
Worse, cgcc defines it to '1' while on some platorms (at least the
few ppc64 I've access to) the installed glibc defines it to '0'.
So, do not let cgcc define this macro.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
-rwxr-xr-x | cgcc | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -276,11 +276,11 @@ sub add_specs { return (' --arch=x86_64' . &float_types (1, 1, 33, [24,8], [53,11], [113,15])); } elsif ($spec eq 'ppc') { - return (' -D_BIG_ENDIAN -D_STRING_ARCH_unaligned=1' . + return (' -D_BIG_ENDIAN' . ' --arch=ppc' . &float_types (1, 1, 21, [24,8], [53,11], [113,15])); } elsif ($spec eq 'ppc64') { - return (' -D_STRING_ARCH_unaligned=1 ' . + return ( ' --arch=ppc64' . &float_types (1, 1, 21, [24,8], [53,11], [113,15])); } elsif ($spec eq 'ppc64+be') { |