STINNER Victor <vstin...@redhat.com> added the comment:
> I created backports to 2.7, 3.6 and 3.7 branches: do you see any reason to > not fix python-gdb.py 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. 0 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)! ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 2.7, Python 3.7, Python 3.8 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue30345> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
