search for: symtype

Hi Ulrich, and any other llvm PowerPC/JIT users, It looks like the Numba maintainers have run in to an issue with RuntimeDyldELF's PowerPC support (See https://github.com/numba/numba/issues/2451#issuecomment-377739948 and later comments) Due to a recent change to weak symbol handling, we now always resolve to the first copy of a function that is emitted (discarding redundant weak/odr

...initrd-2.6.18.8-0.1-default lrwxrwxrwx 1 root root 32 12. Apr 17:10 initrd-2.6-xen.img -> initrd-2.6.16.33-xen_3.0.4.1.img -rw-r--r-- 1 root root 385536 12. Apr 11:54 message -rw-r--r-- 1 root root 87770 6. Mär 17:08 symsets-2.6.18.8-0.1-default.tar.gz -rw-r--r-- 1 root root 344114 6. Mär 17:08 symtypes-2.6.18.8-0.1-default.gz -rw-r--r-- 1 root root 100632 6. Mär 17:08 symvers-2.6.18.8-0.1-default.gz -rw-r--r-- 1 root root 696724 5. Jan 13:51 System.map-2.6.16.33-xen_3.0.4.1 -rw-r--r-- 1 root root 744466 6. Mär 17:03 System.map-2.6.18.8-0.1-default -rwxr-xr-x 1 root root 1762171 6. Mär 17:07 vmli...

...ions in the object. > + for (const std::pair<SymbolRef, uint64_t> &P : computeSymbolSizes(DebugObj)) { > + SymbolRef Sym = P.first; > + std::vector<LLVMPerfJitDebugEntry> LineInfo; > + std::string SourceFileName; > + > + Expected<SymbolRef::Type> SymTypeOrErr = Sym.getType(); > + if (!SymTypeOrErr) { > + // TODO: Actually report errors helpfully. > + consumeError(SymTypeOrErr.takeError()); > + continue; > + } > + SymbolRef::Type SymType = *SymTypeOrErr; > + if (SymType != SymbolRef::ST_Function) >...

...lumn = 24, last_column = 31}, {nle = 0x18}}}, refcnt = 1, flags = 0, dtype = 0x42df60 <integer_type>, byteorder = BYTEORDER_INVALID, len = 4, ops = 0x433f00 <payload_expr_ops>, op = OP_INVALID, {{scope = 0x0, identifier = 0x42fcf0 <proto_unknown_template> "\332\374B", symtype = SYMBOL_SET}, { verdict = 0, chain = 0x42fcf0 <proto_unknown_template> "\332\374B"}, {value = {{_mp_alloc = 0, _mp_size = 0, _mp_d = 0x42fcf0 <proto_unknown_template>}}}, {prefix = 0x0, prefix_len = 4390128}, {expressions = {next = 0x0, prev = 0x42fcf0 <prot...

Having something like this available in tree would definitely be useful. For simplicity, why don't we start with support for the second style? This is the long term useful one and would be a good starting point for getting the code in tree. Can you give a pointer to the patch so that I can assess the rough complexity? If it's simple enough, I'd be happy to help get it reviewed

Hi, On 2016-12-29 13:17:50 -0800, Philip Reames wrote: > Having something like this available in tree would definitely be > useful. Cool. > For simplicity, why don't we start with support for the second style? This > is the long term useful one and would be a good starting point for getting > the code in tree. Works for me. > Can you give a pointer to the patch so that

...dELF::processRelocationRe gsi = GlobalSymbolTable.find(TargetName.data()); if (gsi != GlobalSymbolTable.end()) { Value.SectionID = gsi->second.first; + Value.Offset = gsi->second.second; Value.Addend = gsi->second.second + Addend; } else { switch (SymType) { @@ -860,6 +890,7 @@ void RuntimeDyldELF::processRelocationRe Value.Addend = Addend; break; } + case SymbolRef::ST_Data: case SymbolRef::ST_Unknown: { Value.SymbolName = TargetName.data(); Value.Addend = Addend; @@ -1150,8 +1181...

Changes: - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce

Changes: - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

Changes: - patch v3: - Update on message to describe longer term PIE goal. - Minor change on ftrace if condition. - Changed code using xchgq. - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends

I have updated the klibc patchset based on feedback received. In particular, the patchset has been reorganized so as not to break git-bisect. Additionally, this updates the patch base to 2.6.17-git12 (d38b69689c349f35502b92e20dafb30c62d49d63) and klibc 1.4.8; the main difference on the klibc side is removal of obsolete code. This is also available as a git tree at: