From: Joel Sherrill <joel@OARcorp.com>
To: Ken Raeburn <raeburn@cygnus.com>
Cc: gas2@cygnus.com
Subject: Re: gas-980313 mips64orion problems
Date: Sat, 14 Mar 1998 07:50:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.980314094103.5560A-100000@vespucci.advicom.net> (raw)
In-Reply-To: <tx167liqi67.fsf@cygnus.com>
> because apparently a chunk of the opcode table was also removed
> incorrectly. (This and the tc-mips.c problem should be fixed in the
> next snapshot.) I'm using an alpha-linux host.
You seem to have fixed the problem. I am on a i686-pc-linux-gnu according
to config.guess (Redhat 5.0). I am using the following versions:
BINUTILS gas-980314
GCC egcs-1.0.2-980309-prerelease
NEWLIB newlib-1.8.0 + RTEMS patch
and building "one-tree" style. In this configuration, I managed to
successfully build a full egcs (including objc and fortran).
Yeah!!!
FYI I managed to build this toolset for every other RTEMS target
using the 980310 snapshot so things look pretty good. The RTEMS
targets are:
hppa1.1-rtems, i386-rtems, i386-go32-rtems, i960-rtems,
m68k-rtems, mips64orion-rtems, powerpc-rtems, sh-rtems,
sparc-rtems
So things look pretty good. How close does the 2.9 release look?
> 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.)
OK. I should have remembered the host system part. I did not sent
the .s along since it was obvious that code had been removed
accidentally. Normally I would have sent more along more information.
Thanks.
--joel
next prev parent reply other threads:[~1998-03-14 7:50 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 [this message]
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.980314094103.5560A-100000@vespucci.advicom.net \
--to=joel@oarcorp.com \
--cc=gas2@cygnus.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).