Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Access violation in Kaleidoscope Chapter 4"
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.
2009 Mar 25
0
[LLVMdev] LLVM and GMP
I could be wrong, but I think that you may need to add a 'big-integer'
intrinsic type to llvm.
On Wed, Mar 25, 2009 at 4:32 AM, Paulo Matias <paulomatias0 at gmail.com> wrote:
> Hello
>
> I've been looking to LLVM, in order to develop a compiler for a
> cryptography oriented language. I started by following the tutorials on
> Kaleidoscope, and I must say they were
2009 Mar 25
3
[LLVMdev] LLVM and GMP
Hello
I've been looking to LLVM, in order to develop a compiler for a
cryptography oriented language. I started by following the tutorials on
Kaleidoscope, and I must say they were very usefull. Now I need to use
GMP, so i can add Big Integer support. I am trying to change
Kaleidoscope to support BigIntegers instead of doubles, but I don't
really know how to do that. I'd really
2009 Jun 17
0
[LLVMdev] Segmentation fault - Kaleidoscope
FWIW, I'm also suddenly experiencing segfaults in code that used to work
a few days ago (I'm using svn). This may be unrelated to the problem
described below, but perhaps it's the same thing.
In my case it seems that creating an ExecutionEngine has changed. I used
to do
Module* Mod = makeLLVMModule(); // basically create a gcd function
verifyModule(*Mod,
2010 Feb 17
1
[LLVMdev] Kaleidoscope toy4 failure seg fault on llvm::ExecutionEngine::getTargetData (this=0x0)
On Wed, Feb 17, 2010 at 6:29 AM, Conrado Miranda
<miranda.conrado at gmail.com> wrote:
> First, you have to call llvm-g++ to use the llvm-gcc front end, but it
> doesn't matter here.
I got the compile command from the Kaleidoscope documentation.
> 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
2009 Jun 17
3
[LLVMdev] Segmentation fault - Kaleidoscope
Hello,
Following the tutorial "Kaleidoscope: Adding JIT and Optimizer Support", I
found a Segmentation fault when I try to execute it. I am new in the
neighbourhood, so I don't know what is wrong. Could you help me with that?
I am working with the last version of LLVM (2.5). The code in chapter 2 and
3 works good, but the code in the chapter 4 did not work.
Below are the detail of
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
2016 Apr 01
0
Kaleidoscope on Windows - bug maybe found?
Addendum: this still fails:
auto ExprSymbol = J.findSymbol("putchard");
As yet, I have no idea why - that symbol even seemed to be exported:
extern "C"
double putchard(double X) {
putchar((char)X);
return 0;
}
On Fri, Apr 1, 2016 at 2:42 AM, Russell Wallace <russell.wallace at gmail.com>
wrote:
> To try to find out why it was crashing, I followed the
2015 Feb 10
2
[LLVMdev] Some basic questions regarding MCJIT and Kaleidoscope sample
HI Dibyendu,
A single MCJIT instance can notionally manage multiple modules, but there
are caveats (which I'm afraid I don't remember off the top of my head) that
make it unattractive in practice. I believe most clients opt for something
like the ExecutionEngine-per-Module model used in the Kaleidoscope
tutorials.
As Dave mentioned, I'm also working on some new JIT APIs (Orc) that
2016 Apr 01
2
Kaleidoscope on Windows - bug maybe found?
To try to find out why it was crashing, I followed the trail of function
calls:
C:\llvm\examples\Kaleidoscope\Orc\initial\toy.cpp
auto ExprSymbol = J.findUnmangledSymbol("__anon_expr");
JITSymbol findUnmangledSymbol(const std::string Name) {
return findSymbol(mangle(Name));
}
JITSymbol findSymbol(const std::string &Name) {
return CompileLayer.findSymbol(Name,
2010 Nov 15
0
[LLVMdev] Optimization of calls to functions without side effects (from Kaleidoscope example)
Hi Rob,
> I'm using the gvn pass, not sure about basic-aa.
if you are using LLVM from svn then you need to specify the basic-aa analysis,
otherwise gvn won't unify calls to readonly/readnone functions. This is new
behaviour introduced by Dan; probably the tutorial should be updated.
Ciao,
Duncan.
>
> I've copied the code as-is from
2010 Nov 15
0
[LLVMdev] Optimization of calls to functions without side effects (from Kaleidoscope example)
Rob,
I can reproduce the behaviour you observe using llvm top-of-tree.
I will try to look into it.
Best regards,
--
Arnaud de Grandmaison
-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Rob Pieke
Sent: Monday, November 15, 2010 4:27 PM
To: Duncan Sands; llvmdev at cs.uiuc.edu
Subject: Re: [LLVMdev] Optimization of calls to
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 Nov 15
1
[LLVMdev] Optimization of calls to functions without side effects (from Kaleidoscope example)
Still no luck after switching to:
theFPM->add( new llvm::TargetData( *theExecutionEngine->getTargetData() ) );
theFPM->add( llvm::createBasicAliasAnalysisPass() );
theFPM->add( llvm::createInstructionCombiningPass() );
theFPM->add( llvm::createReassociatePass() );
theFPM->add( llvm::createGVNPass() );
theFPM->add( llvm::createCFGSimplificationPass() );
Based on output
2010 Nov 15
1
[LLVMdev] Optimization of calls to functions without side effects (from Kaleidoscope example)
SUCCESS!
Sorry, I had removed the addFnAttr() call by accident. Using the basicAA pass and ReadOnly, as you suggested, works like a charm!
:)
> -----Original Message-----
> From: Rob Pieke
> Sent: Monday, November 15, 2010 4:40 PM
> To: 'Duncan Sands'
> Cc: 'llvmdev at cs.uiuc.edu'; 'Dan Gohman'
> Subject: RE: [LLVMdev] Optimization of calls to
2012 Jul 20
0
[LLVMdev] LLVM Kaleidoscope Chapter 7 Compilation Error in MinGW32(MSYS Shell) on Windows
I've managed to compile LLVM & Clang on windows using command prompt and
using it in MinGW (MSYS Shell). I've done this multiple times, following
many different instructions, ranging from the Getting started page for
clang, the llvm.org official getting started page, and even the attached
guide written by someone else on the llvmdev email list (
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
2013 Jun 04
1
[LLVMdev] MCJIT and Kaleidoscope Tutorial
Hi Andrew,
Am 04.06.2013 02:13, schrieb Kaylor, Andrew:
> Hi Dmitri,
>
> You might want to try replacing the call to JMM->invalidInstructionCache() with a call to TheExecutionEngine->finalizeObject(). If you are getting a non-NULL pointer from getPointerToFunction but it crashes when you try to call it, that is most likely because the memory for the generated code has not been
2008 Apr 15
2
[LLVMdev] Bugs in Kaleidoscope tutorial code, and a bus error
I'm working through the Kaleidoscope tutorial through section 2.4, and
I've encountered some problems: several minor bugs, and finally a bus
error that has me stumped:
-------
In the code listed in LLVM Tutorial section 2.2 Implementing a Parser and AST.
Line 19 has a comma at the end of line that shouldn't be there
Line 120 is missing a closing angle bracket.
Line 120 should be
2019 Jan 07
2
Kaleidoscope tutorial: extern functions failing
Hi all,
I am new to LLVM and have been working through the Kaleidoscope tutorial.
Everything is working fine so far except for local externs (as opposed to
things like the math functions, which are working). Note that I have seen
this bug with the reference code listing, as well as my own code. link to
code: https://llvm.org/docs/tutorial/LangImpl05.html#full-code-listing
[c34n10 kaleidoscope]