similar to: [LLVMdev] Linking library files using llvmc

Can the driver (llvmc) be built on win32?

Bram Adams wrote: > Hi, > > Op 14-aug-06, om 09:29 heeft Reid Spencer het volgende geschreven: > >> >>> Apparently, %llvmgccdir% and %llvmcc1% are not recognized as a useful >>> variable by the llvmc configuration parser. >> >> >> Actually, they are. See tools/llvmc/ConfigurationDriver.cpp around line >> 304. Also, they are recognized

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

Reid Spencer wrote: > 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

Hello, guys. I've tried to use llvmc to test optimization options but wasn't successful. Would you mind telling me what's wrong with this? ------------------------------------------------------------- $ llvmc chc_03.c -O3 -o chc_03 terminate called after throwing an instance of 'std::string' llvmc((anonymous namespace)::PrintStackTrace()+0x15)[0x8086091]

Thank you so much for your reply, Chris. If so, can I ask you two things more? First, is there any way to have various optimizations on LLVM assembly such as -O options in llvmc? llvm-gcc doesn't seem to be working for these -O options... Second, I'm still not sure about difference between *.s and *.ll. LLVM assembly *.s file can be made from llvm-gcc with -S option. Another

Hello All, On a Debian/AMD64 host I am surprised that there is apparently no way to generate position independent code in shared object (i.e. to output files which are easy dlopen-able without pain)? I probably missed something obvious, but what? I want to compile LLVM assembly source code -suitably generated- into .so as directly as possible... Regards -- Basile STARYNKEVITCH

On Mon, 22 Oct 2007, Basile STARYNKEVITCH wrote: > On a Debian/AMD64 host I am surprised that there is apparently no way to > generate position independent code in shared object (i.e. to output > files which are easy dlopen-able without pain)? > > I probably missed something obvious, but what? You're missing the fact that llvmc is highly experimental, and is not really usable

Hello, Since the old llvmc was removed, is it now OK to rename llvmc2 to llvmc? I'll update man pages accordingly.

On Nov 25, 2008, at 9:11 AM, Mikhail Glushenkov wrote: > Hello, > > Since the old llvmc was removed, is it now OK to rename llvmc2 to > llvmc? > I'll update man pages accordingly. yes please! -Chris

Greetings everybody! In my quest to attract more users to llvmc, I've added support for compilation via the Clang front-end (previously, only llvm-gcc was supported). This is enabled with the '-clang' switch; basically, you can now just alias 'ccc' to 'llvmc -clang' and get the same functionality. Examples: Compile via Clang: $ llvmc -clang test.c

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

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

The validator buildbot builds llvm-gcc and installs it in a non-standard location. It then reconfigures llvm with --with-llvmgccdir=<llvm-gcc_prefix> I see this code in llvmc/Base/Base.td: def llvm_gcc_c : llvm_gcc_based<"llvm-gcc -x c", "c", "i">; def llvm_gcc_cpp : llvm_gcc_based<"llvm-g++ -x c++", "c++", "i">; def

Hi Sanjiv, 2009/6/15 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > I configure llvm into a separate directory from source. > When I do the steps you mentioned in the source directory, this is what I > get. In that case, copy $LLVM_DIR/tools/llvmc/example/mcc16/Makefile to $LLVM_OBJ_DIR/tools/llvmc/example/mcc16/Makefile and build from that directory.

Hello, When I run llvm-gcc -emit-llvm hello.c -c -o hello.bc... what are the (default) passes that the driver is using? Where I can information about it? I want to examinate what are the sequences of passes that LLVM runs in each process. Thanks in advance, -- Juan Carlos -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Sanjiv, 2009/6/23 <Sanjiv.Gupta at microchip.com> > > > BTW, Chris's Makefile changes broke llvmc yesterday (r75379). I'm > > working on a fix. > > Hi Mikhail, > Did you get a chance to fix this. I still get errors while building examples. > This issue should be fixed now (r74001+). -- ()  ascii ribbon campaign - against html e-mail /\

Mikhail Glushenkov wrote: > Hi Sanjiv, > > 2009/6/23 <Sanjiv.Gupta at microchip.com> > >>> BTW, Chris's Makefile changes broke llvmc yesterday (r75379). I'm >>> working on a fix. >>> >> Hi Mikhail, >> Did you get a chance to fix this. I still get errors while building examples. >> >> > > This issue

Hi Sanjiv, 2009/6/29 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > I want to retrieve the value of argv[0] (which was passed to main function > of the driver) in PrependCustomizedPath. I've added a way to access argv[0] in hooks: http://thread.gmane.org/gmane.comp.compilers.llvm.cvs/50789 -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against