Displaying 20 results from an estimated 8000 matches similar to: "[LLVMdev] The first two lines of llvm tutorial don't compile."
2008 Jun 02
0
[LLVMdev] The first two lines of llvm tutorial don't compile.
You need to use the script 'llvm-config' to pass correct arguments to g
++:
g++ -o broken.o `llvm-config --cxxflags` broken.cpp
On Jun 2, 2008, at 9:43 AM, Hendrik Boom wrote:
> I took the first two lines of the sample program in the tutorial:
>
>
> hendrik at lovesong:~/dv/lang/hlvm$ cat broken.cpp
> #include "llvm/DerivedTypes.h"
> #include
2008 Jun 02
5
[LLVMdev] The first two lines of llvm tutorial don't compile.
On Mon, 02 Jun 2008 09:52:16 -0700, Thomas Hudson wrote:
> You need to use the script 'llvm-config' to pass correct arguments to g
> ++:
>
> g++ -o broken.o `llvm-config --cxxflags` broken.cpp
>
>
Interesting. When I type the command as you provided it (using cut-and-paste) I get:
hendrik at lovesong:~/dv/lang/hlvm$ g++ -o broken.o `llvm-config --cxxflags`
2008 Jun 03
3
[LLVMdev] Problems with iterator.h
Just finished the compiling llvm without llvm-gcc from svn.
Tried it out. Got
g++ -o hlvm.o -c -I/farhome/hendrik/dv/llvm/llvm/include -D_DEBUG -D_GNU_SOURCE
-D__STDC_LIMIT_MACROS -g -Woverloaded-virtual hlvm.cpp
In file included from /farhome/hendrik/dv/llvm/llvm/include/llvm/DerivedTypes.h:
21,
from hlvm.cpp:1:
/farhome/hendrik/dv/llvm/llvm/include/llvm/Type.h:19:31: error:
2006 Aug 06
2
[LLVMdev] Could not access CVS for llvm
I tried to access the latest LLVM, since several messages here so far have
referred me to it. Now I have no experience with CVS-over-the-net. My
previous experiences with versoin control have been RCS and Monotone.
Brief summary:
hendrik at lovesong:~/dv$ mkdir llvm
hendrik at lovesong:~/dv$ cd llvm
hendrik at lovesong:~/dv/llvm$ cvs -d :pserver:anon at llvm.org:/var/cvs/llvm login
Logging in
2006 Aug 07
2
[LLVMdev] Could not access CVS for llvm
Hendrik,
You could also just "touch ~/.cvspass" to create the file which should
eliminate the warning. However, since you did a login, and it seemed
successful, chances are the file now exists (containing the blank
password for anon at llvm.org).
Reid.
On Mon, 2006-08-07 at 09:14 -0500, John Criswell wrote:
> Hendrik Boom wrote:
> > I tried to access the latest LLVM, since
2006 Aug 07
0
[LLVMdev] Could not access CVS for llvm
Hendrik Boom wrote:
> I tried to access the latest LLVM, since several messages here so far have
> referred me to it. Now I have no experience with CVS-over-the-net. My
> previous experiences with versoin control have been RCS and Monotone.
>
> Brief summary:
>
> hendrik at lovesong:~/dv$ mkdir llvm
> hendrik at lovesong:~/dv$ cd llvm
> hendrik at lovesong:~/dv/llvm$
2006 Aug 07
0
[LLVMdev] Re: Could not access CVS for llvm
On Mon, 07 Aug 2006 09:26:07 -0700, Reid Spencer wrote:
> Hendrik,
>
> You could also just "touch ~/.cvspass" to create the file which should
> eliminate the warning. However, since you did a login, and it seemed
> successful, chances are the file now exists (containing the blank
> password for anon at llvm.org).
Indeed, the file is there.
>
> Reid.
>
2008 Jun 09
7
[LLVMdev] regression? Or did I do something wrong again?
I don't know if the toy program in chapter 4 of the tutorial
implementing Kaleidoscope in llvm with C++ is part of your
regression suite, but with the version of llvm I installed
last weekend, it does not compile:
hendrik at lovesong:~/dv/llvm/tut$ g++ -g toy.cpp `llvm-config --cppflags --ldflags --libs core jit native` -O3 -o toy
toy.cpp: In member function ‘virtual llvm::Value*
2006 Aug 07
1
[LLVMdev] Re: Could not access CVS for llvm
Its possible to get the "file not found" error if the directory is not
readable. Are you sure you don't have a permissions problem or
something?
Reid.
On Mon, 2006-08-07 at 13:09 -0400, Hendrik Boom wrote:
> On Mon, 07 Aug 2006 09:26:07 -0700, Reid Spencer wrote:
>
> > Hendrik,
> >
> > You could also just "touch ~/.cvspass" to create the file
2008 Jun 09
0
[LLVMdev] regression? Or did I do something wrong again?
Hi Hendrik,
> hendrik at lovesong:~/dv/llvm/tut$ g++ -g toy.cpp `llvm-config --cppflags --ldflags --libs core jit native` -O3 -o toy
> toy.cpp: In member function ‘virtual llvm::Value* NumberExprAST::Codegen()’:
> toy.cpp:359: error: no matching function for call to ‘llvm::ConstantFP::get(const llvm::Type*&, llvm::APFloat)’
> /usr/local/llvm/include/llvm/Constants.h:237: note:
2008 Jun 09
0
[LLVMdev] regression? Or did I do something wrong again?
On Mon, Jun 9, 2008 at 7:29 AM, Hendrik Boom <hendrik at topoi.pooq.com> wrote:
> I don't know if the toy program in chapter 4 of the tutorial
> implementing Kaleidoscope in llvm with C++ is part of your
> regression suite
It isn't (although that might be a good idea).
> but with the version of llvm I installed
> last weekend, it does not compile:
>
> hendrik
2008 Jun 06
2
[LLVMdev] Index to libraries?
There wouldn't happen to be an index telling one which libraries
define which symbols, would there?
For example, if I'm told
alvm.o: In function `llvm::Function::Create(llvm::FunctionType const*, llvm::GlobalValue::LinkageTypes, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, llvm::Module*)':
2008 Mar 27
1
wine newbie has trouble with T_LOVE95.EXE
I'm new to wine; I'm having trouble running this game, which has been
reported to work previously, in the test result
http://appdb.winehq.org/objectManager.php?sClass=version&iId=4050,
with wine 0.9.24 under Ubuntu 6.10 "Edgy".
I'm running Debian lenny which has wine-0.9.44.
Now I'm enough of a newbie with wine that I presume I'm using wine
improperly (but not
2008 Jun 07
2
[LLVMdev] ExecutionEngine::create returns 0
What does it mean when ExecutionEngine::create returns 0?
Here's a simplified example:
#include "llvm/Module.h"
#include "llvm/ExecutionEngine/ExecutionEngine.h"
main()
{
llvm::Module * module = new llvm::Module("the module");
llvm::ExecutionEngine *ee = llvm::ExecutionEngine::create(module);
fprintf(stdout, "pointer is %x.\n", ee);
}
I
2008 Jun 06
0
[LLVMdev] Index to libraries?
Hi Hendrick,
All of the directories under llvm/lib correspond directly to the
libraries that are built, so you should be able to just grep for the
symbol definitions and add the corresponding library. Use llvm-config
to discover transitive dependencies if possible.
On Jun 6, 2008, at 12:20, Hendrik Boom wrote:
> There wouldn't happen to be an index telling one which libraries
>
2006 Aug 07
1
[LLVMdev] Re: gcc4 or gcc3?
On Mon, 07 Aug 2006 11:45:04 -0700, Reid Spencer wrote:
> Hi Hendrik,
>
> On Mon, 2006-08-07 at 14:35 -0400, Hendrik Boom wrote:
>> I just downloaded the CVS version of llvm and llvm-test. Presumably
>> this is the one that's scheduled to become 1.8 in a few days.
>
> Not really. The current CVS head is quite a ways past release 1.8 at
> this point. If you
2010 Feb 17
1
[LLVMdev] LLVM-OCaml Bindings Tutorial (2.6-2.7)
On Tue, Feb 16, 2010 at 2:47 AM, Jon Harrop <jon at ffconsultancy.com> wrote:
> On Tuesday 16 February 2010 03:51:00 Jianzhou Zhao wrote:
>> Does anyone know if there is any realistic project using LLVM-OCaml
>> Bindings?
>
> I've written a VM in OCaml built upon LLVM using LLVM's OCaml bindings:
>
> http://www.ffconsultancy.com/ocaml/hlvm/
>
> There
2009 Jun 24
2
[LLVMdev] Garbage collection implementation
Jon Harrop wrote:
> The simplest way is surely to reuse HLVM because it provides
everything you
> need and is even written in the right language! ;-)
Is there a web page with HLVM docs? There's a README.txt in the
subversion repository:
https://llvm.org/svn/llvm-project/hlvm/trunk/README.txt
which says:
HLVM comes with documentation in HTML format. These are provided in
2009 Mar 10
2
[LLVMdev] Stack smashing
Someone is trying to work on HLVM with me but they're hitting a problem that
we have not been able to resolve. Specifically, GCC seems to be performing
some kind of sanity check for "stack smashing" and is calling abort because
it is unhappy with something that the code is doing. However, I am not sure
what and cannot reproduce the problem.
The stack trace they have given me is:
2009 Jan 25
2
[LLVMdev] OCaml Journal article: Building a Virtual Machine with LLVM
Following on from the success of our previous OCaml Journal articles covering
LLVM, we have begun a series dedicated to the design and implementation of
high-level languages using LLVM. In particular, these new articles are more
pragmatic in nature and go beyond describing working compilers to also
discuss testing, debugging and the performance of LLVM-based compilers.
The first article in