The problems lie in knowing where exactly to set the breakpoint
Where is a matter of the optimizer keepin the link to the source correctly.

My point is that it is impossible to set a breakpoint in any code the optimizer has 'shared' between multiple functions, simply because it will break when either of the functions sharing the code execute it.

I recall several episodes with 'mildly' optimized code where the above made me pull some of the hair I do not have by breaking when the place the berakpoint stated was executed by another function.

If ever oprimized code is to be - even moderately - debuggable, there will be a need for the optimizer to edit the source to indicate 'shared' code.

The approach I would like to see would be to NOT 'optimize', but make the compiler 'optimal' by getting rid of all the little things like
mov r7,Ralph
mov a,r7
and such. That would make for an efficient unoptimized code. Many things done by the optimized should be and logically belong, in the compiler. Mr Keil: "why in hades is the use of a jump table for switch statements not a straight unoptimized compiler function"

Erik