similar to: [LLVMdev] Possible solution to a llvm-ld bug

Reid Spencer wrote: > On Mon, 2006-02-27 at 20:43 -0800, Wink Saville wrote: > >>> Try passing "-L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend" to llvm-ld. >>> >> This didn't work for me: >> llvm-ld -o t1.app t1.bc t1.a -L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend.a >> >> I get two warning's about library 'crtend' missing

Chris Lattner wrote: > On Sun, 26 Feb 2006, Wink Saville wrote: >> I then do the following in my makefile: >> >> llvm-gcc -c t1.c -o t1.bc >> llvm-gcc -c t1sub1.c -o t1sub1.bc >> llvm-gcc -c t1sub2.c -o t1sub2.bc >> llvm-ar r t1.a t1sub1.bc t1sub2.bc >> llvm-ar: creating t1.a >> llvm-ld -o t1.app t1.bc t1.a /opt/llvm-1.6/llvm-gcc/lib/libcrtend.a

On Mon, 2006-02-27 at 20:43 -0800, Wink Saville wrote: > > Try passing "-L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend" to llvm-ld. > This didn't work for me: > llvm-ld -o t1.app t1.bc t1.a -L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend.a > > I get two warning's about library 'crtend' missing > You didn't get the instructions quite right. The option is

Misha Brukman wrote: > On Sun, Feb 26, 2006 at 10:00:18PM -0800, Wink Saville wrote: > > [snip] > If you're using -c, you're telling LLVM that there are other modules you > will link into the executable. Thus, LLVM does not know whether there > will be static ctors/dtors to run or not, so there's the call to > __main() from main. > > __main() gets

On Sun, 26 Feb 2006, Wink Saville wrote: > I then do the following in my makefile: > > llvm-gcc -c t1.c -o t1.bc > llvm-gcc -c t1sub1.c -o t1sub1.bc > llvm-gcc -c t1sub2.c -o t1sub2.bc > llvm-ar r t1.a t1sub1.bc t1sub2.bc > llvm-ar: creating t1.a > llvm-ld -o t1.app t1.bc t1.a /opt/llvm-1.6/llvm-gcc/lib/libcrtend.a > llvm-ld: warning: Cannot find library 'crtend'

Sanjiv Gupta wrote: > Nick Lewycky wrote: >> Sanjiv.Gupta at microchip.com wrote: >>> >>> >>> A common followup question is "but how do I link native libraries into >>> my .bc file". You don't. A .bc file is llvm ir, you can't put a native >>> binary library into a .bc (barring sticking it in as a string, etc). >>>

Hi, I am sending a patch to enable response file support in ParseCommandLineOptions. With this change, all llvm tools will support response file. This helps overcome the command line length limit which we encountered recently. Index: include/llvm/Support/CommandLine.h =================================================================== --- include/llvm/Support/CommandLine.h (revision 164408) +++

Sent from my iPhone > On May 30, 2016, at 4:52 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > >> On 30 May 2016 at 16:56, Mehdi Amini <mehdi.amini at apple.com> wrote: >> >> >> On 05/30/16 01:34 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >> >> We don't use cl::opt in gold, instead we parse the

Nick Lewycky wrote: > Sanjiv.Gupta at microchip.com wrote: >> >> >> A common followup question is "but how do I link native libraries into >> my .bc file". You don't. A .bc file is llvm ir, you can't put a native >> binary library into a .bc (barring sticking it in as a string, etc). >> >> The build then looks like: >> >>

Hi Sam, please add a testcase. Does this cause any regressions? Ciao, Duncan. > I am sending a patch to enable response file support in ParseCommandLineOptions. > With this change, all llvm tools will support response file. This helps overcome > the command line length limit which we encountered recently. > > Index: include/llvm/Support/CommandLine.h > >

And again... LLVM_BUILD_LLVM_DYLIB:BOOL=ON LLVM_LINK_LLVM_DYLIB:BOOL=ON This one is the good one... maybe. On Tue, Sep 6, 2016 at 11:35 PM, Alexandre Isoard < alexandre.isoard at gmail.com> wrote: > That is because I mistyped it: > LLVM_ENABLE_LLVM_DYLIB:BOOL=ON > LLVM_LINK_LLVM_DYLIB:BOOL=ON > > On Tue, Sep 6, 2016 at 11:31 PM, Wink Saville <wink at saville.com>

Well, although cl::ParseCommandLineOptions contains support for @file. By default it is disabled, which is the case for llvm-link. To enable @file support in llvm-link, a small change is needed: --- llvm-link.cpp.orig 2012-09-20 16:10:50.000000000 -0400 +++ llvm-link.cpp 2012-09-20 16:11:24.000000000 -0400 @@ -83,7 +83,7 @@ LLVMContext &Context = getGlobalContext();

Response file is the conventional name for files serving this purpose. A google search shows the usage of "response file" is not rare. Also it has been used in the LLVM documentation: http://llvm.org/docs/CommandLine.html#response-files Sam -----Original Message----- From: Matt Beaumont-Gay [mailto:matthewbg at google.com] Sent: Tuesday, October 02, 2012 1:35 PM To: Liu, Yaxun (Sam)

I've updated the arch linux bug (https://bugs.archlinux.org/task/50385) with a patch for glibc in the arch linux packages that does fix the segment fault for me. On Mon, Sep 12, 2016 at 2:08 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 12 September 2016 at 22:02, Wink Saville <wink at saville.com> wrote: >> I then cloned the gcc 2.24 sources as of today and

Hello, Last night I checked out the head of CVS and tried to compile after configuring with: ./configure --enable-debug-runtime --enable-jit --prefix=/opt/lvm-cvs I then got a message indicating that Line 1099 of Makefile.rules has 8 leading spaces instead of a tab, I fixed that and then the build completed, although there were 6 warnings (http://www.saville.com/llvm/make1.out). Reid

With the new signature file I was able to verify, but there was still a bad signature: "gpg: key 0x0FC3042E345AD05D: 1 bad signature" which I highlighted below. Didn't seem to be a problem, but thought I'd point it out. I'd be glad to do additional tests if you'd like. $ gpg --list-keys /home/wink/.gnupg/pubring.kbx ----------------------------- pub

Thanks Chris for the comment. Since there is no objection, I attached a new patch which enables response file support and removes the argument for controlling/disabling response file support. The patch also contains a simple test. I did regression check and there are no regressions. + llvmdev Sam From: Chris Lattner [mailto:clattner at apple.com] Sent: Sunday, September 30, 2012 2:20 PM To:

Could we enable ReadResponseFiles=true by default? 2012/9/21 Liu, Yaxun (Sam) <Yaxun.Liu at amd.com>: > Well, although cl::ParseCommandLineOptions contains support for @file. By default it is disabled, which is the case for llvm-link. > > To enable @file support in llvm-link, a small change is needed: > > --- llvm-link.cpp.orig 2012-09-20 16:10:50.000000000 -0400 > +++

Can we call this a "parameters file"? I find "response file" to be non-obvious. On Tue, Oct 2, 2012 at 8:18 AM, Liu, Yaxun (Sam) <Yaxun.Liu at amd.com> wrote: > Thanks Chris for the comment. > > > > Since there is no objection, I attached a new patch which enables response > file support and removes the argument for controlling/disabling response >

On Sun, Feb 26, 2006 at 10:00:18PM -0800, Wink Saville wrote: > Thanks for the info, you've confirmed what I was trying to do, but when > I compile: [snip] > without "-c" (llvm-gcc t1.c -o t1) the dissassembled bytecode does not > call __main: __main() is used to run static constructors and destructors, so if you're compiling without -c, LLVM knows all the files