-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Revert "Restrict COFF to a single thread when symbol count is high (#50874)" #59736
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.
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
Conversation
|
So, with this reversion, PackageCompiler will have a new GCC version requirement (GCC 11+), right? Does that requirement only apply to Windows, or does it also apply to Linux and maCOS? |
Yes - slightly older might be OK too, but GCC 8 is definitely not supported. It spits out: when used on Julia 1.11+ (JuliaLang/PackageCompiler.jl#918)
It should only apply to Windows / COFF (where we rely on these directives) |
…50874)" This reverts commit eb4416b. As of LLVM 16, we automatically emit: .drectve `-exclude-symbols:"<symbol>"` which mitigates this issue where it is supported by the linker (which is the case for at least GCC 11+ and LLD 14+). PackageCompiler on Windows now ships GCC 14 (JuliaLang/PackageCompiler.jl#1012), so we should no longer need this workaround that can make a 15-minute sysimage compilation take an hour+
662ba14 to
a3fd784
Compare
|
SGTM. We bundle the gcc on Windows. In theory people could override with their own gcc, so in theory we should document the Windows-specfici gcc 11+ requirement somewhere. But most people will use the bundled gcc on Windows, so it's not super pressing to add the docs. |
…50874)" (#59736) This reverts commit eb4416b. As of LLVM 16, we automatically emit: ``` .drectve `-exclude-symbols:"<symbol>"` ``` which mitigates this issue where it is supported by the linker (GCC 11+ and LLD 14+ are tested working) PackageCompiler on Windows now ships GCC 14 (JuliaLang/PackageCompiler.jl#1012), so we should no longer need this workaround that can make a 15-minute sysimage compilation take an hour+ (cherry picked from commit 1cba9c2)
…50874)" (#59736) This reverts commit eb4416b. As of LLVM 16, we automatically emit: ``` .drectve `-exclude-symbols:"<symbol>"` ``` which mitigates this issue where it is supported by the linker (GCC 11+ and LLD 14+ are tested working) PackageCompiler on Windows now ships GCC 14 (JuliaLang/PackageCompiler.jl#1012), so we should no longer need this workaround that can make a 15-minute sysimage compilation take an hour+ (cherry picked from commit 1cba9c2)
…50874)" (#59736) This reverts commit eb4416b. As of LLVM 16, we automatically emit: ``` .drectve `-exclude-symbols:"<symbol>"` ``` which mitigates this issue where it is supported by the linker (GCC 11+ and LLD 14+ are tested working) PackageCompiler on Windows now ships GCC 14 (JuliaLang/PackageCompiler.jl#1012), so we should no longer need this workaround that can make a 15-minute sysimage compilation take an hour+ (cherry picked from commit 1cba9c2)
This reverts commit eb4416b.
As of LLVM 16, we automatically emit:
which mitigates this issue where it is supported by the linker (GCC 11+ and LLD 14+ are tested working)
PackageCompiler on Windows now ships GCC 14 (JuliaLang/PackageCompiler.jl#1012), so we should no longer need this workaround that can make a 15-minute sysimage compilation take an hour+