public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia.nrc.ca" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/47287] FAIL: gcc.c-torture/execute/builtins/20010124-1.c execution with -flto Date: Mon, 17 Jan 2011 15:49:00 -0000 [thread overview] Message-ID: <bug-47287-4-SPo8WcOk2L@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47287-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47287 --- Comment #4 from dave at hiauly1 dot hia.nrc.ca 2011-01-17 15:12:38 UTC --- > I suppose you are using GNU ld, right? Yes (gold has not been ported). > On trunk x86_64 with stock binutils 2.21 I get > > > cat 20010124-1.res > 3 > 20010124-1.o 3 > 79 2651d4ed PREVAILING_DEF_IRONLY main_test > 85 2651d4ed RESOLVED_IR g > 110 2651d4ed RESOLVED_IR f > 20010124-1-lib.o 3 > 113 f6a75653 PREVAILING_DEF_IRONLY f > 127 f6a75653 PREVAILING_DEF_IRONLY g > 153 f6a75653 RESOLVED_IR inside_main > main.o 3 > 79 2cccb08f PREVAILING_DEF main > 85 2cccb08f RESOLVED_IR main_test > 88 2cccb08f PREVAILING_DEF_IRONLY inside_main > > thus, memcpy is also missing but at least main_test is correctly > used from 20010124-1.o. > > Thus - can you tell us your exact GNU ld version and maybe debug > what is the lto_symtab contents we generate (there is a lto-plugin/lto-symtab.c > program, not sure if it still works ...) It has been rebuilt a number of times recently. Last night's test run still shows the bug and it used: dave@gsyprf11:~/gcc-4.6/objdir$ ld --version GNU ld (GNU Binutils) 2.21.51.20110116 I tried to do a build without plugin support, but it seems there is a ld configure bug and plugin support can't be disabled. With older versions, I think plugin support had to be explicitly enabled (default was no). I'll try to debug the lto_symtab contents tonight. Dave
next prev parent reply other threads:[~2011-01-17 15:12 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-14 7:19 [Bug lto/47287] New: " danglin at gcc dot gnu.org 2011-01-16 1:40 ` [Bug lto/47287] " danglin at gcc dot gnu.org 2011-01-16 2:17 ` danglin at gcc dot gnu.org 2011-01-17 13:53 ` rguenth at gcc dot gnu.org 2011-01-17 15:49 ` dave at hiauly1 dot hia.nrc.ca [this message] 2011-01-17 16:15 ` hubicka at gcc dot gnu.org 2011-01-17 16:15 ` hubicka at ucw dot cz 2011-01-17 18:05 ` danglin at gcc dot gnu.org 2011-01-18 7:11 ` dave at hiauly1 dot hia.nrc.ca 2011-01-18 7:45 ` dave at hiauly1 dot hia.nrc.ca 2011-02-01 21:05 ` davek 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-47287-4-SPo8WcOk2L@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).