FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

gh-128563: Clarify wording in Whats new for Tail call by Fidget-Spinner · Pull Request #130911 · python/cpython · GitHub

/ cpython Public

gh-128563: Clarify wording in Whats new for Tail call #130911

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Fidget-Spinner merged 1 commit into from
Mar 6, 2025
Conversation 3 Commits 1 Checks 0 Files changed
Merged

gh-128563: Clarify wording in Whats new for Tail call #130911

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension .rst  (1) All 1 file type selected
Viewed files
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Unified
Split
Hide whitespace
Diff view
Unified
Split
Hide whitespace
6 changes: 3 additions & 3 deletions Doc/whatsnew/3.14.rst
Show comments
View file
Open in desktop
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Show hidden characters
Original file line number Diff line number Diff line change
Expand Up @@ -301,11 +301,11 @@ For further information on how to build Python, see
cautiously revised down to 3-5%. While we expect performance results to be better

hauntsaninja Mar 7, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

thanks for updating the docs! it's been interesting following along the journey :-)
maybe a silly question, why do we expect performance numbers to be better than what we report?

Fidget-Spinner Mar 7, 2025

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

The computed goto bug in theory shouldnt affect modern systems that much, but it's unclear for now so I just put that therr.
than what we report, our estimates are more conservative due to a
`compiler bug <https://github.com/llvm/llvm-project/issues/106846>`_ found in
Clang/LLVM 19. We were unaware of this bug, and it artifically boosted
our numbers, resulting in inaccurate results. We sincerely apologize for
Clang/LLVM 19, which causes the normal interpreter to be slower. We were unaware of this bug,
resulting in inaccurate results. We sincerely apologize for
communicating results that were only accurate for certain versions of LLVM 19
and 20. At the time of writing, this bug has not yet been fixed in LLVM 19-21. Thus
any benchmarks with those versions of LLVM may produce artifically inflated numbers.
any benchmarks with those versions of LLVM may produce inaccurate numbers.
(Thanks to Nelson Elhage for bringing this to light.)

(Contributed by Ken Jin in :gh:`128563`, with ideas on how to implement this
Expand Down
Back | FazBrowse Home | New Git URL