From: hjl@lucon.org (H.J. Lu)
To: raeburn@cygnus.com (Ken Raeburn)
Cc: joel@OARcorp.com, gas2@cygnus.com
Subject: Re: gas-980313 mips64orion problems
Date: Sat, 14 Mar 1998 08:09:00 -0000 [thread overview]
Message-ID: <m0yDtVK-00058JC@ocean.lucon.org> (raw)
In-Reply-To: <tx167liqi67.fsf@cygnus.com>
>
> If your problem persists with tonight's snapshot, please let me know.
> Also let me know what host platform and compiler you're using; the
> egcs (non-release) snapshots have recently had some problems with
> binutils, at least on my alpha. (Oh, and send the .s file if it's not
> too much trouble. I can try to re-create it, but I haven't been
> working much with the prerelease snapshots recently, so I may not have
> the sources handy.)
>
The last egcs snapshot has way too many problems on alpha. "make check"
went into infinite loops in so many places that I had to kill it.
--
H.J. Lu (hjl@gnu.org)
prev parent reply other threads:[~1998-03-14 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-13 12:26 Joel Sherrill
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 [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=m0yDtVK-00058JC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=gas2@cygnus.com \
--cc=joel@OARcorp.com \
--cc=raeburn@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).