Program that segfaults with -Ofast
Christer Solskogen
christer.solskogen@gmail.com
Mon Jan 8 09:28:00 GMT 2018
On 08.01.2018 10:13, Andrew Haley wrote:
> On 07/01/18 21:27, Christer Solskogen wrote:
>> Fixed!
>>
>> Wanna know something funny?
>> Having a printf fixed the segfault. Without it, it would crash.
>> So the workaround in read_kickstart (memory.cpp) was to add
>> "volatile int i" instead of "int i".
>>
>> Just one simple printf("Value of i: %d\n", i); was enough to not segfault.
>
> That's probably not the real fix, unless you have another thread accessing
> i.
>
Hm.. perhaps.
Is there a way to see how the code looks like with different
optimization flags?
--
chs
More information about the Gcc-help
mailing list