From: Joel Sherrill <joel@OARcorp.com>
To: gas2@cygnus.com
Subject: gas-980313 mips64orion problems
Date: Fri, 13 Mar 1998 12:26:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.980313142219.14349J-100000@vespucci.advicom.net> (raw)
The same mips64orion problem which existed in gas-980310 still
exists in gas-980313.
If I am reading diffs-weekly-980310 correctly, then a chunk of
code in tc-mips.c was deleted. My guess is that the mips gas is broken on
just about every configuration right now.
I readded the code deleted by the change in diffs-weekly-980310 and
this allowed tc-mips.c to compile but later the build failed trying
to build egcs-1.0.2-980309-prerelease with the following:
/usr2/tools/build-mips64orion-tools/gcc/xgcc
-B/usr2/tools/build-mips64orion-tools/gcc/ -O2 -DCROSS_COMPILE -DIN_GCC
-O2 -I./include -G 0 -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
-fexceptions -Dinhibit_libc -I. -I../../src/gcc -I../../src/gcc/config
-c -DL${name} \
../../src/gcc/libgcc2.c -o ${name}.o; \
if [ $? -eq 0 ] ; then true; else exit 1; fi; \
/usr2/tools/build-mips64orion-tools/binutils/ar rc tmplibgcc2.a
${name}.o; \
rm -f ${name}.o; \
done
_muldi3
_divdi3
/tmp/cca01669.s: Assembler messages:
/tmp/cca01669.s:439: Internal error!
Assertion failure in macro_build at ../../src/gas/config/tc-mips.c line
2349.
Please report this bug.
--joel
next reply other threads:[~1998-03-13 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-13 12:26 Joel Sherrill [this message]
1998-03-13 15:34 ` Ken Raeburn
1998-03-14 7:50 ` Joel Sherrill
1998-03-14 13:16 ` Ken Raeburn
1998-03-16 5:37 ` Joel Sherrill
1998-03-14 8:09 ` H.J. Lu
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=Pine.BSF.3.96.980313142219.14349J-100000@vespucci.advicom.net \
--to=joel@oarcorp.com \
--cc=gas2@cygnus.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).