Check some information found - O0 really cannot make Gcc is not optimized, Gcc will put some content optimizing,
Really upset, is apart from in front of the function plus __attribute__ ((optimize (" O0 "))) and in front of the variable volatile this way of change the code, there is no other way to make the procedures for the GCC don't optimize
CodePudding user response:
Even using O0, will also have a 50-60 will be optimized, such as the inlineCodePudding user response: