similar to: Providing __dso_handle in LLVM

Displaying 20 results from an estimated 4000 matches similar to: "Providing __dso_handle in LLVM"

2017 Jun 03
2
Providing __dso_handle in LLVM
On Fri, Jun 2, 2017 at 1:01 PM Sean Silva <chisophugis at gmail.com> wrote: > On Thu, Jun 1, 2017 at 8:47 PM, Petr Hosek via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> This is a followup to the discussion that started in D28791. To provide >> the context, we need a way to provide __dso_handle in Fuchsia. __dso_handle >> symbol is mandated by C++
2019 Mar 25
2
Trying to create a pure LLVM toolchain on musl based distribution
Le 25/03/2019 à 14:41, Peter Smith a écrit : > Hello David, > > I don't know much about the specifics of Musl, so I'm responding generally. > > As I understand it, clang expects to find the compiler-rt libraries > relative to the resource directory, which you can find out the > location of with clang --print-resource-dir . By default it is > lib/clang/9.0.0
2007 Jan 10
4
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
The machine is a Dell workstation with xeon processors. The OS is RHEL 4 AS x86_64 gcc version is 3.4.6 I checked out the llvm-gcc from svn, configured with ../llvm-gcc/configure --prefix=$HOME/llvm-gcc-install --enable-llvm=$HOME/llvmobj/ --enable-languages=c,c++ --enable-checking --disable-shared --disable-multilib and get the following error message: make
2007 Jan 10
0
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
gcc 3.4.x builds LLVM incorrectly on x86_64. gcc 4.0 will get you much farther, but the llvm-test regression tests still have massive problems. Zhongxing Xu wrote: > The machine is a Dell workstation with xeon processors. The OS is RHEL > 4 AS x86_64 > gcc version is 3.4.6 > > I checked out the llvm-gcc from svn, configured with > ../llvm-gcc/configure
2018 Apr 02
2
LLD-linked binary segfaults at runtime on alpine linux
Alpine linux is a distribution that uses musl libc instead glibc. Here are my steps to reproduce: On Alpine linux, download LLVM, Clang, LLD 6.0.0 from releases.llvm.org, and build them from source. $ clang -c hello_world.c $ ld.lld --gc-sections -m elf_x86_64 -o hello_world /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib/Scrt1.o
2020 Jun 09
2
Cross compile x64 to AArch64 issues
Hi, I am trying to cross compile release-10.x to AArch64 (target=aarch64-linux-gnu), and the directions listed at [1] are not completing the initial cmake step. I'm currently running Manjaro, with the aarch64-linux-gnu package (and associated binutils, headers, and glibc packages). My cmake command is cmake -DCMAKE_CROSSCOMPILING=True -DCMAKE_INSTALL_PREFIX=`realpath install`
2007 Jan 11
2
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
On Jan 9, 2007, at 9:48 PM, Jeff Cohen wrote: > gcc 3.4.x builds LLVM incorrectly on x86_64. > > gcc 4.0 will get you much farther, but the llvm-test regression tests > still have massive problems. Please file bug reports on these. Thanks! Evan > > Zhongxing Xu wrote: >> The machine is a Dell workstation with xeon processors. The OS is >> RHEL >> 4 AS
2018 Apr 02
0
LLD-linked binary segfaults at runtime on alpine linux
Can you add `--reproduce=repro` to lld command line? That generates repro.tar in your current directory which contains all input files. And then please compress and upload it somewhere so that we can take a look. On Mon, Apr 2, 2018 at 9:18 AM Andrew Kelley via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Alpine linux is a distribution that uses musl libc instead glibc. Here are
2017 May 17
3
[lld][ELF] Add option to make .dynamic read only
On Wed, May 17, 2017 at 1:32 PM, Rui Ueyama via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Wed, May 17, 2017 at 1:11 PM, Petr Hosek <phosek at chromium.org> wrote: > >> The motivation is not only memory savings but also security: >> can-never-be-written is strictly better than RELRO in all cases. The >> biggest win is when .dynamic is the sole reason
2018 Apr 02
1
LLD-linked binary segfaults at runtime on alpine linux
https://superjoe.s3.amazonaws.com/temp/repro.tar.xz On Mon, Apr 2, 2018 at 1:26 PM, Rui Ueyama <ruiu at google.com> wrote: > Can you add `--reproduce=repro` to lld command line? That generates > repro.tar in your current directory which contains all input files. And > then please compress and upload it somewhere so that we can take a look. > > > On Mon, Apr 2, 2018 at
2007 Jan 12
2
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
I do all my LLVM stuff on x86_64 without trouble... I have a nightly tester up, and its only getting a few regressions currently, and I think some of those have to do with the radical changes going on in LLVM-land currently, and others with no one having done support for x86-64 in debugging output. (this is at least most of what I've seen, ymmv). Also, for the record, I have found both gcc
2012 Jun 20
3
[LLVMdev] Is cross-compiling for ARM on x86 with llvm/Clang possible?
Hello, Thank you for your kind attention to my issue and your help. I changed the tool chain and tried again. And there is a little progress but still have some problem. Using --sysroot doesn't make clang use linker(ld) in the cross tool. Most important question is how I can make clang use cross tool linker. Let me show you my experiment and questions below. There are two questions. [Run]
2017 May 23
3
[lld][ELF] Add option to make .dynamic read only
Petr Hosek via llvm-dev <llvm-dev at lists.llvm.org> writes: > One of the design principles we're trying to follow is to make everything > read-only, unless it has be writable. The only reason for .dynamic to be > writable is DT_DEBUG which is something we never intend to support. FWIW in > Fuchsia all we need is a read-only .dynamic without emitting DT_DEBUG > altogether,
2007 Jan 11
0
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
Already have concerning gcc 3.4: http://llvm.org/bugs/show_bug.cgi?id=1056 As for llvm-test issues, quite frankly I don't know how well they're expected to work on x86_64. No one has jumped in and said they run fine on their x86_64 system. Maybe they're code generator bugs, or maybe they're portability issues for FreeBSD (though I never saw such massive problems with 32-bit
2012 Jun 19
2
[LLVMdev] Is cross-compiling for ARM on x86 with llvm/Clang possible?
Hello Gergö, Joerg and people on our list With your kind answer, I tried to build a hello world program for ARM(arm-none-linux-gnueabi) on my x86-64 PC. Thank you we verified the generated bitcode. The only thing remained is linking. Let me brief what I did so far. 1. Built Clang/llvm in a way explained in http://clang.llvm.org/get_started.html on Ubuntu 11.10 x86-64 PC 2. Downloaded gcc-4.0
2016 Feb 08
3
[LLD] Incorrect comparision of pointers to function defined in DSO
Hi, It looks like I have found a bug in LLD. Suppose DSO defines a global variable 'data' and initializes it by the address of function 'set_data' defined in the same DSO. If an executable file (linked by LLD) gets address of the '&set_data' function and compares it with a value stored in the 'data' variable it gets different result. If the executable is linked
2007 Jan 12
0
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
Could you provide a list of all tests failing for you? You can just grep the output from make for 'FAILED!'. I've fixed 5 of them so far... 275 to go... Chandler Carruth wrote: > I do all my LLVM stuff on x86_64 without trouble... I have a nightly > tester up, and its only getting a few regressions currently, and I > think some of those have to do with the radical
2010 Dec 28
1
[LLVMdev] llvm with non-standard gcc location
Hi all, I'd like to use LLVM 2.8 on a openSUSE 10.3 box and when I try to compile anything I get an error: martin at vm:~/project/backend> clang tutorial001.m -v -emit-llvm -o tutorial001 clang version 2.9 (trunk 122601) Target: x86_64-unknown-linux-gnu Thread model: posix "/usr/local/llvm/Debug+Asserts/bin/clang" -cc1 -triple x86_64-unknown-linux-gnu -emit-llvm-bc -disable-free
2020 Sep 02
2
LLD: Can we make --warn-backrefs the default?
On 2020-09-01, Petr Hosek wrote: >I see the GNU ld behavior as a limitation, not as a feature, as Peter Smith >also pointed out in https://reviews.llvm.org/D86762. While it can be argued >that there are certain cases where it can help detect layering >violations as you mentioned in your change, I'm not sure how valuable that >is in practice. Every case I've encountered so
2007 May 26
0
[LLVMdev] Problems compiling llvm-gcc4 frontend on x86_64
Hi Warren, You have the -m32 flag set, but it's still giving you this: > Warning: Generation of 64-bit code for a 32-bit processor requested. > Warning: 64-bit processors all have at least SSE2. But are you sure you want to compile the LLVM-GCC source? You should use the binaries unless absolutely necessary. -bw On May 24, 2007, at 10:34 PM, Warren Armstrong wrote: > Hi all,