Yes, it might have, assuming it's available in the 360 compilation environment.
Another solution would be to split the existing function into safe_function() and unsafe_function(), and remove use of the PREFETCH_EX flag. But then you have to explain to callers that they must not protect calls to unsafe_function() with any kind of conditional statement.
The author hinted at possible solutions but it was probably a case of "twice bitten" by that point.
Another solution would be to split the existing function into safe_function() and unsafe_function(), and remove use of the PREFETCH_EX flag. But then you have to explain to callers that they must not protect calls to unsafe_function() with any kind of conditional statement.
The author hinted at possible solutions but it was probably a case of "twice bitten" by that point.