>>110Contrived statistically insignificant examples much?
I was told only compiler writers have this problem so I gave an example of something I've personally encountered. You yourself claim to have experience with what I regard as the most oddball aspect: memory which is not byte-addressable. This kind of weird collections of constraints is all over the place in the embedded world.
where the compiler isn't smart enough, tweaking the source isn't always the best answer.
What is the best answer? To switch compilers, incurring the kind of nightmare problems you describe above? That's not always even an option. Besides, if you're working with the same chip all the time, endian-awareness is not difficult. It's not like portability is a common concern in constrained systems. Usually the code is going to run on one device.