Selective Compiler Optimization

by **angedelamort** » Sep 21, 2004 @ 10:12pm

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 ;)

by **rcp** » Sep 22, 2004 @ 12:27am

by **Bapdude** » Sep 22, 2004 @ 1:51am

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...

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

by **Kzinti** » Sep 22, 2004 @ 3:09am

by **andys** » Oct 6, 2004 @ 2:36pm

by **Kzinti** » Oct 6, 2004 @ 4:26pm

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

by **Kzinti** » Oct 6, 2004 @ 9:02pm

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

by **refractor** » Oct 7, 2004 @ 6:59am

Heh - I also use 0xdeadbeef.

Selective Compiler Optimization

Selective Compiler Optimization

Stupid debug filling with zeros

Re: Stupid debug filling with zeros

Sort

Forum Description

Moderators:

Forum permissions