From: Michael Hope <michael.hope@linaro.org>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org
Subject: Re: [PATCH] Added binutils 2.21.53
Date: Thu, 29 Sep 2011 01:54:00 -0000 [thread overview]
Message-ID: <CANLjY-=RVw=ZWh3ArLsVFcf9qfN0ox6hyEg4QUpRr89_157P1Q@mail.gmail.com> (raw)
In-Reply-To: <201109290123.43533.yann.morin.1998@anciens.enib.fr>
On Thu, Sep 29, 2011 at 12:23 PM, Yann E. MORIN
<yann.morin.1998@anciens.enib.fr> wrote:
> Michael, All,
>
> On Wednesday 28 September 2011 09:00:45 Michael Hope wrote:
>> # HG changeset patch
>> # User Michael Hope <michael.hope@linaro.org>
>> # Date 1317176951 -46800
>> # Node ID 8787c0fd1b726a336314e3a29db4ebe9ef73c8ad
>> # Parent e198132ce41a142d6a05df3906814116a5c904bb
>> Added binutils 2.21.53.
>
> I also rewrote the desc-line (as per the as-yet-undocumented nomenclature!)
> to:
> binutils/binutils: added 2.21.53 snapshot
>
>> binutils 2.21 doesn't recognise the Cortex-M3 SVC instruction when
>> assembling with -mcpu=all. This was fixed by the 2.21.53 snapshot and
>> is needed to build RTOSs such as FreeRTOS.
>
> I'm _usually_ a bit reluctant to adding snapshots, even behind EXPERIMENTAL.
> Do you have an idea on the time-frame for binutils 2.22 (or whatever it's
> gonna be numbered) ?
I'm afraid I don't know when 2.22 will be out. binutils is
interesting as the snapshots are very stable - stable enough that
Ubuntu 11.10, Debian unstable, and Fedora 16 all use the 2.21.53
snapshot.
> The reason I do not really like snapshots is that I would like crosstool-NG
> to be as production-ready as possible. And snapshots are not really
> production-ready, I think.
>
> Of course, there are some places (eg. uClibc) where snapshots are available
> to use. uClibc is a different player, as the releases are quite spaced in
> time that using a snapshot can be usefull.
>
> Don't get me wrong. I like it that new features get added to crosstool-NG!
> I'm just not confident with maintaining unstable stuff. You know, that
> 24h-in-a-day limitation... ;-)
No worries. I'll keep it as a local patch and update when 2.22 comes out.
-- Michael
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-09-29 1:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 7:01 Michael Hope
2011-09-28 23:24 ` Yann E. MORIN
2011-09-29 1:54 ` Michael Hope [this message]
2011-10-05 21:57 ` Yann E. MORIN
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='CANLjY-=RVw=ZWh3ArLsVFcf9qfN0ox6hyEg4QUpRr89_157P1Q@mail.gmail.com' \
--to=michael.hope@linaro.org \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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).