https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98884
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98884
--- Comment #7 from Jakub Jelinek ---
x86-64 is handled correctly according to the psABI, see
https://gitlab.com/x86-psABIs/x86-64-ABI/-/blob/master/x86-64-ABI/low-level-sys-info.tex
The empty classes will end up with NO_CLASS and thus aren't pas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98884
--- Comment #6 from David Brown ---
(In reply to Jakub Jelinek from comment #3)
> If GCC and Clang are ABI incompatible on this, then one of the two compilers
> is buggy. So, it is needed to look at the EABI and find out which case it
> is.
I'v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98884
--- Comment #5 from David Brown ---
(In reply to Jakub Jelinek from comment #4)
> Note, for ABI compatibility or incompatibility it might be better to check
> what happens when some argument is passed after the empty structs. Because
> at least
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98884
--- Comment #4 from Jakub Jelinek ---
Note, for ABI compatibility or incompatibility it might be better to check what
happens when some argument is passed after the empty structs. Because at least
in some ABIs one could get away with just preten
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98884
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98884
--- Comment #2 from David Brown ---
Yes, ABI issues were my initial thought too. If so, then optimising away the
assignments while leaving the stack manipulation (and possibly register
allocations) in place would still be a significant improveme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98884
Richard Biener changed:
What|Removed |Added
Version|unknown |11.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98884
Jonathan Wakely changed:
What|Removed |Added
Component|c++ |target
Target|
