public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dak at gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51333] cxxabi.h incompatible with -fkeep-inline-functions at link time Date: Mon, 28 Nov 2011 15:35:00 -0000 [thread overview] Message-ID: <bug-51333-4-N6yctdy250@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51333-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51333 David Kastrup <dak at gnu dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work|4.5.2 | --- Comment #2 from David Kastrup <dak at gnu dot org> 2011-11-28 15:25:03 UTC --- I am more surprised that actual demangling applications work without -lsupc++ as long as -fkeep-inline-functions is not used. It is good to have a solution (even if its necessity depends on the compilation options in a non-obvious way), but the actual error message certainly does not particularly help in figuring out the problem. I have to take back "works with 4.5.2" since I forgot that I used -fkeep-inline-functions only once I needed to work around a 4.6.1 bug. So I actually have no data point when this option would have worked with the given test file. Probably that renders this particular report "invalid", but somebody really should try making the link error message more intelligible.
next prev parent reply other threads:[~2011-11-28 15:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-28 14:11 [Bug c++/51333] New: " dak at gnu dot org 2011-11-28 14:53 ` [Bug c++/51333] " redi at gcc dot gnu.org 2011-11-28 15:35 ` dak at gnu dot org [this message] 2011-12-03 0:52 ` redi at gcc dot gnu.org 2015-09-25 20:10 ` joshb at cadence dot com
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-51333-4-N6yctdy250@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).