From: daniel.neri@sigicom.com (Daniel Néri)
To: ecos-patches@sources.redhat.com
Subject: Re: [PATCH] when building using binutils 2.20:
Date: Mon, 17 May 2010 07:23:00 -0000 [thread overview]
Message-ID: <87ljbjhu0a.fsf@quadra.hq.sigicom.net> (raw)
In-Reply-To: <4BEAA92D.70807@jifvik.org>
Jonathan Larmour <jifl@jifvik.org> writes:
> I'll let Nick handle this patch, but I'm curious (and admittedly
> haven't looked at the ISA details): it seems strange that msr psp,sp
> used to be allowed but now is not - and presumably it worked on the
> hardware otherwise it wouldn't have been in the port.
Over the weekend I tried to build a new ARM toolchain with binutils
2.20.1 and GCC 4.3.4, and it failed on code generated for ARMv7 by GCC
itself, with GAS complaining about the use of R13. Downgrading to
binutils 2.19.1 helped.
Regards,
Daniel
next prev parent reply other threads:[~2010-05-17 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 12:27 Spencer Oliver
2010-05-12 13:12 ` Jonathan Larmour
2010-05-17 7:23 ` Daniel Néri [this message]
2010-05-17 9:36 ` Spencer Oliver
2010-05-17 11:40 ` Nick Garnett
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=87ljbjhu0a.fsf@quadra.hq.sigicom.net \
--to=daniel.neri@sigicom.com \
--cc=ecos-patches@sources.redhat.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).