public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stigge at antcom dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/57386] ICE: hash-long-double-tr1-aux.cc:54:7: error: unrecognizable insn Date: Fri, 24 May 2013 15:23:00 -0000 [thread overview] Message-ID: <bug-57386-4-aNKMM74fa5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57386-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57386 --- Comment #4 from Roland Stigge <stigge at antcom dot de> --- FWIW, I just tried with GCC 4.7.3, configured and built the same way, and it works. The files libstdc++-v3/src/c++98/hash_tr1.cc libstdc++-v3/src/c++98/hash-long-double-tr1-aux.cc haven't changed really.
next prev parent reply other threads:[~2013-05-24 15:23 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-23 13:24 [Bug libstdc++/57386] New: " stigge at antcom dot de 2013-05-23 14:25 ` [Bug libstdc++/57386] " rguenth at gcc dot gnu.org 2013-05-24 11:18 ` stigge at antcom dot de 2013-05-24 11:49 ` paolo.carlini at oracle dot com 2013-05-24 15:23 ` stigge at antcom dot de [this message] 2013-12-01 11:53 ` [Bug target/57386] " stigge at antcom dot de 2013-12-11 12:49 ` stigge at antcom dot de 2013-12-11 12:51 ` stigge at antcom dot de 2013-12-12 0:22 ` meissner at linux dot vnet.ibm.com 2013-12-12 17:10 ` meissner at linux dot vnet.ibm.com 2013-12-12 21:03 ` meissner at linux dot vnet.ibm.com 2013-12-12 21:03 ` meissner at linux dot vnet.ibm.com 2013-12-12 23:42 ` stigge at antcom dot de 2014-01-07 19:57 ` meissner at gcc dot gnu.org 2014-01-07 20:10 ` meissner 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-57386-4-aNKMM74fa5@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).