Message 105035 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	mark.dickinson
Recipients	lemburg, mark.dickinson, pitrou, vstinner
Date	2010-05-05.14:03:47
SpamBayes Score	0.00013352367
Marked as misclassified	No
Message-id	<1273068229.98.0.576087123255.issue8625@psf.upfronthosting.co.za>
In-reply-to

Content
When doing a debug build of Python with gcc, without any previous setting of CFLAGS, the '-O2' flag is now automatically included. This behaviour started in r79218. It would be nice to restore the original behaviour, if possible, since the optimization causes difficulties when debugging. One solution would be to add '-O0' to OPT for debug builds (on gcc), as in the attached patch. You then get compiler flags including: "-g -O2 -g -O0" which is somewhat ugly, but the -O0 overrides the -O2 (I think). Does this seem like a reasonable solution?

When doing a debug build of Python with gcc, without any previous setting of CFLAGS, the '-O2' flag is now automatically included.

This behaviour started in r79218.

It would be nice to restore the original behaviour, if possible, since the optimization causes difficulties when debugging.  One solution would be to add '-O0' to OPT for debug builds (on gcc), as in the attached patch.  You then get compiler flags including:

"-g -O2 -g -O0"

which is somewhat ugly, but the -O0 overrides the -O2 (I think).  Does this seem like a reasonable solution?

History
Date	User	Action	Args
2010-05-05 14:03:50	mark.dickinson	set	recipients: + mark.dickinson, lemburg, pitrou, vstinner
2010-05-05 14:03:49	mark.dickinson	set	messageid: <1273068229.98.0.576087123255.issue8625@psf.upfronthosting.co.za>
2010-05-05 14:03:48	mark.dickinson	link	issue8625 messages
2010-05-05 14:03:48	mark.dickinson	create