public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: binutils <binutils@sourceware.org>,
	Ralf Corsepius	<ralf.corsepius@rtems.org>
Subject: Re: Release 2.21 (ready ?)
Date: Fri, 19 Nov 2010 17:10:00 -0000	[thread overview]
Message-ID: <4CE6AF6F.6070305@oarcorp.com> (raw)
In-Reply-To: <B541D23F-CA95-4B9A-9DEA-DC8D7657CEC0@adacore.com>

On 11/19/2010 05:45 AM, Tristan Gingold wrote:
> Hi,
>
> I do not plan to make the release today, but it looks like I can now do it at anytime: nobody currently expect to backport a patch.
> If I am wrong, don't forget to tell me.
I tried to reply earlier from my phone but don't know if it got out.

We have a regression on arm-rtems ld which turned up when
Ralf built tool RPMs using 2.20.90.  I just prepared a reproducible
test case with objects.  The PR is:

http://sourceware.org/bugzilla/show_bug.cgi?id=12242

There is a link to a tarball with the objects, libraries, and
a "doit" script to reproduce the error just using arm-rtems-ld.

Thanks.
> Tristan.
>


-- 
Joel Sherrill, Ph.D.             Director of Research&  Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
    Support Available             (256) 722-9985


  parent reply	other threads:[~2010-11-19 17:10 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 11:45 Tristan Gingold
2010-11-19 16:11 ` Doug Kwan (關振德)
2010-11-20  0:02   ` Ian Lance Taylor
2010-11-19 17:10 ` Joel Sherrill [this message]
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
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=4CE6AF6F.6070305@oarcorp.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=binutils@sourceware.org \
    --cc=gingold@adacore.com \
    --cc=ralf.corsepius@rtems.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).