public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/61536] [4.10 regression] g++ and libstdc++ regressions on arm-none-linux-gnueabihf with missing typeinfo Date: Wed, 18 Jun 2014 06:33:00 -0000 [thread overview] Message-ID: <bug-61536-4-rBQcn5SHbs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61536-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61536 --- Comment #13 from Paolo Carlini <paolo.carlini at oracle dot com> --- Excellent, that version is very safe. Are you willing to commit it? Otherwise, I don't know when I can do it, maybe only Sunday. If you do that, you may want to also add, after the first comment: // By default follow the old inline rules to avoid ABI changes. something like: // (logic copied from libsupc++/typeinfo (libstdc++/61536)). otherwise the patch is ready to go in.
next prev parent reply other threads:[~2014-06-18 6:33 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-17 11:36 [Bug tree-optimization/61536] New: " ramana at gcc dot gnu.org 2014-06-17 11:38 ` [Bug tree-optimization/61536] " ramana at gcc dot gnu.org 2014-06-17 11:53 ` ramana at gcc dot gnu.org 2014-06-17 12:17 ` [Bug libstdc++/61536] " paolo.carlini at oracle dot com 2014-06-17 12:23 ` paolo.carlini at oracle dot com 2014-06-17 12:49 ` ramana at gcc dot gnu.org 2014-06-17 13:08 ` paolo.carlini at oracle dot com 2014-06-17 13:09 ` paolo.carlini at oracle dot com 2014-06-17 13:28 ` ramana at gcc dot gnu.org 2014-06-17 13:47 ` paolo.carlini at oracle dot com 2014-06-17 16:08 ` ramana at gcc dot gnu.org 2014-06-17 16:23 ` ramana at gcc dot gnu.org 2014-06-17 21:43 ` ramana at gcc dot gnu.org 2014-06-18 6:33 ` paolo.carlini at oracle dot com [this message] 2014-06-18 9:44 ` ramana at gcc dot gnu.org 2014-06-28 11:01 ` glisse at gcc dot gnu.org 2014-06-28 11:30 ` paolo.carlini at oracle dot com 2014-06-28 11:56 ` paolo.carlini at oracle dot com 2014-06-28 15:54 ` paolo 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-61536-4-rBQcn5SHbs@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).