T

tdeagan

Wed, Jan 14, 2015 9:36 PM

The optimizer is optimizing out some of the key variables I want to watch. I
found this section in openscad.pro:

and changed it to -O0, which I fantasized would turn off optimization (at
the risk of the error above.

Some of the vars I was interested in appeared, so I must have changed
something, but others, e.g. the length of the axes, l, were optimized out.
I had imagined that nothing should be optimized out with -O0, but nope.

Any idea of a simple (or preferred) way to turn optimization off? I'd
prefer something system rather than a function pragma or volatile for a var,
but I"ll take anything that works.

--
View this message in context: http://forum.openscad.org/Debugging-optimized-out-vars-on-Windows-tp11040.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

The optimizer is optimizing out some of the key variables I want to watch. I found this section in openscad.pro: and changed it to -O0, which I fantasized would turn off optimization (at the risk of the error above. Some of the vars I was interested in appeared, so I must have changed something, but others, e.g. the length of the axes, l, were optimized out. I had imagined that nothing should be optimized out with -O0, but nope. Any idea of a simple (or preferred) way to turn optimization off? I'd prefer something system rather than a function pragma or volatile for a var, but I"ll take anything that works. -- View this message in context: http://forum.openscad.org/Debugging-optimized-out-vars-on-Windows-tp11040.html Sent from the OpenSCAD mailing list archive at Nabble.com.

T

tdeagan

Wed, Jan 14, 2015 10:19 PM

I should apologize to those reading via the mail list. I used raw tags to
format my code segment. The section that disappeared in the mail was:

mingw* {

needed to prevent compilation error on MSYS2:

as.exe: objects/cgalutils.o: too many sections (76541)

using -Wa,-mbig-obj did not help

debug: QMAKE_CXXFLAGS += -O1
}

I replaced the -O1 with -O0.

--
View this message in context: http://forum.openscad.org/Debugging-optimized-out-vars-on-Windows-tp11040p11041.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

I should apologize to those reading via the mail list. I used raw tags to format my code segment. The section that disappeared in the mail was: mingw* { # needed to prevent compilation error on MSYS2: # as.exe: objects/cgalutils.o: too many sections (76541) # using -Wa,-mbig-obj did not help debug: QMAKE_CXXFLAGS += -O1 } I replaced the -O1 with -O0. -- View this message in context: http://forum.openscad.org/Debugging-optimized-out-vars-on-Windows-tp11040p11041.html Sent from the OpenSCAD mailing list archive at Nabble.com.

MK

Marius Kintel

Wed, Jan 14, 2015 10:20 PM

On Jan 14, 2015, at 16:36 PM, tdeagan tim@deagan.net wrote:

The optimizer is optimizing out some of the key variables I want to watch. I
found this section in openscad.pro:

Is the debug build still broken on msys?

-Marius

On Jan 14, 2015, at 16:36 PM, tdeagan <tim@deagan.net> wrote: > The optimizer is optimizing out some of the key variables I want to watch. I > found this section in openscad.pro: > Is the debug build still broken on msys? -Marius

T

tdeagan

Wed, Jan 14, 2015 10:39 PM

kintel wrote

Is the debug build still broken on msys?

-Marius

I'm getting a successful build with both -O options. I haven't run the
entire test suite, but the app is running fine and working with the Qt
debugger. I just can't see the values for significant variables.

--
View this message in context: http://forum.openscad.org/Debugging-optimized-out-vars-on-Windows-tp11040p11043.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

kintel wrote > Is the debug build still broken on msys? > > -Marius I'm getting a successful build with both -O options. I haven't run the entire test suite, but the app is running fine and working with the Qt debugger. I just can't see the values for significant variables. -- View this message in context: http://forum.openscad.org/Debugging-optimized-out-vars-on-Windows-tp11040p11043.html Sent from the OpenSCAD mailing list archive at Nabble.com.

MK

Marius Kintel

Wed, Jan 14, 2015 10:42 PM

On Jan 14, 2015, at 17:39 PM, tdeagan tim@deagan.net wrote:

I'm getting a successful build with both -O options. I haven't run the
entire test suite, but the app is running fine and working with the Qt
debugger. I just can't see the values for significant variables.

I was referring to the actual debug build. On Unix systems, we build debug version using "qmake CONFIG+=debug”.
I know that was not working properly on Windows, but not sure about the state of that.

-Marius

On Jan 14, 2015, at 17:39 PM, tdeagan <tim@deagan.net> wrote: > I'm getting a successful build with both -O options. I haven't run the > entire test suite, but the app is running fine and working with the Qt > debugger. I just can't see the values for significant variables. > I was referring to the actual debug build. On Unix systems, we build debug version using "qmake CONFIG+=debug”. I know that was not working properly on Windows, but not sure about the state of that. -Marius

T

tdeagan

Wed, Jan 14, 2015 10:58 PM

I was referring to the actual debug build. On Unix systems, we build debug
version using "qmake CONFIG+=debug”.
I know that was not working properly on Windows, but not sure about the
state of that.

-Marius

Sorry, yes, this is the debug build. I set up a new build kit in Qt using:
qmake.exe C:\msys64\home\tdeagan\openscad\openscad.pro -r -spec win32-g++
"CONFIG+=debug"

Worked like a champ (I did follow the instructions for the QScintilla debug
libs.)

I did have to do a rebuild all to get past some initial linking issues. But
it worked great after that.

--
View this message in context: http://forum.openscad.org/Debugging-optimized-out-vars-on-Windows-tp11040p11047.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

> I was referring to the actual debug build. On Unix systems, we build debug > version using "qmake CONFIG+=debug”. > I know that was not working properly on Windows, but not sure about the > state of that. > > -Marius Sorry, yes, this is the debug build. I set up a new build kit in Qt using: qmake.exe C:\msys64\home\tdeagan\openscad\openscad.pro -r -spec win32-g++ "CONFIG+=debug" Worked like a champ (I did follow the instructions for the QScintilla debug libs.) I did have to do a rebuild all to get past some initial linking issues. But it worked great after that. -- View this message in context: http://forum.openscad.org/Debugging-optimized-out-vars-on-Windows-tp11040p11047.html Sent from the OpenSCAD mailing list archive at Nabble.com.

discuss@lists.openscad.org

Debugging optimized out vars on Windows

needed to prevent compilation error on MSYS2:

as.exe: objects/cgalutils.o: too many sections (76541)

using -Wa,-mbig-obj did not help