From: Ian Lance Taylor <ian@cygnus.com>
To: joel@OARcorp.com
Cc: gas2@cygnus.com
Subject: Re: gas-971208 mips64orion-rtems internal error
Date: Mon, 22 Dec 1997 09:30:00 -0000 [thread overview]
Message-ID: <199712221730.MAA21675@subrogation.cygnus.com> (raw)
In-Reply-To: <Pine.BSF.3.96.971222112434.23375I-100000@vespucci.advicom.net>
Date: Mon, 22 Dec 1997 11:27:44 -0600 (CST)
From: Joel Sherrill <joel@OARcorp.com>
Should I just report this to the egcs list then along with the original
offensive C program
Yeah, I guess so.
Is there something I can do to help make this one
easier to find? It seems pretty weird.
It's probably pretty easy to fix. There's probably just a missing
TARGET_DOUBLE_FLOAT somewhere in mips.md or mips.c.
The 4650 is not a particularly common chip, so it's quite plausible
that changes to the MIPS code have introduced bugs in the 4650
support.
It's also possible that my analysis is wrong, although it seems right
to me.
Ian
prev parent reply other threads:[~1997-12-22 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-20 11:00 Joel Sherrill
1997-12-22 9:19 ` Ian Lance Taylor
1997-12-22 9:27 ` Joel Sherrill
1997-12-22 9:30 ` Ian Lance Taylor [this message]
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=199712221730.MAA21675@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=gas2@cygnus.com \
--cc=joel@OARcorp.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).