sh64-elf (SH5) port: directory opcodes
Hans-Peter Nilsson
hp@bitrange.com
Tue Feb 5 11:20:00 GMT 2002
More information about the Binutils mailing list
Tue Feb 5 11:20:00 GMT 2002
- Previous message (by thread): sh64-elf (SH5) port: directory opcodes
- Next message (by thread): sh64-elf (SH5) port: directory opcodes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5 Feb 2002, Alexandre Oliva wrote: > On Feb 5, 2002, Andrew Cagney <ac131313@cygnus.com> wrote: > > Anyway, if you always include support for all the SH variants, does > > anything break? > > Probably not, since --enable-targets=all works. Though you'd bloat binutils for people with sh[1-4] only. Some SH targets run native in limited systems, I've heard. Can we ignore the bloat issue? Maybe let sh-elf imply bfd+opcodes for sh[1-5] and leave sh[1-4][hl]* the way it is? (Including opcodes but not bfd seems useless. You can't get a sh5 bfd, so you can't (without tricks) invoke the disassembler AFAICT.) brgds, H-P
- Previous message (by thread): sh64-elf (SH5) port: directory opcodes
- Next message (by thread): sh64-elf (SH5) port: directory opcodes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list