From: Neil Booth <neil@daikokuya.co.uk>
To: Mike Cleary <mcleary@iol.unh.edu>
Cc: bemis@iol.unh.edu, clp@iol.unh.edu, gcc@gcc.gnu.org
Subject: Re: bitmap.o error on alpha build of basic toolchain
Date: Tue, 30 Jul 2002 13:22:00 -0000 [thread overview]
Message-ID: <20020730154440.GA11225@daikokuya.co.uk> (raw)
In-Reply-To: <3D46AFE6.8070806@iol.unh.edu>
Mike Cleary wrote:-
> Hello Neil,
> I just checked the same build with the latest CVS and it still came up
> with ther error.
That's odd. The warnings are bogus, and fixed by a patch rth made
a few days ago. The compiler would miscompile itself. I assume
the fix was committed, maybe it hasn't been yet.
Dunno what else to suggest.
Neil.
next parent reply other threads:[~2002-07-30 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D46AFE6.8070806@iol.unh.edu>
2002-07-30 13:22 ` Neil Booth [this message]
2002-07-30 14:11 ` H. J. Lu
2002-07-30 14:41 ` Neil Booth
2002-07-30 15:49 ` H. J. Lu
2002-07-30 13:21 France, George (LKG)
-- strict thread matches above, loose matches on Subject: below --
2002-07-29 10:20 bemis
2002-07-29 23:22 ` Neil Booth
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=20020730154440.GA11225@daikokuya.co.uk \
--to=neil@daikokuya.co.uk \
--cc=bemis@iol.unh.edu \
--cc=clp@iol.unh.edu \
--cc=gcc@gcc.gnu.org \
--cc=mcleary@iol.unh.edu \
/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).