On Tue, May 25, 2021 at 7:49 PM Inada Naoki <[email protected]> wrote:
> On Tue, May 25, 2021 at 5:38 AM Guido van Rossum <[email protected]> wrote: > > > > To the contrary, I think if you want the CI jobs to be faster you should > add the CFLAGS to the configure call used to run the CI jobs. > > > > -Og makes it faster not only CI jobs, but also everyday "edit code and > run `make test` with all assertions" cycles. > > I don't have opinion which should be default. (+0 for -O0). > I use -Og by default and use -O0 only when I need anyway. > Agreed, what we do today is already fine. -Og or -O1 are decent options for fast unoptimized builds that lead to increased productivity in the common case. Actually firing up a debugger on CPython's C code is not the common thing for a developer to do. When someone wants to do that, they should build with the relevant compiler for that purpose. ie: Skip should do this. If there is confusion about the meaning of --with-pydebug, that's just a documentation/help-text update to be made. -gps FWIW, we can disable optimization per-file basis during debugging. > > // Put this line on files you want to debug. > #pragma GCC optimize ("O0") > > Regards, > > -- > Inada Naoki <[email protected]> > _______________________________________________ > Python-Dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/OJJZKWS446PJPXHUBNUVIYE756D5HHP4/ > Code of Conduct: http://python.org/psf/codeofconduct/ >
_______________________________________________ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/PMOP7CQHRHB7C5737E5BKRIBXHX5PBHX/ Code of Conduct: http://python.org/psf/codeofconduct/
