Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upinlining creates duplicates when anon-closure-class can't be eliminated after all #5950
Comments
This comment has been minimized.
This comment has been minimized.
Imported From: https://issues.scala-lang.org/browse/SI-5950?orig=1 |
This comment has been minimized.
This comment has been minimized.
@magarciaEPFL said:
|
scabug
added
enhancement
optimizer
labels
Apr 7, 2017
This comment has been minimized.
This comment has been minimized.
@lrytz should this stay open? |
This comment has been minimized.
This comment has been minimized.
let's track it here scala/scala-dev#53 |
lrytz
closed this
Mar 7, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
scabug commentedJun 19, 2012
Sometimes it happens that"
In general, whenever the instance of the anon-closure-class is used somehow.
As a result, the anon-closure-class can't be eliminated, and we end up emitting code duplicates (for the method/s that did get inlined). When compiling the compiling under
-optimize
about 600 anon-closure-classes are prone to this. In these cases it would be best not to inline at all.Somewhat related,
DeadCodeElimination
.