search for: exeve

...LLVM? It would make more sense to me (but also be more implementation work) to link the LLVM JIT and CodeGen libraries directly into Qemu and to forgo the Qemu->C->LLVM translation process. Not only should this speed it up (because you're removing the C preprocessing, C parsing, and exeve() overhead), but it should also give you more control over what LLVM is doing (you can use LLVM's JIT infrastructure to re-codegen functions at run-time and things like that). -- John T. > > How about storing generated code on disc? Or the intermediate IR? I'd > typically use...

Hi Tilmann, > Nevertheless, it is unlikely that llvm-qemu will ever be much faster > than regular qemu (by replacing its code generator completely, which > it currently does), which is due to the fact that regular qemu has a > very lightweight code generator (it basically only copies blocks of > memory and performs some patching to them and only does static > register

...v.h | 37 +- Xext/xcmisc.c | 26 +- Xext/xf86bigfont.c | 6 - Xext/xtest.c | 39 +- Xi/closedev.c | 1 - Xi/exevents.c | 27 +- Xi/extinit.c | 7 +- Xi/listdev.c | 14 +- Xi/opendev.c | 1 - Xi/queryst.c | 3 +-...

...out-of-range keycodes (bug #12528) Input: Generate XKB mapping changes for all core-sending devices (bug #12523) XFree86 Misc/VidMode: Remove ridiculous debug ErrorFs configure.ac/XFree86: Only build XF86Misc and XF86VidMode when appropriate Xi: Include XI protocol header in exevents.h XKB: Add more bits to xkbsrv.h XFree86: Remove ridiculous SIGIO debugging XKB: Don't update indicators on all devices, add missing include file XKB: Cope with all events in XkbProcessKeyboardEvent XKB: Remove usage of alloca Render: Remove usage of alloc...