public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/52128] [4.7 regression] r183788 caused massive libstdc++ testsuite regression on i686-linux Date: Mon, 06 Feb 2012 16:04:00 -0000 [thread overview] Message-ID: <bug-52128-4-fpfnJNZ7gt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52128-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52128 --- Comment #6 from Mikael Pettersson <mikpe at it dot uu.se> 2012-02-06 16:03:09 UTC --- (In reply to comment #3) > Created attachment 26579 [details] > does this patch fix it? It does, thanks. > What configure command are you running? /tmp/gcc-4.7-20120204/configure --prefix=/tmp/install47 --with-gmp=/home/mikpe/pkgs/linux-x86/gmp-5.0.2 --with-mpfr=/home/mikpe/pkgs/linux-x86/mpfr-3.1.0 --with-mpc=/home/mikpe/pkgs/linux-x86/mpc-0.9 --disable-build-poststage1-with-cxx --disable-libquadmath --disable-plugin --disable-lto --disable-nls --disable-shared --disable-libmudflap --disable-libgomp --enable-threads=posix --enable-checking=release --enable-languages=c,c++ > Have you tried a clean build in an empty objdir? I always build gcc in an empty objdir. > what version of binutils are you using? binutils-2.20.51.0.7-8.fc14.i686 Fedora 14 user-space, but with a gcc-4.5.3 host compiler and a linux-3.2 kernel.
next prev parent reply other threads:[~2012-02-06 16:04 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-06 0:07 [Bug libstdc++/52128] New: " mikpe at it dot uu.se 2012-02-06 0:11 ` [Bug libstdc++/52128] " redi at gcc dot gnu.org 2012-02-06 8:53 ` redi at gcc dot gnu.org 2012-02-06 9:32 ` redi at gcc dot gnu.org 2012-02-06 9:44 ` redi at gcc dot gnu.org 2012-02-06 12:41 ` mario-baumann at web dot de 2012-02-06 12:47 ` redi at gcc dot gnu.org 2012-02-06 16:04 ` mikpe at it dot uu.se [this message] 2012-02-06 20:52 ` redi at gcc dot gnu.org 2012-02-06 21:25 ` 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-52128-4-fpfnJNZ7gt@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).