search for: msg00623

On Fri, Nov 02, 2012 at 07:53:41PM -0700, reed kotler wrote: > Basically, labels that are not landing pad symbols that are inserted > for exception handling > and dwarf purposes, must declared : > > $mysym = . > > as opposed to: > > $mysym: Can't you use $mysym +/- 1 in the landing pad reference to work this idiosyncracy? Joerg

...you call a function, the ISA determines whether you are in mips16 >> or mips32 by the presence >> or absence of this bit. >> >> Some notes from the gcc mips16 checkins for this explain a lot of the >> issues. >> >> http://gcc.gnu.org/ml/gcc-patches/2008-08/msg00623.html >> http://gcc.gnu.org/ml/gcc-patches/2008-11/msg01273.html >> >> I will add a test case for the mips specific part. >> >> I have post commit review privilege for the mips area but not for any >> target independent areas. >> >> >> >> _...

mips16 has some unusual requirements for label symbols in .s. I think that arm thumb has the same issue but have not located yet how this is handled. When you have a label of an instruction in mips16, when you reference the label, the linker adds a 1 to the address. When you call an odd numbered address, the procesor switches to mips16 mode and when you call an even numbered address it