search for: libstd

Consider the example command line below $ llvm-ld -disable-opt hello.bc -l std -o hello.out Why does -disable-opt links in all the bitcode from the libstd.so into hello.out? - Sanjiv

On Wed, Jul 15, 2009 at 9:32 AM, sanjiv gupta<sanjiv.gupta at microchip.com> wrote: > Consider the example command line below > > $ llvm-ld -disable-opt hello.bc -l std -o hello.out > > Why does -disable-opt links in all the bitcode from the libstd.so into > hello.out? ... because it just disables optimization passed. It does not disable linking. ? - Devang

...wrote: > On Wed, Jul 15, 2009 at 9:32 AM, sanjiv gupta<sanjiv.gupta at microchip.com> wrote: > > Consider the example command line below > > > > $ llvm-ld -disable-opt hello.bc -l std -o hello.out > > > > Why does -disable-opt links in all the bitcode from the libstd.so into > > hello.out? > > ... because it just disables optimization passed. It does not disable linking. > ? > - > Devang > ______ I think I did not explain the question really well. -disable-opt links the whole lib into the final program while not using -disable-opt lin...

...format and link my programs .bc with them via llvm-ld to generate a linked .bc again. I have created a std.lib using llvm-ld -link-as-library on all .bc files of std libs. How to use -l and -L options of llvm-ld in that case? What are the other required options? What are the naming conventions? libstd.a ( for -l std)? - Sanjiv

...Jul 15, 2009 at 9:32 AM, sanjiv gupta<sanjiv.gupta at microchip.com> wrote: >> > Consider the example command line below >> > >> > $ llvm-ld -disable-opt hello.bc -l std -o hello.out >> > >> > Why does -disable-opt links in all the bitcode from the libstd.so into >> > hello.out? >> >> ... because it just disables optimization passed. It does not disable linking. >>  ? >> - >> Devang >> ______ > I think I did not explain the question really well. > > -disable-opt links the whole lib into the final...

...would be enough. I didn't build again, but I did configure with the settings posted yesterday, and there's a warning which I'm unsure how to interpret and if it's a concern: --- CMake Warning at tools/lldb/cmake/modules/LLDBConfig.cmake:409 (message): You appear to be linking to libstdc++ version lesser than 4.9 without exceptions enabled. These versions of the library have an issue, which causes occasional lldb crashes. See <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59656> for details. Possible courses of action are: - use libstdc++ version 4.9 or newer...

I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 right near the end of compiling llvm-gcc in valarray-inst.cc. assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow scaling by ESP" Does this build on Linux ? My remote Linux box has died and not a ble to reset it for a day or two. /home/ang/build/l...

This looks like pr4572. Evan On Jul 27, 2009, at 3:25 AM, Aaron Gray wrote: > I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 > right near the end of compiling llvm-gcc in valarray-inst.cc. > > assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow > scaling by ESP" > > Does this build on Linux ? > > My remote Linux box has died and not a ble to rese...

...ld again, but I did configure with the settings posted > yesterday, > and there's a warning which I'm unsure how to interpret and if it's a > concern: > > --- > CMake Warning at tools/lldb/cmake/modules/LLDBConfig.cmake:409 (message): > You appear to be linking to libstdc++ version lesser than 4.9 without > exceptions enabled. These versions of the library have an issue, which > causes occasional lldb crashes. See > <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59656> for details. > Possible > courses of action are: > > - use...

On Tue, Dec 20, 2016 at 11:05 AM, Carsten Mattner <carstenmattner at gmail.com> wrote: > On Tue, Dec 20, 2016 at 5:05 PM, Teresa Johnson <tejohnson at google.com> > wrote: > > Hi Carsten, > > > > A few responses below, but first, can you get the link command for > > lldb.so.3.9.1? Last time it was the lldb.so build that was using > > ld.bfd with the