similar to: [LLVMdev] [OT] GCC specs language and adding options

Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] [OT] GCC specs language and adding options"

2009 Sep 18
0
[LLVMdev] [OT] GCC specs language and adding options
To add to what Duncan said, On Wed, Sep 16, 2009 at 1:28 PM, Aaron Gray <aaronngray.lists at googlemail.com> wrote: > Hi, > I have been trying to get to grips with GCC's specs language in order to add > COFF and ELF emission options. Good luck. :) > I have noticed that the '-emit-llvm-bc' option does not appear to work at > all either with -S or without, giving
2009 Jan 31
0
[LLVMdev] -O4 -fvisibility=hidden
I was able to also build sparky (http://www.cgl.ucsf.edu/home/sparky/) at -O4 under llvm-gcc-4.2 and llvm-g++-4.2 on darwin with minor patches... --- sparky/c++/_tkinter.c.orig 2009-01-30 22:14:28.000000000 -0500 +++ sparky/c++/_tkinter.c 2009-01-30 22:16:40.000000000 -0500 @@ -3089,6 +3089,9 @@ } } +PyMODINIT_FUNC +init_tkinter(void)
2015 Feb 15
3
[LLVMdev] Any mechanism available for link time inlineing?
mobi phil wrote: > thanks, sounds great, heard about llvm-lto, but was not following in > details. I have an llvm-lto in my dev branch build....now what I do not > find are some example on how to use it for link time inline-ing. In > worst case have to deal with the overhead to experiment With what linker? LLVM LTO is available by default with Apple's XCode development
2009 Jan 31
2
[LLVMdev] -O4 -fvisibility=hidden
On Mon, Jan 26, 2009 at 09:57:28AM -0800, Devang Patel wrote: > Hi Jack, > > On Jan 25, 2009, at 10:00 AM, Jack Howarth wrote: > > > Doing that changes the error messages into a bus > > error on the darwin linker. > > > Pl. file bugzilla report (or radar) with a reproducible test case so > that we can investigate this linker crash. > > As you
2016 Jul 21
4
difference between llvm-gcc and clang
Hi everyone, Both llvm-gcc and clang would use llvm as its backend. Dose everyone know the difference of bitcode generated by llvm-gcc and llvm? Or actually they are same, like if I use the same compiler options, like -O4. Any help is appreciated. Best, Yuxi -------------- next part -------------- An HTML attachment was scrubbed... URL:
2011 Mar 24
2
[LLVMdev] Instrumentation with liblto and gold
Hi, I need advice in instrumenting programs using liblto and gold plugin. Specifically, I added my pass in tools/lto/LTOCodeGenerator.cpp. My pass inserts functions (myLoad and myStore) for some load and store instructions. The functions exist in a library file. I found that the approach works for the example in the link: http://llvm.org/docs/GoldPlugin.html $ llvm-gcc -flto a.c -c -o a.o $ ar q
2011 Mar 25
1
[LLVMdev] Instrumentation with liblto and gold
Hi John, Thank you for your advice. LIBS and LDFLAGS work for the configure script, but they gave errors in the make stage for apache and mysql. I used either of the following ones with other flags: - export LIBS="-L/home/sangmin/Dropbox/Falcon/bin/ -ldummy" - export LDFLAGS="-L/home/sangmin/Dropbox/Falcon/bin/ -ldummy" Here are the error messages: Compile error (apache):
2019 Jul 16
3
lld-link crash when build openssl with LTO
Usage of the builtin appears independent of LTO, see below. With any of -fno-builtin, -fno-builtin-memcpy, and -ffreestanding, which are all typically used to prevent usage of memcpy calls, we still always get a memcpy builtin in TlsDriverEntryPoint(). I see this even without -flto (e.g. try with just -emit-llvm). I guess it is because this memcpy is not coming from the original source, but
2011 Mar 24
0
[LLVMdev] Instrumentation with liblto and gold
On 3/24/11 6:23 PM, Sangmin Park wrote: > Hi, > > I need advice in instrumenting programs using liblto and gold plugin. > Specifically, I added my pass in tools/lto/LTOCodeGenerator.cpp. > My pass inserts functions (myLoad and myStore) for some load and store > instructions. > The functions exist in a library file. > > I found that the approach works for the example in
2019 Jul 16
2
lld-link crash when build openssl with LTO
Yeah, it crashes indeed. I can reproduce the problem locally. Let me see what is going on. On Tue, Jul 16, 2019 at 9:00 PM Shi, Steven <steven.shi at intel.com> wrote: > In my previous test case, after add the `-fno-builtin` to clang then > build, the lld-link still has same crash as below: > > > > $ make > >
2012 Jun 08
2
[LLVMdev] How to use LLVM optimizations with clang
Hi Shahzad, > Is it possible that we can use LLVM optimization beside O1, O2, O3 > along with dragonegg plugin? sure, try this: gcc -fplugin=path/dragonegg.so ...other_options_here... -S -o - -fplugin-arg-dragonegg-emit-ir -fplugin-arg-dragonegg-llvm-ir-optimize=0 | opt -pass1 -pass2 ... Here -fplugin-arg-dragonegg-emit-ir tells it to output LLVM IR rather than target assembler.
2020 Feb 18
4
LLD doesn't handle globals with appending linkage
Hello. I'm posting this question here, because there seem to be no LLD-specific mailing list. Sorry in advance if this is wrong one. I compile two C source with following command: clang -flto -o %name.bc %name.c LLVM is augmented with my custom pass, which amongst other things create a global with appending linkage: @myvar = appending constant [1 x [1 x i8]*] ... I also have another pass
2019 Jul 16
2
lld-link crash when build openssl with LTO
lld should not crash in this case (so that's a bug that needs fixing), but setting it aside, did you try adding `-fno-builtin` to clang so that clang doesn't handle `memcpy` as a built-in function? On Tue, Jul 16, 2019 at 8:46 PM Shi, Steven <steven.shi at intel.com> wrote: > Hi Rui, > > For the test case in my previous email, if I change the `memcpy` to > `foobar` in
2019 Feb 28
4
lld-link crash when linking intrinsics lib
+Peter Collingbourne <pcc at chromium.org> LTO is used in this test case, and one source file defines its own `memset` function while the other file uses llvm.memset. Looks like LTO is confused by the user-defined memset. Could you take a look? Steven, Do you need to use LTO? I thought that LTO is a workaround to not produce an object file that cannot be handled by your ELF-to-COFF
2012 Jun 07
3
[LLVMdev] How to use LLVM optimizations with clang
Thanks alot Chad for quick response. Does this means that, we can not use LLVM optimizations except O1, O2, O3, O4 and unroll-loops with clang? One more thing I would like to know that If I want to process multiple modules with opt at the same time like opt -adce *.bc then how is it possible with opt in one go, if I process all the bytecode files within Makefile. Thanks. Shahzad On Thu, Jun
2012 Jul 04
1
[LLVMdev] About thread_local in 3.0
Hi LLVM, I am using 3.0, and I have a question about the __thread in c and thread_local in LLVM IR: O1-O4 and the final linked code behave differently. //////////////////////////////////// The following C code is from the LLVM testcase (SingleSource/UnitTests/Threads/2010-12-08-tls.c) #include <stdio.h> __thread int a = 4; int foo (void) { return a; } int main (void) {
2012 Jun 08
2
[LLVMdev] How to use LLVM optimizations with clang
Hi Shahzad, > I tried your method and it works fine. What would be the next step to > produce the final executable? I have tried the following but it is > producing an error > > $ gcc -fplugin=/path/to/dragonegg.so -S *.c > -fplugin-arg-dragonegg-emit-ir | opt -adce this won't work because you aren't passing the IR to opt (you need -o - for that if using a pipe) and you
2019 Jul 16
2
lld-link crash when build openssl with LTO
Hi Steven, One thing I noticed is that you are defining `memcpy`, which clang has an intrinsic with the same name. Can you try renaming it to a random name, like `foobar`, to see if the problem still exists? On Tue, Jul 16, 2019 at 10:10 AM Shi, Steven <steven.shi at intel.com> wrote: > I’ve submitted a BZ for this issue as below: > > > > Bug 42626 - lld-link crash when
2019 Jul 15
2
lld-link crash when build openssl with LTO
Hi Rui, We met a lld-link crash problem when build 32bits openssl1.0 with LTO in uefi firmware. We narrow down and figure out a simple test case to reproduce this problem as blow. Please advise. Thank you! $ cat main.c void TlsDriverEntryPoint () { unsigned char *ret = 0; const unsigned char cryptopro_ext[17] = {0x00,0x00,0x00,0x00,
2009 Dec 23
0
[LLVMdev] Problem while compling SPEC2000 with llvm-gcc
On 2009-12-23 08:22, Li Shengmei wrote: > > Hi, all > > I use llvm-gcc –O4 to compile SPEC 2000, some benchmarks > can’t be built successfully, such as 164.gzip, 175.vpr etc. > > The error messages are as follows. > > > > …… > > zh.o unlzw.o unpack.o unzip.o util.o zip.o -o gzip > > bits.o: file not recognized: File format not recognized