public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "costamagnagianfranco at yahoo dot it" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/66262] New: [REGRESSION] testsuite failure with libstdc++ (gcc-5) and g++-4.9 together Date: Sat, 23 May 2015 10:08:00 -0000 [thread overview] Message-ID: <bug-66262-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66262 Bug ID: 66262 Summary: [REGRESSION] testsuite failure with libstdc++ (gcc-5) and g++-4.9 together Product: gcc Version: 5.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: costamagnagianfranco at yahoo dot it Target Milestone: --- Hi, sorry in advance for the low quality bug report. I'm reporting this upstream, since I suspect the ABI broke in some bad way between 4.9 and 5.0. note: I tried to explain as much as possible on Debian bug [1] Firstly I wasn't able to make it work with g++-5 and libstdc++ from gcc-5 package After the Debian Maintainer rebuilt gcc-5 with * Configure with --disable-libstdcxx-dual-abi --with-default-libstdcxx-abi=c++98 While libstdc++ provides a dual ABI to support both the c++98 and c++11 ABI, there is no committment on compatibility of the old experimental c++11 ABI from GCC 4.9 and the stable c++11 ABI in GCC 5. and now I can build them with both g++-5 and libstdc++ from gcc-5. the problem actually is that now Debian has libstdc++ from gcc-5, and the default compiler still set to gcc-4.9. With that combination (g++-4.9 and libstdc++ from gcc-5) the bug is there and I can't upload in Debian the new release until I figure this out. I can try to provide more informations, just feel free to ask me. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784655
next reply other threads:[~2015-05-23 10:08 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-23 10:08 costamagnagianfranco at yahoo dot it [this message] 2015-05-23 10:17 ` [Bug libstdc++/66262] " trippels at gcc dot gnu.org 2015-05-23 10:49 ` costamagnagianfranco at yahoo dot it 2015-05-23 10:59 ` trippels at gcc dot gnu.org 2015-05-26 13:44 ` trippels at gcc dot gnu.org 2015-05-26 13:57 ` costamagnagianfranco at yahoo dot it 2015-05-26 13:59 ` costamagnagianfranco at yahoo dot it 2015-06-01 9:51 ` costamagnagianfranco at yahoo dot it 2015-06-01 10:17 ` trippels at gcc dot gnu.org 2015-06-01 10:30 ` costamagnagianfranco at yahoo dot it 2015-06-01 10:40 ` trippels at gcc dot gnu.org 2015-06-01 11:32 ` doko at gcc dot gnu.org 2015-06-01 12:02 ` hjl.tools at gmail dot com 2015-06-01 12:13 ` redi at gcc dot gnu.org 2015-06-01 12:19 ` redi at gcc dot gnu.org 2015-06-01 12:21 ` redi at gcc dot gnu.org 2015-06-01 12:52 ` costamagnagianfranco at yahoo dot it 2015-06-06 12:17 ` 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-66262-4@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).