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: 30 Aug 2003 21:37:37 -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
yuri at tsoft dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
------- Additional Comments From yuri at tsoft dot com 2003-08-30 21:37 -------
Since I can not reopen similar to this Bug #11915 which was closed I
reopen this one:
I still think this is bug in GCC even considering aliasing rules.
Grounds:
* in "operator new" object is not created yet so aliasing rules no not apply.
NOTE1: aliasing rules begin to apply the moment after the operator new() exits
NOTE2: also if to treat memory area returned as an object and apply
operator new any "light memory allocating" there will become impossible,
which undermines the meaningfullness of operator new overloading.
Yuri