search for: ziga

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

Hello, Ziga. > First the calling conversion. The so called __thiscall conversion on > VC++ passes arguments on stack, while this pointer is passed > into ECX register. For GCC, as far as I am aware, the this pointer is > pushed as if it were a special (first) argument. The fix would > be prea...

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

...lock 21258200 on dm-0 READ block 21258208 on dm-0 Timings are showing that these gaps (where block_{n+1} > block_{n} + 8) are where most of the time is lost. Is there any way I could read the directory blocks in larger batches? Any other ideas on how to improve these times? Thanks, -- Ziga [1] Note that the file system was unmounted between running the tests to make sure the caches were cold. [2] This is the amount of data read while stat-ing the files (retrieved from /proc/diskstats, rsect column). [3] The algorithm is as follows: for each file, get the corresponding...

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

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

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

Anton Korobeynikov pravi: > Hello, Ziga. > > >> VCPP throws a warning that class is previously declared as struct. >> Either it must be struct everywhere or class everywhere. >> Declaration uses struct, while the definition uses class. >> > Nice! However it will be better to do the opposite: h...

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

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

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

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

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

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

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

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

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