I don't remember if we had a Whats New for the original clang-cl issue. We should definitely mention in the whats new that clang cl building on Windows is now possible, and say PGO too.

Woops sorry pressed the wrong button!

@chris-eibl How do you plan to address:

We should definitely mention in the whats new that clang cl building on Windows is now possible, and say PGO too.

Are there more PRs for those kind of optimizations on Windows? if so, we can delay everything until they are done. Otherwise, let's mention that in the What's New entry

I don't remember if we had a Whats New for the original clang-cl issue. We should definitely mention in the whats new that clang cl building on Windows is now possible, and say PGO too.

Building with clang-cl has been possible for a very long time:#101352.

The only fixes I am aware of are just these two (and just main and current 3.14 alphas are/have been affected):

• _GENERATE_DEBUG_SECTION_WINDOWShttps://github.com/python/cpython/pull/130040/files#r1981801677 already fixed by you
• blake2module.c needs to be compiled with libhacl SIMD flags #130213: close to being fixed

So maybe just mention PGO in the Whats New?
Maybe this here and-flto=thin, too?

@zooba treats clang-cl as quite optional in#129907 (comment)
but I think a Whats New entry would not hurt.

Shall I give it a go here and mention those three things?

@Fidget-Spinner : your tail call for Windows#130040 (comment) came without What's new, too. Shall I add an entry, too?

Are there more PRs for those kind of optimizations on Windows?

I'd like to work on the many warnings clang-cl emits, but IMHO that won't go into What's new. Regarding optimizations, I think that's it atm, we can amend later, anyway.

@Fidget-Spinner : your tail call for Windows#130040 (comment) came without What's new, too. Shall I add an entry, too?

We don't need it, as there's already a whats new for tail call in general.

I think we want to be careful putting too much into What's New, since we still aren'ttechnically supporting clang-cl on Windows yet, we're really just unblocking it. No doubt if@chris-eibl sticks around it'll remain unblocked, but also, if Clang one day breaks down and MSVC is fine then we're still going to release.

A simple entry (which should already be there?) stating thatbuild.bat now has a clang-cl specific option (previously you needed to setPlatformToolset but that was the only difference) and perhaps calling out that this enables some clang-specific optimisations, referencingPCbuild\readme.txt for more info seems to hit the balance. Let's avoid using the word "support" in regards to our source code.

previously you needed to set PlatformToolset but that was the only difference

This is still true, we do not have a "clang" switch for build.bat, yet.

I am fine with entirely removing the whatsnew if that makes it easier :)

This is still true, we do not have a "clang" switch for build.bat, yet.

(Seen after submitting my review.) Oh don't we? Okay, yeah, let's treat all clang-cl specific changes as undocumented then. The day it gets an option is when we'd start putting notes in theBuild section of NEWS, and give the option a brief mention in What's New.