http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39753
Richard Guenther changed:
What|Removed |Added
Target Milestone|4.3.6 |4.4.7
--- Comment #16 from Richard Gue
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39753
m...@gcc.gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #15 from mrs at gc
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39753
Jack Howarth changed:
What|Removed |Added
CC||howarth at nitro dot
|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39753
--- Comment #13 from John Engelhart
2011-03-19 04:06:28 UTC ---
I'm the original reporter.
At this point, I no longer have any specific examples that demonstrate this
problem (this was filed quite some time ago).
m...@gcc.gnu.org:
> So, I'm so
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39753
--- Comment #12 from Mike Stump 2011-03-19
03:58:25 UTC ---
Any warnings generated that are invalid are bugs. These bugs should be filed,
and we'll fix them. Please attach an example file that generate warnings.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39753
--- Comment #11 from Nicola Pero 2011-03-19
01:24:47 UTC ---
Having looked at some of the warnings generated in GNUstep if you compile
with -fstrict-aliasing, they seem to be C warnings with little relevance
to Objective-C (they mostly seem to be
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39753
Nicola Pero changed:
What|Removed |Added
Status|WAITING |NEW
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39753
m...@gcc.gnu.org changed:
What|Removed |Added
Keywords|alias, wrong-code |
Status|NEW
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39753
--- Comment #8 from Richard Guenther 2011-03-15
11:49:12 UTC ---
The easiest way is to attach the may_alias attribute to all object types that
should not be subject to TBAA. Bonus point if you transition that attribute
to use a flag instead.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39753
Iain Sandoe changed:
What|Removed |Added
CC||mrs at gcc dot gnu.org
Known to fail|
10 matches
Mail list logo
