public inbox for
 help / color / mirror / Atom feed
From: Richard Henderson <>
To: Cort Dougan <>
Subject: Re: ppc instructions in gas
Date: Thu, 06 May 1999 18:43:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, May 06, 1999 at 06:57:54PM -0600, Cort Dougan wrote:
> } We should fix gcc then.  That should not be hard at all.
> Ok.  Patch gcc to emit correct code and modify the asm we have in the
> kernel?  Know of any cute gas methods of converting 0xffff and its ilk to a
> signed value?

Pardon?  "gas methods"?

> } 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.
> I'd prefer to actually do the right thing in my asm and if gcc did the same
> that would all the better.  So the check in binutils to allow unsigned
> values is probably a workaround for gcc?

No, the check to allow unsigned values is a workaround for (to pick a
name out of the hat) NorTel's hand-written assembly code.

So I'm on the right page, "lis" is the only instruction this is an issue
for?  What about the old "liu" insn?  "U" presumably stood for "upper"
not "unsigned"?


  parent reply	other threads:[~1999-05-06 18:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
1999-05-06 15:07     ` Richard Henderson
     [not found]       ` <>
1999-05-06 15:35         ` Richard Henderson
     [not found]           ` <>
1999-05-06 16:56             ` Richard Henderson
     [not found]               ` <>
1999-05-06 17:49                 ` Richard Henderson
     [not found]                   ` <>
1999-05-06 18:43                     ` Richard Henderson [this message]
1999-05-06 20:06       ` Ian Lance Taylor
1999-05-06 20:13         ` Richard Henderson
1999-05-06 20:43           ` Ian Lance Taylor

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:

* 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).