This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/23383] builtin array operator new is not marked with malloc attribute
- From: "xinliangli at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 4 Jun 2008 05:23:51 -0000
- Subject: [Bug c++/23383] builtin array operator new is not marked with malloc attribute
- References: <bug-23383-6528@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #10 from xinliangli at gmail dot com 2008-06-04 05:23 -------
(In reply to comment #9)
> This isn't possible. The user can override operator new at the very last
> minute: e.g. by interposing a shared object with LD_PRELOAD. There is no way
> that a compiler or even LTO optimizing linker can know about this. A special
> non-standard compiler flag is required.
>
Then runtime override would be illegal (in theory) (if builtin operator is
assumed), though the program may still run fine.
so LLVM's LTO completely gives up when seeing operator new or there is a
special flag?
David
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23383