This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Should sh-*-* enable 64bit targets?

On Wed, May 24, 2006 at 10:58:55PM -0700, H. J. Lu wrote:
> I built the sh-linux cross binutils without my patch:
> [hjl@gnu-13 binutils-import-cross]$ ./build-sh-linux/ld/ld-new -V
> GNU ld version 2.17.50 20060524
>   Supported emulations:
>    shlelf_linux
>    shelf_linux
> My patch doesn't change it.

Ridiculous.  You didn't even build a sh-linux cross on a host that tests
your change!

src/binutils-current/configure --prefix=/usr/local --disable-nls --build=i586-linux --host=i586-linux --target=sh-linux


../opcodes/.libs/libopcodes.a(sh64-dis.o): In function `sh64_get_contents_type_disasm':
/src/binutils-current/opcodes/sh64-dis.c:463: undefined reference to `sh64_get_contents_type'
/src/binutils-current/opcodes/sh64-dis.c:477: undefined reference to `sh64_get_contents_type'
collect2: ld returned 1 exit status
make[4]: *** [objdump] Error 1
make[4]: Leaving directory `/home/alan/build/gas/sh/binutils'

> The question is what the original intention was.

I don't care what the original intent of those SH #ifdef BFD64 tests
were.  They are quite useless.

> I don't think "#ifdef BFD64" is just a comment. targmatch.sed will put
> them into targmatch.h:

For the purpose of running config.bfd as a shell script, it is most
definitely just a comment.  targmatch.sed only picks out targ_defvec, so
in the case of the SH #ifdef BFD64, it is useless for targmatch.h too.

Alan Modra
IBM OzLabs - Linux Technology Centre

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]