search for: fammiliar

...KDE 3.4), but still have some issues - sound being one of them. But that's my problem. I'd like to contribute to the wine project somehow. Perhaps starting as a test user for some application. Then involving (as learn C) in solving wine related problems. I don't know if you're fammiliar to the online game Conquer Online (www.conqueronline.com). It's a MMORPS (or something like that!). Built only for windows. I have it now and all the .dlls it asks, but still I can't run it. I get this as I try to run the game: gtl@MCLAREN:~/.wine/drive_c/Program Files/Conquer 1.0$ win...

...trying to adjust the proxy before falling back to more drastic measures, such as patching or relinking...). > It would be possible to implement more aggressive solutions, and if you > are interested, llvmdev is a great place to talk about how to do it. > yes, maybe. well, maybe I can fammiliarize myself with the project more, and maybe be able to say something actually useful at some point... > Are you interested in using LLVM for your project? If not, llvmdev isn't > a very appropriate place to talk about your project. If you are, this is > a great place to ask questio...

On Wed, 24 Oct 2007, BGB wrote: > even more interestingly: if the same compiler were also used for static > compilation, it could be used as a special feature to make such dynamic > movability available even for statically compiled and linked code (as > is, in my case, parts of the app which are statically compiled and > linked, can't currently be relinked...). LLVM handles

...rst place, so it obviously had access to write it there. In any case, the JIT can use mprotect to map the page writable if it has to. > a major detractor at this point for me and LLVM, is that it is > written in > C++, and I am not so good with C++, and I am otherwise not so > fammiliar with > the codebase... That sounds like an excellent reason to get more familiar with C++ and the LLVM code base. It's usually better to try to grow your capabilities than to limit what you can do by avoiding learning new things ;-) LLVM has extensive documentation at http://llvm.or...

oh, ok. actually, I had partly considered this approach at one point, but opted with the form I did instead (in large part because it does not involve such a tweak, or dependency on the previous location). of course, as noted, due to the possibility of function pointers, this is a little risky. I had not considered this issue previously, but it is definitely worth consideration... I guess the

On Oct 23, 2007, at 05:52, BGB wrote: > I am assuming then that some external assembler is used (such as > 'gas')?... In the static compilers, yes. The JIT directly serializes instructions into memory without the aid of an external assembler. There are also experimental built-in assemblers; LLVM calls them object writers[1]. > it looks like much of the interconnection

...languages would target it, so I wanted something hopefully fairly general. different frontends could be written hopefully without too much interdependence or conflict. this is also why I had chosen a stack machine, as this offers at least some semblance of machine-abstraction. I am also fairly fammiliar with stack machines, as I have had a long time of fairly good success with them... a major problem I have ran into though is related to evaluation ordering, which though providing multiple options, doesn't really provide any great options. in part, the x86-64 calling convention leaves a ma...

...ype-agnostic (it is the task of the operation itself to deal with whatever was given to it). as such, a lot of the IL-compiler's internals go to dealing with all the various types (a good deal exists in terms of elaborate type-dispatch code). I also used a stack because that is what I am most fammiliar with... I call my IL language RPNIL, or RIL (since it is an RPN-based IL). the RIL compiler (converts RIL to assembler) is generally referred to as the 'lower compiler', with the 'upper compiler' handling the translation from C to RIL. as noted, I also have a runtime assembler an...

well, as it so seems I need to bother everyone on the list with my pointless newb crap, but here goes. maybe there was a FAQ for all this, but I missed it. well, I am not trying to demean LLVM in any way here, only trying to understand and evaluate things from my POV is all... sorry if at all I seem arrogant or condescending... well, running a linecounter, it is about 223 kloc (c++ ...), +