From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: binutils@sources.redhat.com, gcc@gcc.gnu.org
Subject: bug in a29k-coff
Date: Thu, 21 Sep 2000 14:46:00 -0000 [thread overview]
Message-ID: <39CA8090.E9138ABD@OARcorp.com> (raw)
CC: gcc 2.95.2
BINUTILS: binutils 2.10
TARGET: a29k-rtems (basically a29k-coff)
I don't know if anyone cares about this or not. We have an old
a29k port of RTEMS and I was (perhaps foolishly) trying to build
a29k tools to see how badly it was bit-rotted. When building C++,
it blew up on this gcc invocation:
/usr1/rtems/work-tools/tools/b-a29k-gcc/gcc/xgcc \
-B/usr1/rtems/work-tools/tools/b-a29k-gcc/gcc/ \
-B/opt/a29k-rtems/a29k-rtems/bin/ \
-I/opt/a29k-rtems/a29k-rtems/include -O2 \
-I../../gcc-2.95.2/gcc/../newlib/libc/sys/rtems/include
-DCROSS_COMPILE \
-DIN_GCC -O2 -I./include -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 \
-D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -O2 -I. \
-I../../gcc-2.95.2/gcc -I../../gcc-2.95.2/gcc/config \
-I../../gcc-2.95.2/gcc/../include -c \
../../gcc-2.95.2/gcc/cp/new1.cc -DL_op_new
Tracking it down, I cut new1.s down to this and it still failed.
==================
.text
store 0,0,AI0,gr116
==================
sh$ a29k-rtems-as new1.s
new1.s: Assembler messages:
new1.s:2: Error: Invalid operands
==================
I don't know whether that is valid assembly language or not for the
a29k so I can't blame it on gcc or binutils.
Thanks.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next reply other threads:[~2000-09-21 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-21 14:46 Joel Sherrill [this message]
2000-09-21 17:12 Richard Kenner
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=39CA8090.E9138ABD@OARcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@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).