search for: stt_object

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...

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 semantic...

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...

...zik 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. > >> Te...

...gt; 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 sema...

...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...

...assembler source: .type i, at object # @i .section .tdata,"awT", at progbits .globl i .align 4 i: .long 7 # 0x7 .size i, 4 ... is given ELF symbol type STT_TLS by gcc's assembler, but STT_OBJECT by clang's assembler. I think this used to work, a few weeks ago. Has anything changed in this are recently? Thanks, Jay.

...at object               # @i >        .section        .tdata,"awT", at progbits >        .globl  i >        .align  4 > i: >        .long   7                       # 0x7 >        .size   i, 4 > > ... is given ELF symbol type STT_TLS by gcc's assembler, but > STT_OBJECT by clang's assembler. The .type directive should probably specify type "tls_object" rather than just "object". But I think gas infers that this is a TLS symbol anyway, because it is mentioned in TLS-related relocations. See this thread and follow-ups: http://www.cygwin.com...

...ing copy) @@ -1000,7 +1000,7 @@ switch (symb->getType()) { case ELF::STT_SECTION: - Result = Section ? Section->sh_addr : UnknownAddressOrSize; + Result = Section ? Section->sh_offset : UnknownAddressOrSize; return object_error::success; case ELF::STT_FUNC: case ELF::STT_OBJECT: -Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130118/506f6f0a/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: section-offset.patch Type: appli...

Hi, On Ubuntu Linux/x86_64, I get: $ cat t.c #include <stdio.h> __thread int i = 7; int main() { printf("%d\n", i); } $ clang -o t t.c $ ./t Segmentation fault (gdb) disas Dump of assembler code for function main: 0x0000000000400560 <+0>: push %rbp 0x0000000000400561 <+1>: mov %rsp,%rbp 0x0000000000400564 <+4>: sub $0x10,%rsp

...a valid directive. + MCSA_Invalid = 0, ///< Not a valid directive. // Various directives in alphabetical order. - MCSA_ELF_TypeFunction, /// .type _foo, STT_FUNC # aka @function - MCSA_ELF_TypeIndFunction, /// .type _foo, STT_GNU_IFUNC - MCSA_ELF_TypeObject, /// .type _foo, STT_OBJECT # aka @object - MCSA_ELF_TypeTLS, /// .type _foo, STT_TLS # aka @tls_object - MCSA_ELF_TypeCommon, /// .type _foo, STT_COMMON # aka @common - MCSA_ELF_TypeNoType, /// .type _foo, STT_NOTYPE # aka @notype - MCSA_Global, /// .globl - MCSA_Hidden,...

...;        .section        .tdata,"awT", at progbits >>        .globl  i >>        .align  4 >> i: >>        .long   7                       # 0x7 >>        .size   i, 4 >> >> ... is given ELF symbol type STT_TLS by gcc's assembler, but >> STT_OBJECT by clang's assembler. > > The .type directive should probably specify type "tls_object" rather > than just "object". The attached patch fixes this, and it makes my favourite (proprietary) app work on Linux when compiled with clang. > But I think gas infers that...

...umber of defined types. */ +#define STB_LOOS 10 /* start of OS-specific */ +#define STB_HIOS 12 /* end of OS-specific */ +#define STB_LOPROC 13 /* start of processor-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...

....dynamic Type: SHT_DYNAMIC Entries: - Tag: DT_SONAME Value: libsomething.so - Tag: DT_SYMTAB Value: .dynsym - Tag: DT_SYMENT Value: 0x18 DynamicSymbols: Global: - Name: foo Type: STT_FUNC Section: .data - Name: bar Type: STT_OBJECT Section: .data The final section is of type SHT_DYNAMIC, and the "Entries" key illustrates the proposed addition. Walking through the three dynamic entries, 1. DT_SONAME: The value of this entry is a string that will be inserted into the dynamic string table (.dynstr) alongside...

2012/1/23 Bendersky, Eli <eli.bendersky at intel.com>: > Hi, > > I would like to examine the implications you mention in more detail. > Thank you! > (1) Symbol address > According to the ELF standard, in a symbol table entry st_value means: "In relocatable files, st_value holds a section offset for a defined symbol. That is, > st_value is an offset from the

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 --