This is reproducible with gcc-4.5 4.5.1-8ubuntu2, the version being used at natty open. So it seems to be a longstanding bug.
Not reproducible when building with -O1 or -O2 because gcc optimizes the code out completely (getting the right answer for the address of main in this case... or at least the right parity).
This is reproducible with gcc-4.5 4.5.1-8ubuntu2, the version being used at natty open. So it seems to be a longstanding bug.
Not reproducible when building with -O1 or -O2 because gcc optimizes the code out completely (getting the right answer for the address of main in this case... or at least the right parity).
Not reproducible when building with -marm.