From: Joel Sherrill <joel@OARcorp.com>
To: gas2@cygnus.com
Subject: gas-980310: mips64orion-rtems failure
Date: Wed, 11 Mar 1998 05:53:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.980311074312.28051B-100000@vespucci.advicom.net> (raw)
It would not compile and failed with the following message:
gcc -DHAVE_CONFIG_H -I. -I../../src/gas -I. -D_GNU_SOURCE -I.
-I../../src/gas -I../bfd -I../../src/gas/config -I../../src/gas/../include
-I../../src/gas/.. -I../../src/gas/../bfd -O2 -c
../../src/gas/config/tc-mips.c
../../src/gas/config/tc-mips.c: In function `md_begin':
../../src/gas/config/tc-mips.c:889: parse error before `if'
../../src/gas/config/tc-mips.c:1114: parse error before `void'
I took a shot at patching this. This code is very different from what was
in 2.8.1. It now compiles but I have very little confidence that I got it
right. The code in question is setting the isa indicator. Anyway, the
patch is below my signature:
--joel
Joel Sherrill Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (205) 722-9985
Wed Mar 11 07:46:11 CST 1998 Joel Sherrill <joel@OARcorp.com>
* config/tc-mips.c: (md_begin): Added missing brace and
parenthesis so this would compile.
*** tc-mips.c.orig Tue Mar 10 03:20:11 1998
--- tc-mips.c Wed Mar 11 07:45:04 1998
***************
*** 883,890 ****
else if (mips_cpu == 4000
|| mips_cpu == 4100
|| mips_cpu == 4400
! || mips_cpu == 4300
if (mips_3900 < 0)
mips_3900 = (mips_cpu == 3900);
--- 883,892 ----
else if (mips_cpu == 4000
|| mips_cpu == 4100
|| mips_cpu == 4400
! || mips_cpu == 4300)
+ mips_opts.isa = 3;
+ }
if (mips_3900 < 0)
mips_3900 = (mips_cpu == 3900);
reply other threads:[~1998-03-11 5:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.980311074312.28051B-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).