Skip to content

Repeating deoptimizations when compiling Scala #293

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

Closed
vjovanov opened this issue Jan 31, 2018 · 2 comments
Closed

Repeating deoptimizations when compiling Scala #293

vjovanov opened this issue Jan 31, 2018 · 2 comments
Assignees

Comments

@vjovanov
Copy link
Member

When compiling scala programs there are repeating deoptimizations that seem suspicious. To easily reproduce:

git clone https://github.com/scala/compiler-benchmark.git
cd compiler-benchmark
git reset --hard 367811e9a2fe070ae34d10a7986a8a5d444b38a2
sbt
sbt> hot -psource=scalap -wi 100 -i 5 -f1 -jvm <graalvm>/Contents/Home/bin/java -jvmArgs -XX:+PrintCompilation

Observe the logs and see a few dozen methods that get compiled on every iteration of the benchmark. An example is scala.reflect.internal.tpe.TypeComparers$class::firstTry$1.

@alina-yur
Copy link
Member

@vjovanov @mur47x111 I assume this can be closed now?

@mur47x111
Copy link
Member

We have attached speculation to prevent most of the repeated deoptimization and I think this can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants