Displaying 20 results from an estimated 100 matches similar to: "[LLVMdev] Question about linker error"
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 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
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
2011 Feb 13
3
[LLVMdev] conversion from 'const llvm::Value*' to 'llvm::Constant*'
Oh, I thought that after "codegening" cos(0) would get me double 1.0
(assigment is working for anything like: global a = 1/3 + 2 /3 for
example) What would be the best way to make assigments involving
functions, like global a = cos(0);
without getting the assertion arising from InitVal =
cast<Constant>(Init->Codegen()); ?
I made some changes and now my code basically works,
2009 Oct 01
3
[LLVMdev] PHI and Allocas
Hi,
I'm incrementing my toy compiler to account for variable mutations
around if/else blocks.
Reading the Kaleidoscope tutorial, I've learnt that I can substitute
the PHI node creation by allocas and retrieving the value later, if
needed. The Kaleidoscope example seems to account for one value only,
the result of:
Value *ThenV = Then->Codegen();
(...)
Value *ElseV =
2011 Feb 13
2
[LLVMdev] conversion from 'const llvm::Value*' to 'llvm::Constant*'
Hi Duncan
Many many thanks, it works now!
But there are still some details I must be missing. I'm getting an assertion
when I try the following assignment in my script:
global c = cos(1);
Assertion failed: isa<X>(Val) && "cast<Ty>() argument of incompatible
type!", file c:/llvm-source-2.7/include/llvm/Support/Casting.h, line 200
However, running for example
2019 Nov 18
2
Crash using exceptions
Hello,
I get a crash in my program that uses exceptions and the LLVM JIT,
even though the exceptions are controlled and thrown/catched in a part
that doesn't deal with LLVM. I noticed that llvm-config --cxxflags
includes the -fno-exceptions flag. Do I need to throw no exceptions
whatsoever in my application to use LLVM JIT?
As a minimal example, I modified the code in
2011 Feb 13
0
[LLVMdev] conversion from 'const llvm::Value*' to 'llvm::Constant*'
Hi Anton,
> But there are still some details I must be missing. I'm getting an assertion
> when I try the following assignment in my script:
> global c = cos(1);
> Assertion failed: isa<X>(Val) && "cast<Ty>() argument of incompatible type!",
I think this is telling you that cos(1) is not a constant.
Ciao, Duncan.
2011 Feb 12
2
[LLVMdev] conversion from 'const llvm::Value*' to 'llvm::Constant*'
Hi
Apolagize if this newbie question has some obvious answer. When running
something like
...
ExprAST *Init = GlobalNames[i].second;
const Value *InitVal;
InitVal = Init->Codegen();
GlobalVariable * globvar = new GlobalVariable(*TheModule,
InitVal->getType(), false, llvm::GlobalValue::ExternalLinkage, InitVal,
Twine(GlobalName));
...
I'm getting the following error
error: invalid
2009 Oct 01
0
[LLVMdev] PHI and Allocas
On Thu, Oct 1, 2009 at 4:35 PM, Renato Golin <rengolin at systemcall.org> wrote:
> Hi,
>
> I'm incrementing my toy compiler to account for variable mutations
> around if/else blocks.
>
> Reading the Kaleidoscope tutorial, I've learnt that I can substitute
> the PHI node creation by allocas and retrieving the value later, if
> needed. The Kaleidoscope example
2007 Nov 05
0
[LLVMdev] 'Implementing a language with LLVM' tutorial
Very nice. Here's a couple comments on the first 6 chapters:
http://llvm.org/docs/tutorial/LangImpl1.html
"We handle comments by skipping to the end of the line and then
returning the next comment."
Shouldn't this say "returning the next comment"?
http://llvm.org/docs/tutorial/LangImpl2.html
I was a bit confused at first because the AST node classes are called
ASTs.
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
2008 Feb 22
1
[LLVMdev] tutorial typos
There were some typos in the tutorial. This patch should fix them:
index b7f968b..50619e0 100644
--- a/docs/tutorial/LangImpl2.html
+++ b/docs/tutorial/LangImpl2.html
@@ -933,7 +933,7 @@ public:
/// of arguments the function takes).
class PrototypeAST {
std::string Name;
- std::vector< Args;
+ std::vector<std::string> Args;
public:
PrototypeAST(const std::string
2007 Nov 05
5
[LLVMdev] 'Implementing a language with LLVM' tutorial
On Mon, 5 Nov 2007, Aaron Gray wrote:
>> Anyone have thoughts or feedback? :)
>
> Nice job. The only bit that is not immediately clear is the 'Proto'
> variable, but is clear when looking through the code at the end of the page.
Where in the tutorial? What would you suggest that I say?
> Could do with a link to the LLVMBuilder class reference material.
I added a link
2011 Feb 12
0
[LLVMdev] conversion from 'const llvm::Value*' to 'llvm::Constant*'
Hi Anton,
> I'm getting the following error
>
> error: invalid conversion from `const llvm::Value*' to `llvm::Constant*'
>
> How may I make this conversion? Any help would be much appreciated!
cast<Constant>(whatever)
Ciao, Duncan.
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
2015 Feb 05
4
[LLVMdev] Fwd: [cfe-dev] freebsd-mips64 unhandled .cpsetup
Moving to llvmdev, as this is not a clang issue.
David
> Begin forwarded message:
>
> Date: 5 February 2015 17:00:34 GMT
> From: Sean Bruno <sbruno at ignoranthack.me>
> To: cfe-dev at cs.uiuc.edu
> Subject: [cfe-dev] freebsd-mips64 unhandled .cpsetup
> Reply-To: sbruno at freebsd.org
>
>
> I'm taking a journey to try and get a clang/llvm build of
2015 Feb 16
2
[LLVMdev] [cfe-dev] freebsd-mips64 unhandled .cpsetup
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 02/09/15 09:09, Toma Tabacu wrote:
>
>> Toma:
>>
>> Hey, I'm the bsd nerd trying to get our mips target switched over
>> to clang/llvm. I looked at switching the mips asm parser over
>> to parseExpression() but I am unfamiliar with the syntax to do
>> this for .cpsetup.
>>
>> If you do
2010 Jun 21
2
[LLVMdev] MC: Object file specific parsing
Hi Daniel,
attached is a patch that pushes most of the object file specific parsing
out of AsmParser and down into MachOAsmParser. This was done as a
cleanup for the ELF work. I know that you're not happy with this
approach, particularly the fact that as we add more object file formats
and assembler dialects, it's going to cause a class explosion. But I was
hoping that we could use this
2010 Nov 22
0
[LLVMdev] Emitting LLVM IR for control flow
Hi
I'm following the excellent Kaleidoscope tutorial to learn how to build an
interpreter using LLVM. Apologize if this list is not the best place to post
beginner's questions. In Kaleidoscope 2.7 when I run
def binary : 1 (x y) y;
def testfor (x)
(for c = 1, c<2 in
x = x +1 ) :
x;
testfor(1)
unexpectadly get 3.000000 instead of 2.000000. This happens, I believe,
because the