From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Henderson To: Cort Dougan Cc: gas2@sourceware.cygnus.com Subject: Re: ppc instructions in gas Date: Thu, 06 May 1999 17:49:00 -0000 Message-id: <19990506174929.A13363@cygnus.com> References: <19990504180843.A31050@attis.cs.nmt.edu> <19990505145806.H9469@cygnus.com> <19990505165232.A8594@attis.cs.nmt.edu> <19990506150724.A10994@cygnus.com> <19990506161159.A27229@attis.cs.nmt.edu> <19990506153554.B10994@cygnus.com> <19990506171639.A26711@attis.cs.nmt.edu> <19990506165624.A24549@cygnus.com> <19990506180806.A5113@attis.cs.nmt.edu> <19990506180806.A5113@attis.cs.nmt.edu> X-SW-Source: 1999/msg00098.html 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 > assemble. 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. r~