gcc ignores the __may_alias__ attribute on a struct typedef
This is gcc as of Mon Nov 19 21:35:13 2007 UTC.
There are numerous problems with forcing users to put
the attribute there. First of all, given the number of
people who put the attribute on the typedef, that is
clearly what people find to be natural. Second of all,
the struct definition may be coming from a header file
that the user does not control. Third of all, the need
for both aliasing and non-aliasing versions of a struct
creates data type incompatibilities if one can not
simply be a typedef that refers to the other.
See also: #28834, #29436, and the numerous duplicates
of both. (people REALLY expect this syntax to work)
--
Summary: gcc ignores the __may_alias__ attribute on a struct
typedef
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: acahalan at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34156
