public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: binutils <binutils@sourceware.org>
Subject: Re: Release 2.21 - Pre tests
Date: Wed, 08 Dec 2010 15:55:00 -0000	[thread overview]
Message-ID: <mcrzksgl0o3.fsf@google.com> (raw)
In-Reply-To: <1ACEED66-DF20-4A9E-924D-3EA4217F332E@adacore.com> (Tristan	Gingold's message of "Wed, 8 Dec 2010 11:46:55 +0100")

Tristan Gingold <gingold@adacore.com> writes:

> On Dec 1, 2010, at 5:53 PM, Ian Lance Taylor wrote:
>
>> Tristan Gingold <gingold@adacore.com> writes:
>> 
>>> Not sure too.  Maybe we should document that gcc 4.1.3 is know to work
>>> too, while gcc 4.1.0 - 4.1.2 are known to fail.
>> 
>> I have committed this patch to mainline and 2.21 branch.
>
> BTW, is the web page still accurate:
>
>   * gold - A new, faster, ELF only linker, still in beta test.
>
> Ie, do you consider gold as 'still in beta test' ?

I don't really, but in the wider scheme of things gold is perhaps
reasonably described as in beta test until it is the standard linker for
at least one distro.  Also I would like to see the kernel developers
reliably test with gold, and of course the glibc build still does not
work with gold.  I don't really know what the web page should say.

Ian

  reply	other threads:[~2010-12-08 15:55 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 11:45 Release 2.21 (ready ?) Tristan Gingold
2010-11-19 16:11 ` Doug Kwan (關振德)
2010-11-20  0:02   ` Ian Lance Taylor
2010-11-19 17:10 ` Joel Sherrill
2010-11-23 16:32 ` Release 2.21 - Pre tests Tristan Gingold
2010-11-23 18:54   ` Matthias Klose
2010-11-24  9:28     ` Richard Sandiford
2010-11-24 14:40       ` Matthew Gretton-Dann
2010-11-25  1:40         ` Alan Modra
2010-11-25  9:49           ` Matthew Gretton-Dann
2010-11-25  9:55             ` Tristan Gingold
2010-11-25 15:16               ` Matthew Gretton-Dann
2010-11-23 21:04   ` Ian Lance Taylor
2010-11-23 21:17     ` H.J. Lu
2010-11-23 23:00       ` Ian Lance Taylor
2010-11-23 23:09         ` H.J. Lu
2010-11-24  8:23     ` Tristan Gingold
2010-12-01  0:21       ` Ian Lance Taylor
2010-12-01 11:03         ` Tristan Gingold
2010-12-01 16:53           ` Ian Lance Taylor
2010-12-08 10:47             ` Tristan Gingold
2010-12-08 15:55               ` Ian Lance Taylor [this message]
2010-12-08 16:02                 ` Tristan Gingold
2010-11-24  9:53   ` Matthew Gretton-Dann
2010-11-24  9:56     ` Tristan Gingold
2010-12-01 15:14   ` Release 2.21 - Soon Tristan Gingold
2010-12-01 15:18     ` H.J. Lu
2010-12-02 15:03       ` Tristan Gingold
2010-12-03 17:43     ` Steve Ellcey
2010-12-03 18:08       ` Maciej W. Rozycki
2010-12-03 18:26         ` Steve Ellcey
2010-12-04  0:44           ` Maciej W. Rozycki
2010-12-03 21:11         ` Steve Ellcey
2010-12-04  0:55           ` Maciej W. Rozycki
2010-12-06 10:46             ` Chris Smith
2010-12-06 14:02               ` Tristan Gingold
2010-12-06 16:36             ` Steve Ellcey
2010-12-06 17:35               ` Maciej W. Rozycki
2010-12-06 17:40     ` H.J. Lu
2010-12-07  8:24       ` Tristan Gingold

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=mcrzksgl0o3.fsf@google.com \
    --to=iant@google.com \
    --cc=binutils@sourceware.org \
    --cc=gingold@adacore.com \
    /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).