You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The combination of LTO=none with release mode is emitting a single, enourmous file to allow for inlines at compile time. However, this performance hack, comes with a bad scaling when it comes to compilation times. Larger projects like our unit tests might take even +15 minutes just to compile.
We should remove the special handling of LTO=none + release mode and split the defs into N files to allow for faster, parallel compilation. We should also remove recently added warnings about using this combination of settings added in #3494
The text was updated successfully, but these errors were encountered:
fixscala-native#3502
This performance hack seems to be introduced when
there's no LTO option is available in scala-native (or LLVM at that
time?)
scala-native#506
fixscala-native#3502
This performance hack seems to be introduced when
there's no LTO option is available in scala-native (or LLVM at that
time?)
scala-native#506
…tive#3514)
fixscala-native#3502
This performance hack seems to be introduced when
there's no LTO option is available in scala-native (or LLVM at that
time?)
scala-native#506
The combination of LTO=none with release mode is emitting a single, enourmous file to allow for inlines at compile time. However, this performance hack, comes with a bad scaling when it comes to compilation times. Larger projects like our unit tests might take even +15 minutes just to compile.
We should remove the special handling of LTO=none + release mode and split the defs into N files to allow for faster, parallel compilation. We should also remove recently added warnings about using this combination of settings added in #3494
The text was updated successfully, but these errors were encountered: