public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "z0sh at sogetthis dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/50594] Option -fwhole-program discards replaced new operator for std::string Date: Mon, 03 Oct 2011 16:12:00 -0000 [thread overview] Message-ID: <bug-50594-4-hRCY6pMMDX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50594-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50594 --- Comment #13 from Kerrek SB <z0sh at sogetthis dot com> 2011-10-03 16:12:28 UTC --- Very interesting. I understand that making the function static makes the program ill-formed, but it's still somewhat surprising that a compiler flag should turn a perfectly valid program into an invalid one. Perhaps adding those visibility specifiers to the <new> header would be a good idea, since it'd be a pure-library solution. Thanks in any case for clarifying this!
next prev parent reply other threads:[~2011-10-03 16:12 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-02 22:54 [Bug c++/50594] New: " z0sh at sogetthis dot com 2011-10-02 23:03 ` [Bug c++/50594] " pinskia at gcc dot gnu.org 2011-10-02 23:08 ` paolo.carlini at oracle dot com 2011-10-02 23:33 ` z0sh at sogetthis dot com 2011-10-02 23:41 ` paolo.carlini at oracle dot com 2011-10-03 13:18 ` daniel.kruegler at googlemail dot com 2011-10-03 13:23 ` paolo.carlini at oracle dot com 2011-10-03 13:42 ` redi at gcc dot gnu.org 2011-10-03 13:44 ` redi at gcc dot gnu.org 2011-10-03 13:46 ` paolo.carlini at oracle dot com 2011-10-03 13:49 ` daniel.kruegler at googlemail dot com 2011-10-03 15:04 ` redi at gcc dot gnu.org 2011-10-03 15:13 ` paolo.carlini at oracle dot com 2011-10-03 16:12 ` z0sh at sogetthis dot com [this message] 2011-10-04 9:27 ` rguenth at gcc dot gnu.org 2011-10-04 9:37 ` paolo.carlini at oracle dot com 2011-10-04 9:55 ` redi at gcc dot gnu.org 2011-10-04 10:06 ` rguenther at suse dot de 2011-10-04 10:12 ` redi at gcc dot gnu.org 2011-10-04 12:00 ` z0sh at sogetthis dot com 2011-10-04 18:38 ` jason at gcc dot gnu.org 2011-10-11 23:30 ` paolo.carlini at oracle dot com 2011-10-11 23:40 ` paolo.carlini at oracle dot com 2011-10-12 18:41 ` paolo at gcc dot gnu.org 2011-10-12 18:43 ` paolo.carlini at oracle dot com 2012-03-12 16:32 ` fang at csl dot cornell.edu
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-50594-4-hRCY6pMMDX@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).