Page 1 of 1

Selective Compiler Optimization

PostPosted: Sep 21, 2004 @ 5:32pm
by Bapdude

PostPosted: Sep 21, 2004 @ 5:39pm
by refractor

PostPosted: Sep 21, 2004 @ 5:53pm
by Bapdude

PostPosted: Sep 21, 2004 @ 7:12pm
by xPeterx

PostPosted: Sep 21, 2004 @ 10:12pm
by angedelamort
usually, when it's not working in release, it's because of a memory problem. But to be sure, you can always look at the assembly code to see if the compiler messed up ;)

PostPosted: Sep 22, 2004 @ 12:27am
by rcp

PostPosted: Sep 22, 2004 @ 1:51am
by Bapdude
rcp:

Thanks for your suggestion. Yes, you are correct...I should try to understand the problem rather than looking for a "bandaid" solution.

My problem basically involves flags that are set before a function call. In the "debug" version, the flags are set correctly (initialized) prior to entering the function. In the "release" version, the flags are not. It's actually VERY simple code, so I can't imagine why the compiler has a problem with it. Of course, I've seen stranger things... :D

PostPosted: Sep 22, 2004 @ 2:42am
by Dan East

PostPosted: Sep 22, 2004 @ 3:09am
by Kzinti

Stupid debug filling with zeros

PostPosted: Oct 6, 2004 @ 2:36pm
by andys

Re: Stupid debug filling with zeros

PostPosted: Oct 6, 2004 @ 4:26pm
by Kzinti

PostPosted: Oct 6, 2004 @ 7:50pm
by Dan East

PostPosted: Oct 6, 2004 @ 9:02pm
by Kzinti

PostPosted: Oct 7, 2004 @ 12:39am
by Dan East

PostPosted: Oct 7, 2004 @ 6:59am
by refractor
Heh - I also use 0xdeadbeef.