This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/11973] GCC 3.3 optimizer creates wrong code (i386/Linux)
- From: "yuri at tsoft dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 31 Aug 2003 02:04:44 -0000
- Subject: [Bug c++/11973] GCC 3.3 optimizer creates wrong code (i386/Linux)
- References: <20030818211447.11973.yuri@tsoft.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11973
------- Additional Comments From yuri at tsoft dot com 2003-08-31 02:04 -------
When "operator new" is called object is non-existent yet.
Aliasing rules talk about accessing two different types with one lvalue.
But in case of "operator new" the second one doesn't exist yet. Therefore
aliasing rules do not apply in this case. We return "void*" from operator new,
not object pointer.
If it was some other function (not operator new) I agree with you totally.
Yuri.