From: Jeffrey A Law <law@cygnus.com>
To: Richard Henderson <rth@cygnus.com>
Cc: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>,
wilson@cygnus.com, egcs@cygnus.com
Subject: Re: egcs-971105 config.guess and gcc/config.guess have diverged
Date: Thu, 13 Nov 1997 11:19:00 -0000 [thread overview]
Message-ID: <2667.879448175@hurl.cygnus.com> (raw)
In-Reply-To: <19971112150154.29821@dot.cygnus.com>
In message < 19971112150154.29821@dot.cygnus.com >you write:
> On Wed, Nov 12, 1997 at 04:48:23PM -0500, Kaveh R. Ghazi wrote:
> > I don't think the problem is, as you imply above, that support
> > is missing. The issue is that ev5* support is there and broken. At
> > least I couldn't bootstrap my ev5 with egcs out of the box.
>
> It's not ev5 thats the problem but ev56 (since it is ev5's that I have),
> almost certainly caused by the relatively untested byte-word extension.
>
> We should probably not enable MASK_BYTE_OPS by default in configure.in
> until we've got it fixed.
Kaveh -- can you try removing MASK_BYTE_OPS in gcc/{configure,configure,in}
for the alpha56 target, then try to bootstrap the ev56?
If that works we can use it for the release; for the mainline we've already
sucked in the work from ev56 work from the FSF tree.
jeff
next prev parent reply other threads:[~1997-11-13 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-12 14:37 Kaveh R. Ghazi
1997-11-12 15:00 ` Richard Henderson
1997-11-13 11:19 ` Jeffrey A Law [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-11-13 14:58 Kaveh R. Ghazi
1997-11-11 17:12 Kaveh R. Ghazi
1997-11-12 12:09 ` Jim Wilson
1997-11-06 17:24 Kaveh R. Ghazi
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=2667.879448175@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=ghazi@caip.rutgers.edu \
--cc=rth@cygnus.com \
--cc=wilson@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).