This is the mail archive of the
binutils@sourceware.cygnus.com
mailing list for the binutils project.
Re: Should the linker tests notice multilib variations ?
- To: devans@cygnus.com
- Subject: Re: Should the linker tests notice multilib variations ?
- From: Ian Lance Taylor <ian@zembu.com>
- Date: 13 Jul 1999 12:34:18 -0400
- CC: nickc@cygnus.com, binutils@sourceware.cygnus.com
- References: <199907131629.JAA00144@canuck.cygnus.com.>
Date: Tue, 13 Jul 1999 09:29:57 -0700
From: Doug Evans <devans@cygnus.com>
Perhaps we should even make -EB and -EL global options
for the assembler, and use some new md function to implement them.
I think this is the way to go.
I'll even volunteer to implement it ...
Thanks.
Do we need a new md function though?
Studying tc-ppc.[ch], set_target_endian seems superfluous.
target_big_endian is initialized to TARGET_BYTES_BIG_ENDIAN in read.c.
Then at the end of md_begin, if !set_target_endian, target_big_endian
gets set to TARGET_BYTES_BIG_ENDIAN again.
(PPC_BIG_ENDIAN == TARGET_BYTES_BIG_ENDIAN).
As I recall, different gas targets used to implement endianness
differently. Then somebody introduced the global target_big_endian
variable. If you can straighten things out so that no md function is
required, so much the better.
On the other hand, we do need some code somewhere that checks whether
the option can actually be supported--we probably shouldn't just
accept and ignore -EL and generate a big endian file--so we may need
some target specific information. Or maybe the same BFD information
that Nick wants for the linker can be used here as well.
Ian