public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rbmj at verizon dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/55126] Libstdc++-v3 fails to compile Date: Tue, 30 Oct 2012 01:04:00 -0000 [thread overview] Message-ID: <bug-55126-4-JAWfu6NvId@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55126-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55126 --- Comment #2 from rbmj at verizon dot net 2012-10-30 01:04:08 UTC --- git bisect reports that commit that introduced the regression is svn: 192488 (or git: 584abc984ad...). I don't know enough about the codebase to easily tell where gcc is segfaulting, but hopefully somebody whose familiar with the internals can quickly see what happened.
next prev parent reply other threads:[~2012-10-30 1:04 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-29 20:13 [Bug libstdc++/55126] New: " rbmj at verizon dot net 2012-10-29 20:36 ` [Bug c++/55126] " redi at gcc dot gnu.org 2012-10-30 1:04 ` rbmj at verizon dot net [this message] 2012-10-30 1:15 ` [Bug target/55126] " d.g.gorbachev at gmail dot com 2012-10-30 1:59 ` rbmj at verizon dot net
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-55126-4-JAWfu6NvId@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).