public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "davek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/46319] LTO plugin test failures with --with-build-config=bootstrap-lto --with-plugin-ld=ld Date: Fri, 05 Nov 2010 22:59:00 -0000 [thread overview] Message-ID: <bug-46319-4-BGyNUW68BV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46319-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46319 --- Comment #3 from Dave Korn <davek at gcc dot gnu.org> 2010-11-05 22:59:04 UTC --- When I tried running these tests in a pre-existing build tree, plugin_default_version_check failed because the datestamps don't match up: (gdb) p gcc_version[0] $5 = {basever = 0x1029fe8 "4.6.0", datestamp = 0x1029fee "20101103", devphase = 0x1029ff7 "experimental", revision = 0x1143f30 "", configuration_arguments = 0xd2d2c0 "/n/10/davek/gcc/gcc/configure --prefix=/n/ 10/davek/gcc --with-mpfr=/opt/cfarm/mpfr-2.4.1 --with-gmp=/opt/cfarm/gmp-4.2.4 - -with-mpc=/opt/cfarm/mpc-0.8 --with-libelf=/n/10/davek/usr --enable-bootstrap ". ..} (gdb) p plugin_version[0] $6 = {basever = 0x7ffff7567d29 "4.6.0", datestamp = 0x7ffff7567d2f "20101105", devphase = 0x7ffff7567d38 "experimental", revision = 0x7ffff7567e28 "", configuration_arguments = 0x7ffff7566720 "/n/10/davek/gcc/gcc/configure --pref ix=/n/10/davek/gcc --with-mpfr=/opt/cfarm/mpfr-2.4.1 --with-gmp=/opt/cfarm/gmp-4 .2.4 --with-mpc=/opt/cfarm/mpc-0.8 --with-libelf=/n/10/davek/usr --enable-bootst rap "...} (gdb) This will happen if $objdir/gcc/plugin-version.h or $objdir/gcc/configargs.h has been regenerated for any reason in between building the compiler and running the test. Can you tell if this may have happened in your case?
next prev parent reply other threads:[~2010-11-05 22:59 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-05 17:10 [Bug lto/46319] New: LTO plugin test failures with --wi th-plugin-ld=ld hjl.tools at gmail dot com 2010-11-05 17:27 ` [Bug lto/46319] LTO plugin test failures with --with-build-config=bootstrap-lto --with-plugin-ld=ld hjl.tools at gmail dot com 2010-11-05 17:44 ` davek at gcc dot gnu.org 2010-11-05 22:59 ` davek at gcc dot gnu.org [this message] 2010-11-05 23:28 ` hjl.tools at gmail dot com 2010-11-05 23:30 ` hjl.tools at gmail dot com 2010-11-05 23:31 ` hjl.tools at gmail dot com 2010-11-05 23:33 ` davek at gcc dot gnu.org 2010-11-08 4:53 ` davek at gcc dot gnu.org 2010-11-08 6:27 ` davek at gcc dot gnu.org 2010-11-09 19:32 ` davek at gcc dot gnu.org 2010-11-10 18:01 ` hjl.tools at gmail dot com 2010-11-10 22:53 ` davek at gcc dot gnu.org 2010-11-11 1:47 ` hjl.tools at gmail dot com
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-46319-4-BGyNUW68BV@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).