Displaying 20 results from an estimated 700 matches similar to: "[LLVMdev] compiling the tutorial"
2008 Nov 21
1
[LLVMdev] compiling the tutorial
Óscar Fuentes ha scritto:
> Carlo Alberto Ferraris <cafxx at strayorange.com> writes:
>
>> Hi,
>> I'm investigating adding LLVM JIT support to a project of mine, but I'm
>> having issues when trying to compile the Kaleidoscope tutorial* under
>> MSVC 2008.
>> In particular, the problem is that in main() when this line is executed
>>
2008 Nov 20
0
[LLVMdev] compiling the tutorial
Carlo Alberto Ferraris <cafxx at strayorange.com> writes:
> Hi,
> I'm investigating adding LLVM JIT support to a project of mine, but I'm
> having issues when trying to compile the Kaleidoscope tutorial* under
> MSVC 2008.
> In particular, the problem is that in main() when this line is executed
>> // Create the JIT.
>> TheExecutionEngine =
2008 Feb 21
3
[LLVMdev] LLVM Win32 Issue
Hello all,
I'm trying to bring an LLVM-based project that is working on Linux up
on Win32. I am having problems with llvm::ExecutionEngine::create
returning a NULL. I traced it to these lines:
// Unless the interpreter was explicitly selected, try making a JIT.
if (!ForceInterpreter && JITCtor)
EE = JITCtor(MP, ErrorStr);
// If we can't make a JIT, make an
2008 Feb 21
0
[LLVMdev] LLVM Win32 Issue
"Aaron Dwyer" <llvmification at gmail.com> writes:
[snip]
> JITCtor and InterpCtor are both NULL, so it's obvious why I'm getting
> back a NULL execution engine. I am pretty sure it's because I'm
> missing a few llvm .lib or .obj files. What is the set of llvm object
> files needed at link time for Win32 on X86 JIT?
This is what I use on MinGW. It
2009 Sep 23
1
[LLVMdev] [PATCH] Set error message if JIT/Interpreter not linked in.
Hi,
In ExecutionEngine.cpp, when the JIT or the Interpreter have not been
linked in then EngineBuilder::create fails without setting ErrorStr.
I've attached a patch to fix this.
Warm Regards
KS Sreeram
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ee-not-linked-in-msg.diff
URL:
2009 Jun 23
3
[LLVMdev] X86 JIT
On Mon, Jun 22, 2009 at 4:43 PM, Chris Lattner <clattner at apple.com>
wrote:
>
> On Jun 22, 2009, at 2:19 PM, Kasra wrote:
>
> Hi,
>
> for some reason I could not get the machine code generator for x86
> working. The interpreter is the only thing that works, is there
> anything that I am missing here?
>
> This recently changed. In your main program, please
2012 Aug 09
1
[LLVMdev] question about ExectuionEngine::Create
I found the following problem when I try to debug "target does not support
mc emission" in linux (the same code executes OK in windows):
Below is a snippet extracted from this method,
if (UseMCJIT && ExecutionEngine::MCJITCtor) {
ExecutionEngine *EE =
ExecutionEngine::MCJITCtor(M, ErrorStr, JMM, OptLevel,
2010 Jan 22
3
[LLVMdev] Kaleidoscope-tutorial: Fails to create the JIT
Hello All
I 'm studing LLVM/Clang and trying to follow the Kaleidoscope tutorial
(Release 2.6 version).
I found some minir docu-bugs and added them to Bugzilla.
However, Now I found a show-stopper for me, the toy (v4) demo does
build, but does crash, on any input. Even a simpe ';'!
Looking into the (demo-code) found the that the JIT can't be build/
created,/loaded/...
Which
2010 Jan 22
0
[LLVMdev] Kaleidoscope-tutorial: Fails to create the JIT
On Fri, Jan 22, 2010 at 1:56 PM, ALbert Mietus <albert at ons-huis.net> wrote:
> Hello All
>
> I 'm studing LLVM/Clang and trying to follow the Kaleidoscope tutorial
> (Release 2.6 version).
> I found some minir docu-bugs and added them to Bugzilla.
>
> However, Now I found a show-stopper for me, the toy (v4) demo does
> build, but does crash, on any input. Even a
2009 Jun 22
0
[LLVMdev] X86 JIT
On Jun 22, 2009, at 2:19 PM, Kasra wrote:
> Hi,
>
> for some reason I could not get the machine code generator for x86
> working. The interpreter is the only thing that works, is there
> anything that I am missing here?
This recently changed. In your main program, please #include "llvm/
Target/TargetSelect.h" and call InitializeNativeTarget(); before
setting up
2010 Jan 23
2
[LLVMdev] Kaleidoscope-tutorial: Fails to create the JIT
I ask for advice, for TheExecutionEngine === NULL,
>> Which result's in a null-pointer for "TheExecutionEngine"; which
>> explains the bus-errror ..
Reid Kleckner wrote:
> Try changing the above line to:
> std::string str;
> TheExecutionEngine =
> EngineBuilder(OurModuleProvider).setErrorStr(str).create();
> cout << str << '\n';
2009 Jun 22
2
[LLVMdev] X86 JIT
Hi,
for some reason I could not get the machine code generator for x86 working. The interpreter is the only thing that works, is there anything that I am missing here?
-- Kasra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090622/89dca208/attachment.html>
2010 Jan 23
0
[LLVMdev] Kaleidoscope-tutorial: Fails to create the JIT
Look at what is in <llvm source root>/examples/Kaleidoscope/toy.cpp.
This is the final version of the tutorial and worked the last time I played with 2.6.
Garrison
On Jan 23, 2010, at 12:21, ALbert Mietus wrote:
> I ask for advice, for TheExecutionEngine === NULL,
>
>>> Which result's in a null-pointer for "TheExecutionEngine"; which
>>> explains
2008 Dec 02
1
[LLVMdev] Kaleidoscope tutorial failed at Chapter 4...
Hi everyone. I am using LLVM 2.4 release to practise the tutorial at
Kaleidoscope Chapter 4.
I built the LLVM library, and created my own project, and then paste the
code from the tutorial into my own project. Then after compiled and built
it, I passed the built stage. (I am using visual studio 2005 )
However, when I tried to input some code in the command line window, the
sample program crashed.
2010 Feb 17
2
[LLVMdev] Kaleidoscope toy4 failure seg fault on llvm::ExecutionEngine::getTargetData (this=0x0)
I am new to llvm so I might be missing a critical step. My system is
Fedora 12 but this also happens in Mac OS X 10.6.2. Here are the
steps I used to compile llvm:
export TARGETS=x86,x86_64,cpp
export INSTALLDIR=/home/rovitotv/llvm
../llvm-2.6/configure --prefix=$INSTALLDIR --enable-bindings=none
--enable-targets=$TARGETS --enable-optimized
--with-llvmgccdir=$INSTALLDIR
2010 Jan 23
2
[LLVMdev] Kaleidoscope-tutorial: Fails to create the JIT
--Groetjes, Albert
ALbert Mietus
GSM: +316 16 531 258
Send prive mail to: ALbert at ons-huis dot net
Don't send spam mail!
Mijn missie: http://SoftwareBeterMaken.nl product, proces & imago.
Mijn leven in het kort: http://albert.mietus.nl/Doc/CV_ALbert.html
On 23 Jan 2010., at 22:07, Garrison Venn wrote:
> Look
2010 Nov 15
6
[LLVMdev] Optimization of calls to functions without side effects (from Kaleidoscope example)
I'm using the gvn pass, not sure about basic-aa.
I've copied the code as-is from http://llvm.org/docs/tutorial/LangImpl4.html#code and added "F->addFnAttr( Attribute::ReadOnly )" after "Function *F = Function::Create(FT, Function::ExternalLinkage, Name, TheModule)".
The passes it sets up are:
// Set up the optimizer pipeline. Start with registering info about
2010 Feb 17
0
[LLVMdev] Kaleidoscope toy4 failure seg fault on llvm::ExecutionEngine::getTargetData (this=0x0)
First, you have to call llvm-g++ to use the llvm-gcc front end, but it
doesn't matter here.
I'd like to suggest that you use pastebin to put your code and the send us
the link, so that we can download it. The problem is that TheExecutionEngine
is set to NULL (maybe because of a previous error), but it will be really
better if you use pastebin.
On Wed, Feb 17, 2010 at 6:01 AM, Todd Rovito
2011 Nov 04
2
[LLVMdev] Question on JIT optimizations
Hi,
If hope this is the right list to post a question like this. If not,
my apologies -- please redirect me.
Following the Kaledoscope example I am trying to write a simple JIT and
compile my own small language using LLVM. Compilation happens using the
C++ api by constructing a VM and emitting code using the api (just as the
Kaledoscope example).
The code in this setup will be optimized
2008 Feb 04
0
[LLVMdev] Exception handling in JIT
Looks sane. Thanks.
Evan
On Feb 1, 2008, at 1:24 AM, Nicolas Geoffray wrote:
> Dear all,
>
> Here's a new patch with Evan's comments (thx Evan!) and some cleanups.
> Now the (duplicated) exception handling code is in a new file:
> lib/ExecutionEngine/JIT/JITDwarfEmitter.
>
> This patch should work on linux/x86 and linux/ppc (tested).
>
> Nicolas
> Index: