public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Rainer Orth <ro@techfak.uni-bielefeld.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: 4.3/4.4 PATCH: Fix Solaris/x86 bootstrap with Sun ld (PR bootstrap/33100)
Date: Wed, 05 Nov 2008 18:32:00 -0000	[thread overview]
Message-ID: <m3iqr2f2ip.fsf@google.com> (raw)
In-Reply-To: <18705.54181.858026.33670@manam.TechFak.Uni-Bielefeld.DE> (Rainer Orth's message of "Wed\, 5 Nov 2008 18\:11\:01 +0100 \(MET\)")

Rainer Orth <ro@techfak.uni-bielefeld.de> writes:

> As I suggested in the original patch submission, it should be possible to
> move the inclusion of i386/t-crtstuff to libgcc/configure.ac and make it
> conditional on a linker test there.  This way, only systems with broken Sun
> linkers would be penalized.  I could well try that approach, since it's
> certainly cleaner and doesn't break unwind information on recent Solaris 11
> where we don't have to.  What do you think?

I think it's up to you.  You can also just split the config.gcc test
on the solaris version number.


>> I'll approve this patch for mainline and 4.3 branch.
>
> What about the 4.2 branch?  As I mentioned, the patch is needed there, too,
> and I've successfully bootstrapped on i386-pc-solaris2.10.  Unfortunately,
> the cleaner approach outlined above isn't available here since there's no
> separate libgcc with it's own configure, so I fear it's either this hack or
> leave that branch broken.

OK for 4.2 branch also.

Ian

  reply	other threads:[~2008-11-05 18:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 14:53 Rainer Orth
2008-11-05 16:05 ` Ian Lance Taylor
2008-11-05 17:12   ` Rainer Orth
2008-11-05 18:32     ` Ian Lance Taylor [this message]
2008-11-06 12:45       ` Rainer Orth
2008-11-19 17:41       ` Rainer Orth
2008-11-19 19:27         ` Ian Lance Taylor

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=m3iqr2f2ip.fsf@google.com \
    --to=iant@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ro@techfak.uni-bielefeld.de \
    /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).