public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Philip Blundell <philb@gnu.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: bootstrap/3147: arm-elf and arm-rtems unbuildable on 3.0 branch
Date: Wed, 13 Jun 2001 00:36:00 -0000 [thread overview]
Message-ID: <20010613073601.21351.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR bootstrap/3147; it has been noted by GNATS.
From: Philip Blundell <philb@gnu.org>
To: joel@OARcorp.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/3147: arm-elf and arm-rtems unbuildable on 3.0 branch
Date: Wed, 13 Jun 2001 08:31:10 +0100
--==_Exmh_104880588P
Content-Type: text/plain; charset=us-ascii
>/tmp/ccNuRMlh.s:31: Error: bad instruction `adds r4,lr,r4'
>/tmp/ccNuRMlh.s:32: Error: bad instruction `addcs r7,r7,#65536'
Strange - you seem to be getting ARM code despite the `-mthumb' option. I'll
investigate this later today if nobody beats me to it.
>Unknown. I suspect that using binutils 2.11 rather than 2.10
>might get around this. But generally binutils 2.11 is broken
>on other platforms that have RTEMS targets so it is not in use
>yet.
Please try the binutils-2.11.1pre1 archive I made the other day and see if
that fixes your problems with 2.11.
p.
--==_Exmh_104880588P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999 (debian)
iD8DBQE7Jxa+VTLPJe9CT30RAhCXAKCwzYfcHwLdfBni/7mXbPuBRQxRswCggiZ9
V+9loSKSlAJ0Hx6Ew6O2Apc=
=7dRc
-----END PGP SIGNATURE-----
--==_Exmh_104880588P--
next reply other threads:[~2001-06-13 0:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 0:36 Philip Blundell [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-06 11:09 neil
2001-06-13 12:06 Philip Blundell
2001-06-13 11:56 Joel Sherrill
2001-06-13 11:46 Philip Blundell
2001-06-13 4:46 Richard Earnshaw
2001-06-12 14:56 joel
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=20010613073601.21351.qmail@sourceware.cygnus.com \
--to=philb@gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.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).