Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Full C++ support"
2006 Nov 21
2
[LLVMdev] EH and C++ intergation
I was going through documentation and source lately, and I decided how to
make llvm bytecode more compatible to C++:
1) thiscall sould be introduced, which would take N arguments and the
first argument would always be the C++ "this" argument. This would
abstract llvm compiler dependant C++ code emittion.
2) the ret instruction should be able to return structs (as Chris has
already
2006 Nov 21
2
[LLVMdev] EH and C++ intergation
Chris Lattner pravi:
> On Tue, 21 Nov 2006, [ISO-8859-2] Žiga Osolin wrote:
>> I was going through documentation and source lately, and I decided
>> how to
>> make llvm bytecode more compatible to C++:
>> 1) thiscall sould be introduced, which would take N arguments and the
>> first argument would always be the C++ "this" argument. This would
>>
2006 Nov 21
1
[LLVMdev] EH and C++ intergation
Chris Lattner pravi:
> On Tue, 21 Nov 2006, [ISO-8859-2] Žiga Osolin wrote:
>>> Sure. Anton can give you ideas for this.
>>>
>> I think it should not be too difficult because you allow custom call
>> conversions and this is quite easy to add, we only have to garantee that
>> the backend will emit it.
>
> Right.
>
>>>> 2) the ret
2006 Nov 21
0
[LLVMdev] EH and C++ intergation
On Tue, 21 Nov 2006, [ISO-8859-2] Žiga Osolin wrote:
> I was going through documentation and source lately, and I decided how to
> make llvm bytecode more compatible to C++:
> 1) thiscall sould be introduced, which would take N arguments and the
> first argument would always be the C++ "this" argument. This would
> abstract llvm compiler dependant C++ code emittion.
Sure.
2006 Nov 21
0
[LLVMdev] EH and C++ intergation
On Tue, 21 Nov 2006, [ISO-8859-2] Žiga Osolin wrote:
>> Sure. Anton can give you ideas for this.
>>
> I think it should not be too difficult because you allow custom call
> conversions and this is quite easy to add, we only have to garantee that
> the backend will emit it.
Right.
>>> 2) the ret instruction should be able to return structs (as Chris has
>>>
2006 Nov 21
0
[LLVMdev] EH and C++ intergation
I was going through documentation and source lately, and I decided how to
make llvm bytecode more compatible to C++:
1) thiscall sould be introduced, which would take N arguments and the
first argument would always be the C++ "this" argument. This would
abstract llvm compiler dependant C++ code emition.
2) the ret instruction should be able to return structs (as Chris has
already
2007 Dec 17
2
[LLVMdev] MSIL
Hi everyone!
I am working on a .NET based project (actually written in C#). During
the coding, we have noticed many inefficiencies of C# compiler to
optimize code. Compiler performs only a few optimisations. A vital
optimisation, inlining, is missed. The JIT-er has rules not to inline
methods containing structs as parameters (this is really stupid!) and
inlining methods longer than 20 bytes
2006 Nov 06
2
[LLVMdev] LLVM code emittion and C++ compiler compatibily
> On Mon, 6 Nov 2006, [ISO-8859-2] Žiga Osolin wrote:
>> The other thing are the return types. I don't know (it is probably even
>> not documented) how VC++ returns smart pointer (boost::smart_ptr),
>> or any other type (other basics types, such as int, float, ... are
>> probably returned into EAX as with GCC). Once again, we may
>> need specific return values
2006 Nov 18
2
[LLVMdev] EH and call conversion integration
Hello!
I am currently trying to make EH (exception handling) possible to be
integrated in C++. This means that C++ code can throw exceptions and
llvm code can catch such exception and llvm can throw exceptions that
C++ can catch (or pass through). There are quite some difficulties with
approach:
* I must write ABI specific backends for EH. Since we support Visual
Studio and GCC, two
2006 Nov 06
2
[LLVMdev] LLVM code emittion and C++ compiler compatibily
Hello!
I have a question how about JIT-ed code and the C++ compiler
compatibily. My project (www.baadengine.org) will use
llvm and we will provide integration of JIT-ed code directly into C++
code. This means that C++ code can call JIT code just
like any other code and JIT-ed code can call C++ code. We will compile
to your bytecode from our BSF format.
The question is if it is possible this
2006 Nov 19
0
[LLVMdev] EH and call conversion integration
On Sat, 18 Nov 2006, [ISO-8859-2] Žiga Osolin wrote:
> I am currently trying to make EH (exception handling) possible to be
> integrated in C++. This means that C++ code can throw exceptions and
> llvm code can catch such exception and llvm can throw exceptions that
> C++ can catch (or pass through). There are quite some difficulties with
> approach:
Cool! This is the major
2006 Nov 19
1
[LLVMdev] EH and call conversion integration
Chris Lattner pravi:
> On Sat, 18 Nov 2006, [ISO-8859-2] Žiga Osolin wrote:
>> I am currently trying to make EH (exception handling) possible to be
>> integrated in C++. This means that C++ code can throw exceptions and
>> llvm code can catch such exception and llvm can throw exceptions that
>> C++ can catch (or pass through). There are quite some difficulties with
2006 Nov 06
0
[LLVMdev] LLVM code emittion and C++ compiler compatibily
On Mon, 6 Nov 2006, [ISO-8859-2] Žiga Osolin wrote:
> The other thing are the return types. I don't know (it is probably even
> not documented) how VC++ returns smart pointer (boost::smart_ptr),
> or any other type (other basics types, such as int, float, ... are
> probably returned into EAX as with GCC). Once again, we may
> need specific return values per arhitecture.
It is
2006 Nov 04
1
[LLVMdev] llvm partly ported to windows
Hello (again)!
I fixed most of the system and the following projects compile now:
* Analysis
* AsmParser
* Bytecode
* CBeckend
* Codegen
* ExecutionEngine
* Support
* System
* TableGen
* Target
* Transforms
* VMCore
I would like to compile at least x86 target as well as Fibonacci example
(to test if it really works). In order to do so, I may need some hints:
1) How to generate
2006 Oct 10
1
[LLVMdev] llvmdev: Windows support
Hello, everyone!
My name is Žiga Osolin and I am one of administrators of baadengine
project (www.baadengine.org). It is an open source, BSD-licenced, game
engine. We are very interested in llvm to provide us runtime code
generation (basically, wrappers to easily call scripts from C++ and
vica-versa, via vtbl (we replace vtbl for scripted types)) and also to
allow our VM to run on llvm. Our
2006 Nov 06
0
[LLVMdev] LLVM code emittion and C++ compiler compatibily
On Mon, 6 Nov 2006, [ISO-8859-2] Žiga Osolin wrote:
> The problem is this is not possible, because what I would compile to JIT
> are actual classes. The integration of C++ and JIT code is very
> important; for example we would create our own vtbls with JIT-ed code
> addresses as the function call target.
Ok. Realize that this ties you to a specific compiler version though.
>
2006 Dec 23
1
[LLVMdev] in Cygwin problems
Problem 2:
Configure:
../src/configure --prefix=/tmp/llvm/install --disable-threads --disable-nls --disable-shared --enable-languages=c,c++ --disable-c-mbchar --program-prefix=llvm-
$ make
make[1]: Entering directory `/tmp/llvm3/llvm/build/libiberty'
make[2]: Entering directory `/tmp/llvm3/llvm/build/libiberty/testsuite'
make[2]: Nothing to be done for `all'.
make[2]: Leaving
2006 Nov 21
4
[LLVMdev] LLVM and Cell processor
Hi all,
I've been following LLVM for a couple of years, and though I've not
found an occasion to use it (yet), I'm always curious about its
potential uses.
I was discussing with friends about the Cell processor, and some of
the arguments were that it is difficult to program and difficult to
optimize. One of the concerns was that the PPE (central processor) is
"in
2006 Dec 22
0
[LLVMdev] in Cygwin problems
On Sat, 23 Dec 2006, Roman wrote:
> How to solve this problem?
Java isn't supported. Use --enable-languages=c,c++
-Chris
> $ make
> make[1]: Entering directory `/tmp/llvm3/llvm/build/libiberty'
> make[2]: Entering directory `/tmp/llvm3/llvm/build/libiberty/testsuite'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory
2006 Dec 22
5
[LLVMdev] in Cygwin problems
How to solve this problem?
$ make
make[1]: Entering directory `/tmp/llvm3/llvm/build/libiberty'
make[2]: Entering directory `/tmp/llvm3/llvm/build/libiberty/testsuite'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/tmp/llvm3/llvm/build/libiberty/testsuite'
make[1]: Leaving directory `/tmp/llvm3/llvm/build/libiberty'
make[1]: Entering directory