search for: mysym

...ress, the procesor switches to mips16 mode and when you call an even numbered address it switches to mips32 mode. This causes some problems in the exception tables. Basically, labels that are not landing pad symbols that are inserted for exception handling and dwarf purposes, must declared : $mysym = . as opposed to: $mysym: Has this problem of making this distinction already been solved in llvm and if so, how is this done? Tia. Reed

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

...ode and when you call an even numbered > address it switches to mips32 mode. > > This causes some problems in the exception tables. > > Basically, labels that are not landing pad symbols that are inserted for > exception handling > and dwarf purposes, must declared : > > $mysym = . > > as opposed to: > > $mysym: > > Has this problem of making this distinction already been solved in llvm > and if so, how is this done? > > Tia. > > Reed

...ed >> address it switches to mips32 mode. >> >> This causes some problems in the exception tables. >> >> Basically, labels that are not landing pad symbols that are inserted for >> exception handling >> and dwarf purposes, must declared : >> >> $mysym = . >> >> as opposed to: >> >> $mysym: >> >> Has this problem of making this distinction already been solved in llvm >> and if so, how is this done? >> >> Tia. >> >> Reed