public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Matt Hargett <matt@use.net>
Cc: "gcc-help\@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: bootstrap comparison failure with bootstrap-lto
Date: Mon, 21 Nov 2011 17:27:00 -0000	[thread overview]
Message-ID: <mcr1ut2hxty.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (raw)
In-Reply-To: <9A909B94-ADF4-4213-B862-5AEE2C19F715@use.net> (Matt Hargett's	message of "Sun, 20 Nov 2011 07:52:59 -0800")

Matt Hargett <matt@use.net> writes:

>> Looking at this, I think that this kind of test is going to fail when
>> using -flto and gold, because gold is going to report that the symbols
>> listed in the .ctors and .init_array sections are not visible from the
>> outside.  Unfortunately this is not simple to fix in gold.  In fact, I'm
>> not sure it's possible in the general case.
>
> Do we have enough info to file an actionable bug (or bugs)? if so, should I file it under the bootstrap component?

I filed http://gcc.gnu.org/PR51225 .

I'm testing a patch to add -fno-lto when running that test in the
configure script.

Ian

      reply	other threads:[~2011-11-21  5:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 22:23 Matt
2011-11-15  5:56 ` Ian Lance Taylor
2011-11-16 21:55   ` Matt
2011-11-17  5:43     ` Ian Lance Taylor
2011-11-18  6:35       ` Matt
2011-11-18 13:47         ` Ian Lance Taylor
2011-11-18 21:08           ` Matt
2011-11-19  1:11             ` Ian Lance Taylor
2011-11-19  2:41               ` Matt
2011-11-19 15:37                 ` Ian Lance Taylor
2011-11-20  6:51                   ` Matt
2011-11-20  7:32                     ` Ian Lance Taylor
2011-11-20 20:23                       ` Matt Hargett
2011-11-21 17:27                         ` Ian Lance Taylor [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=mcr1ut2hxty.fsf@dhcp-172-18-216-180.mtv.corp.google.com \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=matt@use.net \
    /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).