Nate Ohlson

Hello all I have been selected by GSoC to work on this! @mdboom I am curious how you were able to get the unit tests to pass with the linker...

I would like to get some discussion going about performance impacts of enabling options and how much we would be willing to conceed in performance for safety. Here is an...

@corona10 Yes I am going to be implementing some tooling to keep track of new warnings that are generated by enabling these new flags, which is the next step of...

@corona10 I agree let's remove fall-through warnings and I will look into why I am not seeing those warnings when I build locally

@corona10 PR to remove fallthrough warning option: https://github.com/python/cpython/pull/121041 Just from browsing the builds from #121030 it seems that clang is only emitting warnings for fallthrough. Here are builds with warnings:...

@hugovk For the warning tooling I had initially considered if it would be feasible to add to the pipeline for each of the buildbots maybe even as a unit test...

@hugovk Awesome thank you for the input! I am moving forward with a GitHub Actions solution. > Things to consider: do we want warnings to fail the build, so that...

> Consider adding extra flags to CFLAGS_NODIST, so they only affect CPython, not third-party extensions built for it. Those might have conflicting requirements. I agree with limiting the scope of...

I started a thread to have more discussion related to this topic: https://discuss.python.org/t/new-default-compiler-options-for-safety/60057/2 Attn: @encukou @sethmlarson