search for: versym

Displaying 6 results from an estimated 6 matches for "versym".

How to run single compiler-rt test in monorepo?
2019 Oct 31
2
How to run single compiler-rt test in monorepo?
...from there. For LLVM I can do the following: > cd build/buildtrunk/test > ../bin/llvm-lit --show-tests . And it shows all tests discovered of the llvm main library, but not tests of for example clang or compiler-rt. Running a single test works aswell: > ../bin/llvm-lit -v tools/yaml2obj/versym-section.yaml -- Testing: 1 tests, 1 workers -- PASS: LLVM :: tools/yaml2obj/versym-section.yaml (1 of 1) ... However whatever I try, I have not succeeded in having Lit discover the compiler-rt tests, and I didn't manage to run just one compiler-rt test. Information online is sparse, and I didn...
ASAN not finding any bugs?
2020 Feb 03
2
ASAN not finding any bugs?
...2 (PLTRELSZ) 72 (bytes) 0x0000000000000014 (PLTREL) RELA 0x0000000000000017 (JMPREL) 0x400528 0x0000000000000007 (RELA) 0x400510 0x0000000000000008 (RELASZ) 24 (bytes) 0x0000000000000009 (RELAENT) 24 (bytes) 0x000000006ffffffe (VERNEED) 0x4004f0 0x000000006fffffff (VERNEEDNUM) 1 0x000000006ffffff0 (VERSYM) 0x4004e6 0x0000000000000000 (NULL) 0x0
Targeting old glibc
2020 Nov 12
1
Targeting old glibc
...d. Fortunately its absence does not affect correctness. > This requires binary patching > > ... > 0x000000006ffffffb (FLAGS_1) Flags: NOW > - 0x000000006ffffffe (VERNEED) 0x8ef0 > - 0x000000006fffffff (VERNEEDNUM) 5 > - 0x000000006ffffff0 (VERSYM) 0x89c0 > - 0x000000006ffffff9 (RELACOUNT) 1536 > 0x0000000000000000 (NULL) 0x0 > > > In the end, the solution is: > > r2 -wqc '/x feffff6f00000000 @ section..dynamic; w0 16 @ hit0_0' a.so; llvm-objcopy -R .gnu.version -R .gnu.versi...
ASAN not finding any bugs?
2020 Feb 03
2
ASAN not finding any bugs?
...t; 0x0000000000000017 (JMPREL) 0x400528 >> 0x0000000000000007 (RELA) 0x400510 >> 0x0000000000000008 (RELASZ) 24 (bytes) >> 0x0000000000000009 (RELAENT) 24 (bytes) >> 0x000000006ffffffe (VERNEED) 0x4004f0 >> 0x000000006fffffff (VERNEEDNUM) 1 >> 0x000000006ffffff0 (VERSYM) 0x4004e6 >> 0x0000000000000000 (NULL) 0x0 >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
Targeting old glibc
2020 Nov 11
2
Targeting old glibc
It did partially fix the issue but there is still one problem: llvm-objdump -sx gives: Version References: required from libpthread.so.0: 0x09691a75 0x00 05 GLIBC_2.2.5 0x09691972 0x00 09 GLIBC_2.3.2 0x09691973 0x00 07 GLIBC_2.3.3 0x06969192 0x00 12 GLIBC_2.12 required from libdl.so.2: 0x09691a75 0x00 21 GLIBC_2.2.5 required from libuuid.so.1: 0x09da27b0 0x00 19
Targeting old glibc
2020 Nov 11
0
Targeting old glibc
...gs. DT_RELACOUNT is also deleted. Fortunately its absence does not affect correctness. This requires binary patching ... 0x000000006ffffffb (FLAGS_1) Flags: NOW - 0x000000006ffffffe (VERNEED) 0x8ef0 - 0x000000006fffffff (VERNEEDNUM) 5 - 0x000000006ffffff0 (VERSYM) 0x89c0 - 0x000000006ffffff9 (RELACOUNT) 1536 0x0000000000000000 (NULL) 0x0 In the end, the solution is: r2 -wqc '/x feffff6f00000000 @ section..dynamic; w0 16 @ hit0_0' a.so; llvm-objcopy -R .gnu.version -R .gnu.version_r a.so >On Wed, Nov 11, 2...