"Robert Shearman" rob@codeweavers.com wrote:
Shouldn't be enough for the __i386__ case just omitting 'inline' in access_resource definition?
Dmitry Timoshkov wrote:
No. Marcus already discovered with the previous version of EXC_CallHandler using the "-funit-at-a-time" option that the compiler can re-order the arguments and generally do whatever it wants if we hint that it won't be used outside of the module. The compiler is also free to generate LdrAccessResource as a simple jump to access_resource, or even to just make access_resource point to the same address as LdrAccessResource. In short, the only sure way of generating code that Shrinker needs is to do it explicitly.