public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/64504] Invalid free() with _GLIBCXX_DEBUG and -fwhole-program Date: Mon, 26 Jan 2015 10:56:00 -0000 [thread overview] Message-ID: <bug-64504-4-SmzzRmMShd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64504-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64504 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu.org --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- Looks like _S_empty_rep_storage is tested like if (ptr != &_S_empty_rep_storage) in libstdc++ and thus having multiple _S_empty_rep_storage instantiations is going to break. Honza - how was -fwhole-program (and LTO?!) designed to deal with C++ ODR rules? With -fno-linker-plugin, that is? To others: -fwhole-program basically assumes that all defined symbols can be brought local to the unit (apart from main()). Seems like this includes instantiated templates which means that we assume there is only a single TU and thus ODR violations never arise from that.
next prev parent reply other threads:[~2015-01-26 10:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-05 19:46 [Bug libstdc++/64504] New: " andrey.vihrov at gmail dot com 2015-01-06 11:18 ` [Bug libstdc++/64504] " redi at gcc dot gnu.org 2015-01-06 14:08 ` andrey.vihrov at gmail dot com 2015-01-25 18:35 ` andrey.vihrov at gmail dot com 2015-01-26 10:56 ` rguenth at gcc dot gnu.org [this message] 2015-01-26 11:06 ` redi at gcc dot gnu.org 2015-06-09 15:12 ` andrey.vihrov at gmail dot com 2015-06-09 16:56 ` redi at gcc dot gnu.org
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-64504-4-SmzzRmMShd@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).