Peter Jansen wrote:
Hi All,
The real question here is what we should do about these misalignment
issues. If the code handles them properly, you really won't like the
result. The MSP430 doesn't allow misaligned loads and stores, so they
have to be simulated by a mass of instructions. The slow bulky code that
produces isn't going to please many people. Should we just say no
misalignment is permitted? Maybe I should check how the other MSP430
compilers handle this.
The compiler MUST get the code correct for what is written. Fast code
that is incorrect is useless, slow code that functions correctly is a
much better option.
How many projects are pushing the outside of the envelope for
speed/efficiency? If you want efficiency and you think you can write it
faster in assembler then go ahead.
Ill have a look at the sample code.
Regards,
I agree that generating wrong code is no good. However, there are other
options, like complaining and not generating anything. You seem to be
taking a narrow view of efficiency. I wasn't thinking of speed, but of
the size of the resulting code. That matters very much to any embedded
developer.
Steve
