From: Richard Henderson <firstname.lastname@example.org>
To: Cort Dougan <email@example.com>
Subject: Re: ppc instructions in gas
Date: Thu, 06 May 1999 17:49:00 -0000 [thread overview]
Message-ID: <19990506174929.A13363@cygnus.com> (raw)
On Thu, May 06, 1999 at 06:08:06PM -0600, Cort Dougan wrote:
> As it is, gcc (32-bit mode) generates
> code that will do a lis of 0xffff (the unsigned value) which shouldn't work
> according to the manual. When I do this for 64-bit with egcs it will not
We should fix gcc then. That should not be hard at all.
> Right, it should complain for both 32 and 64 bit. It only complains for
> 64-bit now, though. So I don't know if I should fix our asm (probably not,
> even though according to the manual it's incorrect but gcc generates the
> same code).
> If I can change those operands to be unsigned it will still load a 16 bit
> value correctly but will allow things to work according to the manual and
> the egcs generated code.
> Can we make these critters unsigned? I don't know of any code that
> requires they be signed anywhere.
I'm not real comfortable just changing it. Who knows what sort
of code is out there. I wouldn't be adverse to reducing the
error to a warning in 32-bit mode though.
next prev parent reply other threads:[~1999-05-06 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19990504180843.A31050@attis.cs.nmt.edu>
[not found] ` <19990505145806.H9469@cygnus.com>
[not found] ` <19990505165232.A8594@attis.cs.nmt.edu>
1999-05-06 15:07 ` Richard Henderson
[not found] ` <19990506161159.A27229@attis.cs.nmt.edu>
1999-05-06 15:35 ` Richard Henderson
[not found] ` <19990506171639.A26711@attis.cs.nmt.edu>
1999-05-06 16:56 ` Richard Henderson
[not found] ` <19990506180806.A5113@attis.cs.nmt.edu>
1999-05-06 17:49 ` Richard Henderson [this message]
[not found] ` <19990506185754.A12025@attis.cs.nmt.edu>
1999-05-06 18:43 ` Richard Henderson
1999-05-06 20:06 ` Ian Lance Taylor
1999-05-06 20:13 ` Richard Henderson
1999-05-06 20:43 ` Ian Lance Taylor
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).