This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c/34156] gcc ignores the __may_alias__ attribute on a struct typedef



------- Comment #2 from acahalan at gmail dot com  2007-11-20 05:35 -------
(In reply to comment #1)
> Please read the dicussion starting at:
> http://gcc.gnu.org/ml/gcc/2007-11/msg00213.html

Discussion noted.

It seems like the 100% workable solution is to let the C++ compiler factor
attributes into the name mangling scheme.

I can also imagine trying to hide the distinction, possibly maintaining it up
until the point at which the compiler generates output. This may even be what
users would most desire, assuming the C++ exception stuff can be made to work.

Making this C-only is another option, though a rather crummy one.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34156


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]