[committed] pa10 load/store opcodes and FLAG_STRICT
Carlos O'Donell
carlos@systemhalted.org
Mon Jul 11 14:34:00 GMT 2005
More information about the Binutils mailing list
Mon Jul 11 14:34:00 GMT 2005
- Previous message (by thread): [committed] pa10 load/store opcodes and FLAG_STRICT
- Next message (by thread): [committed] pa10 load/store opcodes and FLAG_STRICT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, Jul 10, 2005 at 10:40:32PM -0400, John David Anglin wrote: > I discovered this weekend that there is still a bit of code that relies > on old PA 1.0 syntax (gmp). It uses "0" for the space register "%sr0". > This restores the previous behavior prior to my cache completer update. > I had to reorder varies entries in the table because the immediate > ranges for non-strict loads and stores have to be order from largest > to smallest. > > Tested on hppa-unknown-linux-gnu and hppa2.0w-hp-hpux11.11. Committed > to trunk. I like the FLAG_STRICT mode, I think using '0' for the space register is rubish. I've cleaned up glibc under the strict mode. Are you adverse to making people cleanup poorly formated assembly? It's a mechanistic change :) c.
- Previous message (by thread): [committed] pa10 load/store opcodes and FLAG_STRICT
- Next message (by thread): [committed] pa10 load/store opcodes and FLAG_STRICT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list