4 ms·
Yes. You will never have a startup test of all the instructions used, in all the circumstances where they are used. Startup tests are useful for checking the pr
by ncmncm 5y ago
Yes. You will never have a startup test of all the instructions used, in all the circumstances where they are used. Startup tests are useful for checking the presence or absence of certain advertised features, such as SIMD instructions. They are useless for buggy compilers and buggy chip implementations.
And, what would the code do if it detected such a bug? Abort, or run other code that works OK anyway. So, run that code all the time, and you don't need to try to check.
- Gibbon1 5y agoOn an AVR if you write this in C PORTB |= (1<<4); You get this in assembly sbi PORTB, PINB4 However if you write PORTB = PORTB | (1<<4)l The compiler instead emits. sbi PORTB, PINB4 I ported some code once where they went to the trouble of defining the registers as bit fields. In that case portb.pin4 = 1; compiled to sbi PORTB, PINB4