This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: aliasing warnings [patch]
- To: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: aliasing warnings [patch]
- From: David Edelsohn <dje at watson dot ibm dot com>
- Date: Thu, 16 Sep 1999 13:17:24 -0400
- Cc: zack at bitmover dot com, egcs at egcs dot cygnus dot com, egcs-patches at egcs dot cygnus dot com
>>>>> Mark Mitchell writes:
Mark> I don't think this warning should be on by default; it's going to
Mark> generate a ton of false positives. Probably many more than the RMS
Mark> proposal would. And, I don't see how to get line-number information
Mark> for the RMS proposal. I do think this warning might help interested
Mark> parties track down problems in their software, and thereby help to
Mark> avoid getting bitten by -fstrict-aliasing.
Great work, Zack!
Is RMS's proposal more accurate about warning in function which
are dereferencing a pointer incorrectly, as opposed to assigning pointers?
Maybe we really want both warnings enabled together: one to highlight the
questionable lines and the other to say that the function containing those
lines may be dereferencing the pointer incorrectly so the user should
examine warnings in that function more carefully.
David