https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98884
--- Comment #5 from David Brown <david at westcontrol dot com> --- (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 in some ABIs one could get away with just pretending the stack > slots (or registers) are there even when they aren't actually allocated on > the stack, but one would need to have guarantees the callee e.g. will never > modify those stack slots (in most ABIs the call argument stack slot are > owned by the callee). Good point. I tried with: void needs_tags(int x, Tag1 t1, Tag2 t2, Tag3 t3, Tag4 t4, Tag5 t5, int y); and needs_tags(12345, t1, t2, t3, t4, t5, 200); gcc (trunk - gcc 11) on x86 puts 12345 in edi and 200 in esi, just as if the empty tags didn't exist. So does clang for the ARM (putting them in r0 and r1 respectively). gcc 9 for the ARM generates code as though t1 .. t5 were type "int" and value 0.
