https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70066
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-*-*
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
@defmac BIGGEST_ALIGNMENT
Biggest alignment that any data type can require on this machine, in
bits. Note that this is not the biggest alignment that is supported,
just the biggest alignment that, when violated, may cause a fault.
@end defmac
@deftypevr {Target Hook} HOST_WIDE_INT TARGET_ABSOLUTE_BIGGEST_ALIGNMENT
If defined, this target hook specifies the absolute biggest alignment
that a type or variable can have on this machine, otherwise,
@code{BIGGEST_ALIGNMENT} is used.
@end deftypevr
....
#undef TARGET_ABSOLUTE_BIGGEST_ALIGNMENT
#define TARGET_ABSOLUTE_BIGGEST_ALIGNMENT 512
I suspect there is a target issue here or the front-end should be using
TARGET_ABSOLUTE_BIGGEST_ALIGNMENT instead. The back-end is confused about byte
vs bit here and even the comment before the definition of BIGGEST_ALIGNMENT is
incorrect.
