sh64-elf (SH5) port: directory opcodes
Alexandre Oliva
aoliva@redhat.com
Tue Feb 5 09:02:00 GMT 2002
More information about the Binutils mailing list
Tue Feb 5 09:02: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 Feb 5, 2002, Andrew Cagney <ac131313@cygnus.com> wrote: > Why is this necessary? Shouldn't all disassemblers be included and > then, perhaps, just tweak the default arch/mach? I suppose it's because there's no sense whatsoever in including the SH5 machinery in a sh-elf build. sh-elf has no support for SH5 in binutils and simulator, only sh64-elf does. SH5 is such a different architecture from earlier SH versions that it barely makes sense to keep them all in a single bfd_arch. It only does because one of the ISAs supported by SH5 happens to be very similar with that used by earlier SHs, so we can reuse a lot of code. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{cygnus.com, redhat.com} CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist Professional serial bug killer
- 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