public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@OARcorp.com> 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 11:56:00 -0000 [thread overview] Message-ID: <20010613185610.31799.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR bootstrap/3147; it has been noted by GNATS. From: Joel Sherrill <joel.sherrill@OARcorp.com> To: Philip Blundell <philb@gnu.org> 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 13:51:53 -0500 Philip Blundell wrote: > > >gc > >c/libgcc2.c -o libgcc/thumb/_muldi3.o > >/tmp/ccNuRMlh.s: Assembler messages: > >/tmp/ccNuRMlh.s:23: Error: Garbage following instruction > >/tmp/ccNuRMlh.s:24: Error: Garbage following instruction > >/tmp/ccNuRMlh.s:25: Error: dest and source1 one must be the same register > > I can't reproduce this. A build with --target=arm-elf worked fine on my > machine. I'm using some old snapshot from the binutils mainline (it calls > itself 2.10.91) but I don't think that should make any difference. > I received a patch from Richard Henderson which is now included in the mainline gcc to fix this. It is hard to know which side to blame when gcc and gas don't like each other. :) > p. > > ------------------------------------------------------------------------------- > Part 1.2Type: application/pgp-signature
next reply other threads:[~2001-06-13 11:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-13 11:56 Joel Sherrill [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:46 Philip Blundell 2001-06-13 4:46 Richard Earnshaw 2001-06-13 0:36 Philip Blundell 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=20010613185610.31799.qmail@sourceware.cygnus.com \ --to=joel.sherrill@oarcorp.com \ --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: linkBe 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).