search for: hookable

I think I have a slight problem with the new hookable plugins and the ini plugin. I haven't looked into it too much, but the plugins use an option to store their abi version. This value is stored so that when the cube/scale plugins are updated it will not be changed and things will not work. Do we need some sort of flag to tell ini not to save...

...RN in the dialog mode. riched20: Implement handling of WM_KEYDOWN VK_ESCAPE in the dialog mode. riched20: Implement handling of WM_KEYDOWN VK_TAB in the dialog mode. Stefan D?singer (13): configure: Check for ms_hook_prologue attribute support. kernel32: Make some functions hookable. user32: Make some functions hookable. shell32: Make some functions hookable. d3d8: Make Direct3DCreate8 hookable. d3d9: Make some functions hookable. ddraw: Make directdraw create functions hookable. dinput: Make the creation functions hookable. d3d: Make...

...Drop tests. hlink: Improve file protocol handling in HlinkParseDisplayName. dinput8: Create a window that will receive events generated by input tests. Stefan D?singer (5): wined3d: surface_load_ds_location can handle WINED3D_LOCATION_DISCARDED. ole32: Make CoCreateInstance hookable for Steam. user32: Make SetWindowTextA/W hookable. d3d9: Make ResetEx and PresentEx hookable. winmm: Make some joystick functions hookable. Stefan Leichter (3): wtsapi32/tests: Add some tests for WTSEnumerateProcessesW. fltlib: Add a version resource. comdlg32:...

...o interact well with regular accesses, which means that regular loads cannot move "down" a non-temporal barrier, and regular stores cannot move "up" a non-temporal barrier. *Why not just have the compiler add the fences?* LLVM could do this, either as a per-backend thing or a hookable pass such as AtomicExpandPass. It seems more natural to ask the programmer to express intent, just as is done with atomics. In fact, a backend is current free to ignore !nontemporal on load and store and could therefore generate only half of what's requested, leading to incorrect code. That wou...

...tions, metadata, whatever) and can write down one format and write checks against the other format for tests. This is a wonderful world to live in with tests. I never want LLVM to *decrease* how much we leverage this. But we *do* have API interactions that we need to test. We have plugin APIs, and hookable interfaces, ranging from Clang frontend actions to JIT listeners. We also have *generic* code in ADT that is all about API interactions. Most generic code in fact is -- we want it to work for *any* T that behaves in a certain way, so we need to give it interesting Ts to test it. My immediate examp...

initramfs-tools git repo: git clone git://git.debian.org/kernel/initramfs-tools.git initramfs-tools is an hookable initramfs generator. It can boot on NFS, LVM2, md, LUKS, dmraid, oldstyle devices, .. The generated initramfs is generic, but can explicitly be tuned for small. It is actively deployed in Debian and Ubuntu. It is written in POSIX shell. It has an "end-user" friendly invocation with update...

...> means that regular loads cannot move "down" a non-temporal barrier, > > and regular stores cannot move "up" a non-temporal barrier. > > > Why not just have the compiler add the fences? > > > LLVM could do this, either as a per-backend thing or a hookable > > pass > > such as AtomicExpandPass . It seems more natural to ask the > > programmer to express intent, just as is done with atomics. In > > fact, > > a backend is current free to ignore !nontemporal on load and store > > and could therefore generate only half...

...egular loads cannot move > "down" a non-temporal barrier, and regular stores cannot move "up" a > non-temporal barrier. > > > > > > *Why not just have the compiler add the fences?* > > > > LLVM could do this, either as a per-backend thing or a hookable pass such > as AtomicExpandPass. It seems more natural to ask the programmer to > express intent, just as is done with atomics. In fact, a backend is current > free to ignore !nontemporal on load and store and could therefore > generate only half of what's requested, leading to inco...