public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49463] [4.7 Regression] LTO doesn't work symbol renamed via asm statement
Date: Tue, 27 Sep 2011 17:18:00 -0000	[thread overview]
Message-ID: <bug-49463-4-MvfdkERakF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49463-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49463

Jan Hubicka <hubicka at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #14 from Jan Hubicka <hubicka at gcc dot gnu.org> 2011-09-27 16:42:57 UTC ---
It turns out that I forgot to commit the libstrstr patch and in meantime
configure script was modified so it no longer enabled -fuse-linker-plugin by
default.  Since I tend to always specify it by hand I did not noticed for quite
a while.

I suppose the problem is that I have plugin enabled LD in my install directory
while configure script is incorrectly querying the system wide LD?

Anyway testsuite should be clean with plugin now. Sorry for taking so long.


      parent reply	other threads:[~2011-09-27 16:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-18 12:48 [Bug middle-end/49463] New: [4.7 Regression] LTO testcase failures hjl.tools at gmail dot com
2011-06-18 14:19 ` [Bug middle-end/49463] " hjl.tools at gmail dot com
2011-06-20 10:24 ` rguenth at gcc dot gnu.org
2011-06-23 14:04 ` hjl.tools at gmail dot com
2011-06-23 16:41 ` [Bug middle-end/49463] [4.7 Regression] LTO doesn't work symbol renamed via asm statement hubicka at gcc dot gnu.org
2011-06-23 16:43 ` hjl.tools at gmail dot com
2011-06-23 16:48 ` hubicka at gcc dot gnu.org
2011-06-25 14:22 ` danglin at gcc dot gnu.org
2011-06-25 15:02 ` hubicka at gcc dot gnu.org
2011-07-09 12:24 ` danglin at gcc dot gnu.org
2011-08-02 14:27 ` rguenth at gcc dot gnu.org
2011-08-05 14:51 ` hubicka at ucw dot cz
2011-08-05 15:40 ` ubizjak at gmail dot com
2011-08-10 13:36 ` uweigand at gcc dot gnu.org
2011-09-27 16:43 ` hubicka at gcc dot gnu.org
2011-09-27 17:18 ` hubicka at gcc dot gnu.org [this message]

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-49463-4-MvfdkERakF@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: link
Be 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).