similar to: [LLVMdev] llvmc issues on x86_32

Hi, > According to the FAQ llvmc is considered experimental/unsupported. But > FWIW, here's an issue I found while trying to use it on 32 bit x86 systems. I am the primary maintainer of llvmc. First of all, thanks for your bug report. > tools/llvmc/plugins/Base/Base.td hardcodes the -relocation-model=pic > option into invocations of llc: This part was copied verbatim from the

Mikhail Glushenkov wrote: > I removed the '-relocation-model' bit from the default invocation > string for llc. To pass arguments to llc, use the new "-Wllc" > option. I'd say that this is the proper solution, even though it breaks backward compatibility on x86_64. But given that llvmc is still considered experimental, better do it now than later. ;-) Thanks a lot

Hi, I encountered an issue with inline assembly in my c files compiled with llvmc. When I have a push instruction in the inline assembly like: __asm__ volatile ( "push {r4}\n\t" ); the compiler will drop the curly braces and leave it in the generated assembly file as: push r4 And this is non-conformant with the ARM

Hi Sanjiv, Sanjiv Gupta <sanjiv.gupta <at> microchip.com> writes: > The salient features that we want to have in the driver are: > [...] As promised, I've implemented a basic compiler driver for the PIC16 toolchain. It's under tools/llvmc/examples/mcc16. Some examples illustrating the features you requested: > 2. If the user has specified to generate the final

> I'll be happy to answer any further questions you may have, feel free to e-mail > me directly (though right now our mail server is down) > The salient features that we want to have in the driver are: 1. llvm-ld will be used as "The Optimizer". 2. If the user has specified to generate the final executable, then llvm-ld should run on all the .bc files generated by clang

Mikhail Glushenkov wrote: > > Hi Sanjiv, > > Sanjiv Gupta <sanjiv.gupta <at> microchip.com> writes: > > > The salient features that we want to have in the driver are: > > [...] > > As promised, I've implemented a basic compiler driver for the > PIC16 toolchain. It's under tools/llvmc/examples/mcc16. > Hi Mikhail, How do you build mcc16

Hi, On Sat, Sep 5, 2009 at 9:12 PM, Sanjiv Gupta<sanjiv.gupta at microchip.com> wrote: > Is the patch below ok? > > Index: LLVMCConfigurationEmitter.cpp > =================================================================== > --- LLVMCConfigurationEmitter.cpp    (revision 80668) > +++ LLVMCConfigurationEmitter.cpp    (working copy) > @@ -1141,6 +1141,7 @@ >          

Albert Graef <Dr.Graef <at> t-online.de> writes: > I'd say that this is the proper solution, even though it breaks backward > compatibility on x86_64. But given that llvmc is still considered > experimental, better do it now than later. A better solution probably would be to add '-relocation-model=pic' only when we are on x86_64. There is no easy way to access

Hi all, In the good old llvmc, the -Wo flag could be used to pass arguments to the optimizer. Is there a similar mechanism anywhere for clang? Is there also a similar mechanism to -Wllc? Thanks! Harel Cain -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120304/0e5c7267/attachment.html>

Looks like a problem with llvmc. Your example works fine with clang. ~/tmp $ cat foo.c void foo() { __asm__ volatile ("push {r4}\n\t"); } gilgamesh: ~/tmp $ clang -target arm-linux-eabi -S -Os foo.c -o - .syntax unified .eabi_attribute 20, 1 .eabi_attribute 21, 1 .eabi_attribute 23, 3 .eabi_attribute 24, 1 .eabi_attribute 25, 1 .file "foo.c" .text .globl foo

Thanks, but I'm not sure I understand. I see no such flag in clang 2.9 nor couldn't I find any mention of it. What does it do? Harel Cain On Sun, Mar 4, 2012 at 15:03, Anton Korobeynikov <anton at korobeynikov.info>wrote: > > In the good old llvmc, the -Wo flag could be used to pass arguments to > the > > optimizer. Is there a similar mechanism anywhere for clang?

> In the good old llvmc, the -Wo flag could be used to pass arguments to the > optimizer. Is there a similar mechanism anywhere for clang? Is there also a > similar mechanism to -Wllc? -mlvm will handle all of them -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Jeffrey Yasskin wrote: > See Owen's email about docs for the 2.6 release, but it's really not > that hard to keep up with trunk. I recently merged trunk LLVM into > Unladen Swallow, and the changes I needed to make are at > http://code.google.com/p/unladen-swallow/source/detail?r=724. Thanks Jeffrey, that was really very helpful! I have Pure working with both the LLVM 2.6

I am getting this error while using the command "llvmc -O3 -Wall hello.cpp" where hello.cpp is some cpp file on my machine. llvmc is the driver calling a bunch of tools like llvm-g++, opt, llc etc. I think the llvmc tool could not probably locate the llvm-g++ tool. I would like to know where should I specify the path to llvm-g++ for llvmc to find them. Also can someone give me the link

Hi, After building llvm with clang the llvmc tests are failing with: llvmc: Node llc is not in graph Anyone else see this ? (TOT llvm & clang) -Argiris

Hi, Is it intended that llvmc should search PATH for llc? For example, this means that llvmc 2.7 can invoke llc 2.8: % echo $PATH /home/jdenny/installs/llvm/2.8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games % /home/jdenny/installs/llvm/2.7/bin/llvmc test.ll llc: Unknown command line argument '-f'. Try: 'llc -help' % strace -f

Hi, Apparently there are two bugs in tools/llvmc/c: /.../llvm/tools/llvmc/c:12: Error: Invalid top level configuration item /.../llvm/tools/llvmc/c:28: Error: Expecting a program name /.../llvm/tools/llvmc/c had 2 errors. Terminating. The first error relates to the following line(s): lang.libs=%llvmgccdir%/lib %llvmgccdir%/lib \ %llvmgccdir%/lib/gcc/%llvmgccarch% ... the other one to:

On Thu, 2006-08-17 at 08:55 -0700, Scott Michel wrote: > Regarding llvmc there is one small problem: with the gcc 4.0 frontend, > "-emit-llvm" needs to be added to all of the translator.command lines. > Not entirely sure how to conditionalize that in the configuration files. Hi Scott, What is needed is a complete overhaul of the configuration mechanism. We have plans to

Without this patch, opt is never called for llvm-assembly (.ll) files when "-opt" is passed to llvmc: $ llvmc -clang -v test.ll llc -f -O2 test.ll -o /tmp/llvm_gvO2nK/test.s as /tmp/llvm_gvO2nK/test.s -o /tmp/llvm_gvO2nK/test.o llvm-ld -native -disable-internalize /tmp/llvm_gvO2nK/test.o -o a.out $ llvmc -clang -opt -v test.ll llc -f -O2 test.ll -o /tmp/llvm_2xiL86/test.s as

Hi Sanjiv, 2009/6/18 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > Hi Mikhail, > Thanks for your wonderful help so far. I have few more questions to ask: > > How do I modify the driver to pick tools from where the driver itself > resides, rather than from the PATH? > Do I need to write some C++ code to customize such behaviors? Yes, this is what hooks are for.