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 vstinner
Recipients Dormouse759, cstratak, jkloth, koobs, mcepl, methane, mi, petr.viktorin, pitrou, vstinner
Date 2018-06-22.07:14:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I created backports to 2.7, 3.6 and 3.7 branches: do you see any reason to not fix in these branches? (Any reason to not add -g to $LTOFLAGS?)

Honestly, the risk is very low: only "./configure --with-lto" is impacted and the addition of -g is protected by $ac_cv_prog_cc_g in configure. The -g flag just asks to copy debug symbols, it should not impact compiler performances.
Anyway, if something goes wrong, obviously we can revert the change and see for a different fix.

Thanks cstratak for the bug report, and thanks Marcel Plch for the proposed fix (it works well)!
Date User Action Args
2018-06-22 07:14:38vstinnersetrecipients: + vstinner, pitrou, jkloth, mcepl, petr.viktorin, methane, koobs, cstratak, Dormouse759, mi
2018-06-22 07:14:38vstinnersetmessageid: <>
2018-06-22 07:14:38vstinnerlinkissue30345 messages
2018-06-22 07:14:38vstinnercreate