Skip to content

clang builds not using full LTO #342

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

Jump to bottom
Closed
Fidget-Spinner opened this issue Jan 11, 2025 · 1 comment · Fixed by #343
Closed

clang builds not using full LTO #342

Fidget-Spinner opened this issue Jan 11, 2025 · 1 comment · Fixed by #343

Comments

@Fidget-Spinner
Copy link
Contributor

Fidget-Spinner commented Jan 11, 2025 •
edited
Loading

GCC defaults to full LTO with --with-lto=yes passed. Clang defaults to ThinLTO with --with-lto=yes passed. You need --with-lto=full to enable full LTO.
@Fidget-Spinner
Copy link
Contributor Author

Fidget-Spinner commented Jan 11, 2025 •
edited
Loading

This might explain the slowdown on macOS and the rest. It has been observed in the past to cause a tremendous slowdown for macOS python/cpython#122580.

This also means the tail-calling interpreter without with ThinLTO is already significantly faster than LTO-full 👀 .

@Fidget-Spinner Fidget-Spinner mentioned this issue Jan 11, 2025
Merged
@Fidget-Spinner Fidget-Spinner mentioned this issue Feb 12, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use full LTO for all builds
1 participant
@Fidget-Spinner