https://bugs.winehq.org/show_bug.cgi?id=38488
--- Comment #2 from Henri Verbeet hverbeet@gmail.com --- (In reply to Nikolay Sivov from comment #1)
This could be a case when wined3d_debug_location() needs to mask out invalid values with '& 0x3ff' for example. Stefan, what you think about it?
It would probably be better to only mask it for the TRACE, (i.e. call it as "wined3d_debug_location(location & WINED3D_LOCATIONS)"), and there may even be an argument for not using wined3d_debug_location() for invalidations at all, instead just using %#x and only printing the new location flags. The FIXME never bothered me enough to send a patch though...