Simon Atanasyan
2014-Nov-06 14:50 UTC
[LLVMdev] [lld][ELF] How to transfer st_other field value from input to output file
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 and Native format to store these data? Is there any alternative solutions? Thanks. -- Simon Atanasyan
Shankar Easwaran
2014-Nov-06 15:52 UTC
[LLVMdev] [lld][ELF] How to transfer st_other field value from input to output file
One way to do that is to add new visibility / contentTypes (whatever is relevant) added for each of the values st_other picks ? What are the other values st_other can take on MIPS ? Shankar Easwaran On 11/6/2014 8:50 AM, Simon Atanasyan wrote:> 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 and Native format to store these data? Is there any > alternative solutions? > > Thanks. >-- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation
Simon Atanasyan
2014-Nov-06 16:09 UTC
[LLVMdev] [lld][ELF] How to transfer st_other field value from input to output file
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 implement it. On Thu, Nov 6, 2014 at 6:52 PM, Shankar Easwaran <shankare at codeaurora.org> wrote:> One way to do that is to add new visibility / contentTypes (whatever is > relevant) added for each of the values st_other picks ? > > What are the other values st_other can take on MIPS ? > > Shankar Easwaran > > > On 11/6/2014 8:50 AM, Simon Atanasyan wrote: >> >> 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 and Native format to store these data? Is there any >> alternative solutions?-- Simon Atanasyan
Maybe Matching Threads
- [LLVMdev] [lld][ELF] How to transfer st_other field value from input to output file
- [LLVMdev] [lld][ELF] How to transfer st_other field value from input to output file
- [LLVMdev] [lld][ELF] How to transfer st_other field value from input to output file
- [LLVMdev] [lld] Linker cannot handle sections with non-unique names
- [LLVMdev] [lld] Using llvm-mc in lld test suite