3 ms·

> ... the compiler is allowed to do literally anything ... and yet he makes the claim that "bar() is invoked" which is not only incorrect (bar may or may not b

• Gibbon1 12y ago
  I think my point is dereferencing a pointer address zero is 'undefined' but here is the rub, what happens is entirely out of the optimizer and compilers control because it depends on the context that the program is run under. One can't determine at compile time what will happen. In fact the compiler can't make any assumptions about a pointer whose value has been hard coded. uint8_t b = (uint8_t) 0x30; // 0x30 is the address of PORT D on an AVR Atmega8
• wtallis 12y ago
  "bar() is invoked" is not incorrect. It's perfectly legal for a compiler to produce this result. It's just not mandatory that all compilers do so. There's nothing wrong with the question postulating that a particular compiler behaves this way; the point of the question is to remind the programmer that they have to expect and be prepared for variance between compilers when it's permitted by the standard.