This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/47357] volatile member function is not treated as volatile
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 19 Jan 2011 10:44:56 +0000
- Subject: [Bug c++/47357] volatile member function is not treated as volatile
- Auto-submitted: auto-generated
- References: <bug-47357-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47357
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-01-19 10:44:54 UTC ---
I can't see anything in the program that would be affected by a 'volatile'
keyword. Instead I see a lot of bogus ways to try to circumvent type-based
aliasing rules (using volatile is one). Use -fno-strict-aliasing.