similar to: [LLVMdev] Mingw 1.9 release rar archive currupt

Hello, Ziga > I downloaded the prebuild mingw 1.9 release and tried to extract the > archine with WinRAR (latest), but it didn't work, says that archive is > currupt. The source release was extracted correctly ... I'm sorry, this is well-known issue with msys-supplied tar+bzip2 executables (\n is turned to \r\n somewhere in binary files). I'll fix the tarball soon. --

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

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

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

> 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

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

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

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

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 >>

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 >>>

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. >

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

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.

I was wondering if (and when) is the full C++ compiling support (as it was with llvm3) to be expected (this mainly means the addition of EH to llvm)? Regards, Žiga

Hi all! I?ve got a problem with some (not all) of my mailboxes. If you see, some folders got strange names. 41943652 4.0K drwx------ 3 vmail vmail 4.0K Mar 25 10:42 INBOX 1 42205306 4.0K drwx------ 3 vmail vmail 4.0K Mar 25 10:46 INBOX 1 1 42336882 4.0K drwx------ 3 vmail vmail 4.0K Mar 25 10:48 INBOX 1 1 1 42337295 4.0K drwx------ 3 vmail vmail 4.0K Mar 25 10:49 INBOX 1 1 1 1 42598861

I made the windows port, the first example compiled and executed correctly. I am sending a patch so you can test it if i didn't break linux compatibility. Otherwise, I will look into deja-gnu testing, perhaps can compile it on windows. I will also add other beckend in the future (Sparc, PowerPC). I hope windows using Visual C++ will be soon officially supported :) About the problem I had

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

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

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

Hi, everyone! I decided to make llvm port on windows, to support at least Visual Studio 7.1 and Visual Studio 8. I guess I will make only Visual Studio 7.1 version, since it can be easily converted to version 8. I am using the already made build system made by Morten Ofstad. I don't know how long has it been when he left, but most of the projects are there, only some files are missing and