DLL with both protected and unprotected exports

DLL with both protected and unprotected exports

I have a DLL with multiple exported functions where I want to protect just one of them. When using iprot on just that one function, it produces a DLL with only that one function where all the uprotected functions were removed. Is this the intended behavior or a bug?

1 post / 0 new
For more complete information about compiler optimizations, see our Optimization Notice.