Message320216
> 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)! |
|
Date |
User |
Action |
Args |
2018-06-22 07:14:38 | vstinner | set | recipients:
+ vstinner, pitrou, jkloth, mcepl, petr.viktorin, methane, koobs, cstratak, Dormouse759, mi |
2018-06-22 07:14:38 | vstinner | set | messageid: <1529651678.58.0.56676864532.issue30345@psf.upfronthosting.co.za> |
2018-06-22 07:14:38 | vstinner | link | issue30345 messages |
2018-06-22 07:14:38 | vstinner | create | |
|