search for: fammiliarize

Hello, I'm using Linux for about two months now. Even before switching to Linux I have heard of Wine. I got my system running relativelly stable (I use Slackware 10.2, kernel-2.6.14 and 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.

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

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

>> LLVM handles function pointers currently. It just overwrites the >> first >> instruction of the old code with an unconditional branch to the new >> implementation. Thus, any code branching to the old location will >> still >> work. > > yes, that works so long as one has write access to the text section > (or the > code is otherwise in a

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

----- Original Message ----- From: "Gordon Henriksen" <gordonhenriksen at mac.com> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Wednesday, October 24, 2007 1:45 AM Subject: Re: [LLVMdev] me being stupid: me vs the llvm codebase... On Oct 23, 2007, at 05:52, BGB wrote: > I am assuming then that some external assembler is used (such as >

well, sadly, I am not sure how people are on this list... in any case, LLVM is an interesting project, and may well continue being interesting. but, in my case, I have done my own compilation framework... ok, I didn't really hear about the really interesting bits of LLVM until after I had (more or less) wrote mine... ok, my point is to maybe to have something interesting to talk about, not

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++ ...), +