search for: stt_file

Hi Nick, The object file already has the information that when its STT_FILE and the symbol name is the name of the translation unit already. I dont think the linker has to add a absolute symbol by figuring out the translation unit. Shankar Easwaran On Mon, Oct 15, 2012 at 6:07 PM, Nick Kledzik <kledzik at apple.com> wrote: > > On Oct 15, 2012, at 4:00 PM, S...

On 10/15/12 12:01, Nick Kledzik wrote: > > On Oct 15, 2012, at 8:08 AM, Sidney Manning wrote: >> >> I think that absolute atoms will need something similar to, "contentType" added. >> >> SHN_ABS symbols can have different types, STT_OBJECT, STT_FILE and maybe others. In order for the writer to tell it must have a way to reach back and ask the atom what type of symbols caused it to be created. To that end I added a contentType method to AbsoluteAtom and sprinkled changes around to make this work. > Tell me more about the semantics of STT_F...

On Oct 15, 2012, at 9:06 PM, Shankar Kalpathi Easwaran wrote: > The object file already has the information that when its STT_FILE and the symbol name is the name of the translation unit already. > > I dont think the linker has to add a absolute symbol by figuring out the translation unit. Then we are in agreement. Sid started this thread with the suggestion of adding new content types to AbsoluteAtoms so as to encode...

On Oct 15, 2012, at 8:08 AM, Sidney Manning wrote: > > I think that absolute atoms will need something similar to, "contentType" added. > > SHN_ABS symbols can have different types, STT_OBJECT, STT_FILE and maybe others. In order for the writer to tell it must have a way to reach back and ask the atom what type of symbols caused it to be created. To that end I added a contentType method to AbsoluteAtom and sprinkled changes around to make this work. Tell me more about the semantics of STT_FILE....

I think that absolute atoms will need something similar to, "contentType" added. SHN_ABS symbols can have different types, STT_OBJECT, STT_FILE and maybe others. In order for the writer to tell it must have a way to reach back and ask the atom what type of symbols caused it to be created. To that end I added a contentType method to AbsoluteAtom and sprinkled changes around to make this work. What do the V1 suffixes mean in the Nativ...

.../12 12:01, Nick Kledzik wrote: >> >> On Oct 15, 2012, at 8:08 AM, Sidney Manning wrote: >>> >>> I think that absolute atoms will need something similar to, "contentType" added. >>> >>> SHN_ABS symbols can have different types, STT_OBJECT, STT_FILE and maybe others. In order for the writer to tell it must have a way to reach back and ask the atom what type of symbols caused it to be created. To that end I added a contentType method to AbsoluteAtom and sprinkled changes around to make this work. >> Tell me more about the semantics of S...

I have read ELF specification once again. There is no any explicit references to absolute symbols with no name. The only real case when I see such symbol is a local absolute symbol with "STT_FILE" type. The name of "STT_FILE" symbol is a name of the source file associated with the object file and the "STT_FILE" symbol precedes the other STB_LOCAL symbols from this object file. So it is just a "marker" symbol. If think it's enough to do not call buildDup...

Hi, Method RefNameBuilder::buildDuplicateNameMap() has an assert which blocks atoms with empty name. In general it looks reasonable but some toolchains (for example Sourcery CodeBench in both MIPS and ARM editions) can generate an object file contains absolute STT_FILE symbols with empty name. Moreover crt1.o object file from this toolchain has such symbol. I do not know is it a feature or bug but that behavior exists for a long time. Here is the reproduction script: [[ $ cat test.c void foo() {} $ mips-linux-gnu-gcc -c test.c $ mips-linux-gnu-gcc -r -no...

...PM -0700, Evgenii Stepanov via llvm-dev wrote: > Another option is to allow the conflict, and make the global always > override the section symbol. This is easy to do in the integrated > assembler, but it appears that GAS simply does not work this way. Don't we have a similar case for STT_FILE already? Joerg

...irectives (which would imply that the assembler source was produced with debug info already) then emit one describing the assembler source file itself." Does .file imply that the assembly source was already produced with debug info? Perhaps not in all cases. If you wanted to emit an ELF::STT_FILE into your object, for example, you might add ```.file "foo.s"```. I think we should change this behavior to the previous - check for "-g" but ignore ".file" directives. Or maybe there's a compromise to be found among the different versions of ".file&quot...

Hi, currently LLVM does not handle the conflict between a section and a global _definition_ with the same name well. A section defines a local symbol with the same name (pointing to the start of the section). Depending on the order of declarations, LLVM either silently overrides the section symbol with the global, or crashes with fatal error: error in backend: symbol 'xxx' is already

...d imply that the assembler source was produced with debug info > already) then emit one describing the assembler source file itself.” > > > > Does .file imply that the assembly source was already produced with debug > info? Perhaps not in all cases. If you wanted to emit an ELF::STT_FILE > into your object, for example, you might add ```.file "foo.s"```. > > > > I think we should change this behavior to the previous – check for “-g” > but ignore “.file” directives. Or maybe there’s a compromise to be found > among the different versions of “.file” w...

...or-specific */ +#define STB_HIPROC 15 /* end of processor-specific */ + +#define STT_NOTYPE 0 /* symbol type is unspecified */ +#define STT_OBJECT 1 /* symbol is a data object */ +#define STT_FUNC 2 /* symbol is a code object */ +#define STT_SECTION 3 /* symbol associated with a section */ +#define STT_FILE 4 /* symbol's name is file name */ +#define STT_COMMON 5 /* symbol is a common data object */ +#define STT_TLS 6 /* symbol is thread-local data object*/ +#define STT_NUM 7 /* number of defined types. */ +#define STT_LOOS 10 /* start of OS-specific */ +#define STT_HIOS 12 /* end of OS-specifi...

Hi Andi, Four patches: - clean up asm/bugs.h, by moving all the C code into its own C file - split identify_cpu() into boot and secondary variants, so that boot-time setup functions can be marked __init - repost of the COMPAT_VDSO patches with a bit more robustness from unknown DT_tags, and functions marked __init, since all this is boot-time only setup. Thanks, J --

Hi Andi, Four patches: - clean up asm/bugs.h, by moving all the C code into its own C file - split identify_cpu() into boot and secondary variants, so that boot-time setup functions can be marked __init - repost of the COMPAT_VDSO patches with a bit more robustness from unknown DT_tags, and functions marked __init, since all this is boot-time only setup. Thanks, J --