[hugovk]

This is the second suggestion at #160713 (comment).

The macOS installer uses tail-calling. This moves the tail-calling CI from a dedicated workflow, into the main workflow. This means we get coverage of tail-calling across ARM and Intel and free-threading.

Computed gotos (the non-tail-call on macOS) is still covered by most of buildbots.

One difference, we're now testing with --with-pydebug and --fast-ci. The main effect is debug slows it a bit, and resource testing is enabled so more tests are covered, but in practice it doesn't make any difference: the three jobs take ~57m16s before, 52m16s after.

We also save some CI time: the macOS job in .github/workflows/tail-call.yml only ran when certain C files changed, but it was still extra work. This is now saved.

• Issue: GitHub Action: "Tail calling interpreter" & JIT times out after 60 minutes on macOS x86_64 on building LLVM from source #159612

[itamaro]

this looks good to me, but makes me think - why not have configure detect tail-call support and enable it automatically for supported toolchains? (when the flag is not specified; if the flag is specified it should win)

[hugovk]

Sometimes a compiler claims support for something, but still has bugs, so it's not ready to be used everywhere. Especially if it's experimental for some compilers.

[miss-islington-app]

Thanks @hugovk for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14, 3.15.
🐍🍒⛏🤖

[miss-islington-app]

Sorry, @hugovk, I could not cleanly backport this to 3.14 due to a conflict.

Please backport manually with cherry_picker, see the devguide for more information.

cherry_picker 86be79a2483017f7a233b8a1a7008b8e45129ea1 3.14

[bedevere-app]

GH-161168 is a backport of this pull request to the 3.15 branch.

[bedevere-app]

GH-161169 is a backport of this pull request to the 3.14 branch.