[Bug target/120326] problems with attribute __ms_struct__

2025-05-19 Thread uecker at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120326

--- Comment #3 from uecker at gcc dot gnu.org ---
Those should not get the same TYPE_CANONICAL. tagged_types_tu_compatible_p
should be changed to detect this case which is due to different packing of bit
fields. It works correctly for this:

struct {
  unsigned char a;
  unsigned char b;
  unsigned long c;
} a;
struct {
  unsigned char a;
  unsigned char b;
  unsigned long c;
} __attribute__((packed)) b;

[Bug target/120326] problems with attribute __ms_struct__

2025-05-19 Thread jsm28 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120326

Joseph S. Myers  changed:

   What|Removed |Added

   Last reconfirmed||2025-05-19
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
 CC||uecker at gcc dot gnu.org

--- Comment #2 from Joseph S. Myers  ---
These two structs have no tags; it should be fine to have both of them in the
same translation unit, structs without tags need have no relation to one
another. Rejection should only be if they were given the same tag.

[Bug target/120326] problems with attribute __ms_struct__

2025-05-17 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120326

Andrew Pinski  changed:

   What|Removed |Added

   Keywords||ice-on-invalid-code

--- Comment #1 from Andrew Pinski  ---
This should be rejected as the ms struct is not on the first tag.