Have a separate clean-profile make target

This allows us not to call make clean from the PGO task.

Author: hroncok

Makefile.pre.in

@@ -837,7 +837,7 @@ check-app-store-compliance:
 
 # Profile generation build must start from a clean tree.
 profile-clean-stamp:
-	$(MAKE) clean
+	$(MAKE) clean-profile
 	touch $@
 
 # Compile with profile generation enabled.
@@ -3257,13 +3257,21 @@ profile-removal:
 	rm -f profile-run-stamp
 	rm -f profile-bolt-stamp
 
-.PHONY: clean
-clean: clean-retain-profile clean-bolt
+.PHONY: clean-profile
+clean-profile: clean-retain-profile clean-bolt
 	@if test @DEF_MAKE_ALL_RULE@ = profile-opt -o @DEF_MAKE_ALL_RULE@ = bolt-opt; then \
 		rm -f profile-gen-stamp profile-clean-stamp; \
 		$(MAKE) profile-removal; \
 	fi
 
+# gh-141808: The JIT stencils are deliberately kept in clean-profile
+.PHONY: clean-jit-stencils
+clean-jit-stencils:
+	-rm -f jit_stencils*.h
+
+.PHONY: clean
+clean: clean-profile clean-jit-stencils
+
 .PHONY: clobber
 clobber: clean
 	-rm -f $(BUILDPYTHON) $(LIBRARY) $(LDLIBRARY) $(DLLLIBRARY) \
@@ -3276,11 +3284,6 @@ clobber: clean
 	-rm -f python-config.py python-config
 	-rm -rf cross-build
 
-# gh-141808: The JIT stencils are deliberately kept in make clean(-retain-profile)
-.PHONY: clean-jit-stencils
-clean-jit-stencils:
-	-rm -f jit_stencils*.h
-
 # Make things extra clean, before making a distribution:
 # remove all generated files, even Makefile[.pre]
 # Keep configure and Python-ast.[ch], it's possible they can't be generated

Misc/NEWS.d/next/Build/2025-11-20-23-15-39.gh-issue-141808.NEewZC.rst

@@ -1,4 +1,4 @@
-When running ``make clean`` or ``make clean-retain-profile``, keep the
+When running ``make clean-retain-profile``, keep the
 generated JIT stencils. That way, the stencils are not generated twice when
 Profile-guided optimization (PGO) is used. It also allows distributors to
 supply their own pre-built JIT stencils.