Issue #23445: pydebug builds now use "gcc -Og" where possible, to make the resulting executable faster.

This commit is contained in:
Antoine Pitrou 2015-02-11 19:39:16 +01:00
parent 22fabe218d
commit 3d6c784371
3 changed files with 16 additions and 2 deletions

View File

@ -17,6 +17,12 @@ Library
- Issue #23361: Fix possible overflow in Windows subprocess creation code.
Build
-----
- Issue #23445: pydebug builds now use "gcc -Og" where possible, to make
the resulting executable faster.
What's New in Python 3.4.3rc1?
==============================

6
configure vendored
View File

@ -6283,7 +6283,11 @@ then
if test "$Py_DEBUG" = 'true' ; then
# Optimization messes up debuggers, so turn it off for
# debug builds.
OPT="-g -O0 -Wall $STRICT_PROTO"
if "$CC" -v --help 2>/dev/null |grep -- -Og > /dev/null; then
OPT="-g -Og -Wall $STRICT_PROTO"
else
OPT="-g -O0 -Wall $STRICT_PROTO"
fi
else
OPT="-g $WRAP -O3 -Wall $STRICT_PROTO"
fi

View File

@ -1119,7 +1119,11 @@ then
if test "$Py_DEBUG" = 'true' ; then
# Optimization messes up debuggers, so turn it off for
# debug builds.
OPT="-g -O0 -Wall $STRICT_PROTO"
if "$CC" -v --help 2>/dev/null |grep -- -Og > /dev/null; then
OPT="-g -Og -Wall $STRICT_PROTO"
else
OPT="-g -O0 -Wall $STRICT_PROTO"
fi
else
OPT="-g $WRAP -O3 -Wall $STRICT_PROTO"
fi