similar to: [LLVMdev] [llvm-gcc][patch] Use LDFLAGS from configure

> Makes sense to me. If you built with and without LDFLAGS enabled > should probably just commit it - or do you need someone to commit for > you? I can commit it. I was just not sure if this was an intentional difference. I am running a bootstrap without a LDFLAGS. Will commit if it pass. > -eric > _______________________________________________ > LLVM Developers mailing list

2008/7/23 Duncan Sands <baldrick at free.fr>: > My nightly tester on x86_64-unknown-linux-gnu failed > to bootstrap llvm-gcc today: > > Comparing stages 2 and 3 > Bootstrap comparison failure! > ./build/read-rtl.o differs I am having the same problem. It was "introduced" by revision 54811, so it looks like a memory corruption problem. Investigating. > The

Yes,it's indeedly the correct one,and new ld can also support -plugin option,I don't know the reason of the trouble, 2009/9/17 Rafael Espindola <espindola at google.com> > > llvm-gcc -use-gold-plugin a.a b.o -o hello > > > > which is similar with the example in the document,it tells me that > > libLLVMgold.so can not be found ,but I truly put it in the

For some time now the gold linker has support for plugins and llvm has a plugin for it. Unfortunately, it was still not possible to do fully transparent LTO on linux because ar had no support for plugins and a library created with llvm files in it would have no symbol table and would be rejected by gold. Today support for plugins has been committed to BFD. That is the file format abstraction

Hello, I am trying to bootstrap on ARM linux EABI using a qemu chroot to better test my changes on at least one more architecture. I am using the following configure line: ../gcc/configure --prefix=/home/espindola/install/ --program-prefix=llvm- --enable-languages=c --disable-shared --disable-multilib --enable-llvm=/home/espindola/build --enable-checking arm-linux-gnueabi The bootstrap fails

> I propose that structures that are passed on registers should be slip > into many DAG level arguments (for now this would be all structs) and > the DAG should contain copies instead of loads. The nice thing about > this proposal is that for structures that are passed on the stack, the > DAG doesn't need to know the size. All that we need to add to add to > the DAG is a flag

Rafael, Remember that the qemu <= 0.9.0 can misexecute code compiled by LLVM. I think you should test using qemu CVS. Lauro 2007/11/2, Rafael Espindola <espindola at google.com>: > Hello, > > I am trying to bootstrap on ARM linux EABI using a qemu chroot to > better test my changes on at least one more architecture. > > I am using the following configure line: >

On 21/01/2008, Arvind Ayyangar <arvind.ayyangar at gmail.com> wrote: > Hi, > I am new to LLVM and have been trying to get it working on > scratchbox (ARM target). When I try to build llvm-2.1, the build > freezes with the following output.. > I have build llvm inside scratchbox sometime ago. More recently Lauro pointed out that one should use a patched qemu. Not sure

I have been playing a bit with LLVM again and it looks like the current major missing feature on Linux x86-64 is PIC. Is anyone working on it? If not, I would like to do so. I have the ABI documentation (http://www.x86-64.org/documentation/abi.pdf), but would be glad if someone had some LLVM specific pointers. For example, from the targets that do have support for PIC, which one is the one to be

On 27/07/07, Evan Cheng <evan.cheng at apple.com> wrote: > Code generator shouldn't introspect the LLVM type at all, except to > get the size of the type. Anything needed should be encoded by the > front-end. In the short term, please focus on getting parity with > what we already have. This means x86-64 will be wrong, but it > already is. As a second step we can then

> This does not bound us to any particular size promotion. The solution is generic enough to address all possibilities (of course new attributes may be needed) We are both trying to do the same, I just don't see why this can't be done completely in llvm-gcc or clang. Do you have an C example where we currently do sign extension and that we would be able to avoid it with your proposal?

> llvm-gcc -use-gold-plugin a.a b.o -o hello > > which is similar with the example in the document,it tells me that > libLLVMgold.so can not be found ,but I truly put it in the directory > which is the same as the cc1's. > > What's the problem with my libLLVMgold.so's position? That looks correct. Can you check that *) It is the correct cc1 :-) (run llvm-gcc with

2009/9/17 Nan Zhu <zhunansjtu at gmail.com>: > Yes,it's indeedly the correct one,and new ld can also support -plugin > option,I don't know the reason of the trouble, Does ld actually work if you pass libLLVMGold.so to it? Try to link with llvm-gcc without the -use-gold-plugin option and with -v (it will fail as expected). Copy the collect2 line and add the -plugin line. If

In order to the code generators to lower functions arguments that have the "byval" attribute, they would have to access the original argument Type. For example, on linux x86_64 {i64, i64} should be passed on registers and {i64, i64, i64} goes on the stack. The problem is that when looking at (for example) FORMAL_ARGUMENTS, the only thing that is present is the type of the pointer itself

That's pretty awesome! Will ar, etc. eventually get some autodiscovery of plugins so that things work OOTB after a make install of llvm/llvm-gcc? - Daniel On Tue, May 26, 2009 at 10:52 AM, Rafael Espindola<espindola at google.com> wrote: > For some time now the gold linker has support for plugins and llvm has > a plugin for it. > > Unfortunately, it was still not possible

2009/7/12 Daniel Dunbar <daniel at zuster.org>: > That's pretty awesome! Thanks! > Will ar, etc. eventually get some autodiscovery of plugins so that > things work OOTB after a make install of llvm/llvm-gcc? The bfd library (used by ar and nm) already searches for plugins in $install_dir/lib/bfd-plugins/. Maybe we could pass an option to llvm's configure to tell it where

On May 26, 2009, at 10:52 AM, Rafael Espindola wrote: > Today support for plugins has been committed to BFD. That is the file > format abstraction library used by binutils. This now works Very nice Rafael! Can you please update the web page to mention this, e.g. in the LinkTimeOptimization.html document and wherever else relevant? -Chris > > $ llvm-gcc -emit-llvm -O2 -c a.c

> I am having the same problem. It was "introduced" by revision 54811, > so it looks like a memory corruption problem. Investigating. Interesting. Bootstrapping with gcac works! Some tests with valgrind also work. My next try is to add some debug code to do bounds checking in SmallVector. Cheers, -- Rafael Avila de Espindola Google | Gordon House | Barrow Street | Dublin 4 |

>    git clone git://github.com/earl/llvm-mirror.git llvm >    cd llvm >    git config --add remote.origin.fetch '+refs/remotes/*:refs/remotes/*' >    git fetch >    git svn init https://llvm.org/svn/llvm-project/llvm/trunk >    git svn rebase --local This one worked perfectly. Thanks! I tried the same with the llvm-gcc-4.2 mirror, but "git svn rebase --local"

Code generator shouldn't introspect the LLVM type at all, except to get the size of the type. Anything needed should be encoded by the front-end. In the short term, please focus on getting parity with what we already have. This means x86-64 will be wrong, but it already is. As a second step we can then worry about x86-64-specific param attributes that should be added to handle