search for: sto_mips16

STO_MIPS16 and STO_MICROMIPS flags denote that the symbol use a different "compressed" instructions encoding. Both these flags can be combined with usual "visibility" flags. It looks like adding new flag into the contentTypes set might solve the problem. Thanks for the idea. I try to impl...

...chitecture specific set of flags and modify Native and YAML > formats correspondingly. Interpretation of this field is completely > target/architecture dependent. > > Any opinions? > > On Thu, Nov 6, 2014 at 7:09 PM, Simon Atanasyan <simon at atanasyan.com> wrote: >> STO_MIPS16 and STO_MICROMIPS flags denote that the symbol use a >> different "compressed" instructions encoding. Both these flags can be >> combined with usual "visibility" flags. >> >> It looks like adding new flag into the contentTypes set might solve >> th...

...and modify Native and YAML > > formats correspondingly. Interpretation of this field is completely > > target/architecture dependent. > > > > Any opinions? > > > > On Thu, Nov 6, 2014 at 7:09 PM, Simon Atanasyan <simon at atanasyan.com> wrote: > >> STO_MIPS16 and STO_MICROMIPS flags denote that the symbol use a > >> different "compressed" instructions encoding. Both these flags can be > >> combined with usual "visibility" flags. > >> > >> It looks like adding new flag into the contentTypes set migh...

Hi, On MIPS st_other field in the ELF symbols table might contain some additional MIPS-specific flags besides visibility ones. These flags should be copied to the output linked file. If YAML => Native conversion is switched off, there is no problem. But in case of the conversion we lose st_other field values. So I need an advice how to keep this information. Is it a good idea to extend YAML