similar to: [LLVMdev] llvmc now supports Clang

Hi, I am trying to build my own llvmc plugin, but somehow, the llvm makefiles do not pick up the plugin in the llvmc/plugins directory anymore in a recent (r129445) svn checkout. According to the tutorial (http://llvm.org/docs/CompilerDriverTutorial.html): $ cd tools/llvmc $ cp -r example/Simple plugins/Simple $ make LLVMC_BASED_DRIVER_NAME=mygcc LLVMC_BUILTIN_PLUGINS=Simple does not build

WikiFormatting for code documentation? :-) -scooter On Tue, Dec 9, 2008 at 7:56 AM, Mikhail Glushenkov <foldr at codedgers.com>wrote: > [Chris asked me to bring this up on the mailing list some time > ago, but I couldn't get to it. Sorry for that.] > > Since the beginning, I used ReST [1] for documenting llvmc, instead of > plain HTML that was used historically. In my

Hi Mikhail, On Thu, 28 Oct 2010, Mikhail Glushenkov wrote: > Joel E. Denny <jdenny <at> etinternational.com> writes: > > Is it intended that llvmc should search PATH for llc? For example, this > > means that llvmc 2.7 can invoke llc 2.8: > > [...] > > This is fixed in 2.8+ - llvmc now searches the directory it resides in first. I just built r117553 from

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, Argyrios Kyrtzidis <kyrtzidis <at> apple.com> writes: > > 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) It looks like this is due to a bug in clang: // file1.cpp namespace { class Plugin { }; } // file2.cpp namespace { class Plugin {

On Aug 12, 2010, at 11:04 PM, Mikhail Glushenkov wrote: > Argyrios Kyrtzidis <kyrtzidis <at> apple.com> writes: > >> >> 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) > > It looks like this is due to a

Mikhail Glushenkov wrote: > Hi Sanjiv, > > 2009/6/15 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > >> Hi Mikhail, >> How do you build mcc16 executable? >> > > This should work: > > $ cd $LLVM_DIR/tools/llvmc/examples/mcc16 > $ make > > I configure llvm into a separate directory from source. When I do the steps you mentioned in

[Chris asked me to bring this up on the mailing list some time ago, but I couldn't get to it. Sorry for that.] Since the beginning, I used ReST [1] for documenting llvmc, instead of plain HTML that was used historically. In my opinion, ReST is much easier to write and read (in the text editor or on terminal); it can also be used to produce PDFs, man pages or HTML that looks exactly the same

Hi, On Thu, Oct 28, 2010 at 01:28:47PM -0400, Joel E. Denny wrote: > Hi Mikhail, > > On Thu, 28 Oct 2010, Mikhail Glushenkov wrote: > > > Joel E. Denny <jdenny <at> etinternational.com> writes: > > > Is it intended that llvmc should search PATH for llc? For example, this > > > means that llvmc 2.7 can invoke llc 2.8: > > > [...] > >

> 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. i00202 at ubuntu:~/projects/llvm/tools/llvmc/example/mcc16$ make make[1]: Entering directory `/home/i00202/projects/llvm/tools/llvmc/example/mcc16/plugins' make[2]: Entering directory

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? And how to make sure that we have same behavior on Windows as far as paths (/ Vs \) and picking up tools from the driver directory is concerned? Do I need to write some C++ code to customize such

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

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 Sanjiv, 2009/6/15 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > Hi Mikhail, > How do you build mcc16 executable? This should work: $ cd $LLVM_DIR/tools/llvmc/examples/mcc16 $ make If you're building from some other dir, you'll need to update mcc16/Makefile, so it knows where Makefile.common is located. > There are so many confusing things there: driver, plugins,

Hi, Joel E. Denny <jdenny <at> etinternational.com> writes: > > Hi, > > Is it intended that llvmc should search PATH for llc? For example, this > means that llvmc 2.7 can invoke llc 2.8: > [...] This is fixed in 2.8+ - llvmc now searches the directory it resides in first.

Hi Aaron, Aaron Gray <aaronngray.lists <at> googlemail.com> writes: > I sent you a _patch_ that disables it on Cygwin for the time being. LLVM > does not load DLL's properly apparently. I would love to get to the bottom > of this at some point. I've just added an --enable-llvmc-dynamic configure option (enabled only on Windows by default). This is based on your

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

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.

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. tools/llvmc/plugins/Base/Base.td hardcodes the -relocation-model=pic option into invocations of llc: def llc : Tool< [(in_language "llvm-bitcode"), (out_language "assembler"), (output_suffix "s"), (cmd_line

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.