public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel@OARcorp.com>
To: gas2@cygnus.com
Subject: joel's tc-mips.c patch :(
Date: Wed, 11 Mar 1998 07:06:00 -0000	[thread overview]
Message-ID: <Pine.BSF.3.96.980311075416.28051C-100000@vespucci.advicom.net> (raw)

Well it must not be right.  It did not complete the multilib build.  I had
ben using the gas-971208 snapshot internally and compared the tc-mips.c
file against the version in that snapshot.  It appears that a chunk of
code disappeared.  A new version of the patch is below my signature which
should give a hint as to what got accidentally deleted.  It is still not
right though but it gets farther.  

Here is where it got to.

  /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/cca15880.s: Assembler messages:
/tmp/cca15880.s:439: Internal error!
Assertion failure in macro_build at ../../src/gas/config/tc-mips.c line
2351.

Suggestions appreciated.  I really do not know enough about the mips to
fix this one right.

--joel

*** tc-mips.c.orig      Tue Mar 10 03:20:11 1998
--- tc-mips.c   Wed Mar 11 07:51:26 1998
***************
*** 884,890 ****
--- 884,920 ----
                 || mips_cpu == 4100
                 || mips_cpu == 4400
                 || mips_cpu == 4300
+                || mips_cpu == 4600
+                || mips_cpu == 4650)

+         mips_opts.isa = 3;
+
+       else if (mips_cpu == 5000
+                || mips_cpu == 8000
+                || mips_cpu == 10000)
+         mips_opts.isa = 4;
+
+       else
+         mips_opts.isa = 1;
+
+     }
+
+ if (mips_opts.mips16 < 0)
+     {
+       if (strncmp (TARGET_CPU, "mips16", sizeof "mips16" - 1) == 0)
+         mips_opts.mips16 = 1;
+       else
+         mips_opts.mips16 = 0;
+     }
+
+   if (mips_4650 < 0)
+     mips_4650 = (mips_cpu == 4650);
+
+   if (mips_4010 < 0)
+     mips_4010 = (mips_cpu == 4010);
+
+   if (mips_4100 < 0)
+     mips_4100 = (mips_cpu == 4100);

    if (mips_3900 < 0)
      mips_3900 = (mips_cpu == 3900);






                 reply	other threads:[~1998-03-11  7:06 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.980311075416.28051C-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).