-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Restore batch mode compiler support for dartk and dartkp configurations #31585
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
Labels
area-vm
Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
front-end-kernel
legacy-area-front-end
Legacy: Use area-dart-model instead.
P0
A serious issue requiring immediate resolution
Comments
/cc @alexmarkov @a-siva |
Enabled in -cdartkp --strong in 8c38a41 |
The CL caused regressions, talked to Martin and reverted it in https://dart.googlesource.com/sdk/+/af0b27480a30bea4c87ab34b8d4f712319fcd3f5 |
A re-land of that CL is in-progress and more CLs are in preparation. |
whesse
pushed a commit
that referenced
this issue
Dec 12, 2017
Preliminary testing shows, this increases performance by around 20%. The main benefit is by re-using a warmed-up VM and not start one from scratch for every compilation. Going forward we can do more optimizations, e.g. reading the platform dill file only once into memory (instead of repeatedly) ... => This requires us using the new state-full IKG compiler. Issue #31585 Change-Id: I2d3448783fc118611baf4671187a897227a65a6c Reviewed-on: https://dart-review.googlesource.com/28400 Reviewed-by: Vyacheslav Egorov <[email protected]>
whesse
pushed a commit
that referenced
this issue
Dec 12, 2017
Issue #31585 Change-Id: I70790a33cfbfbc7c2c48c6e77074f955d6de7e01 Reviewed-on: https://dart-review.googlesource.com/28280 Commit-Queue: Martin Kustermann <[email protected]> Reviewed-by: Vyacheslav Egorov <[email protected]>
whesse
pushed a commit
that referenced
this issue
Dec 12, 2017
…trong Issue #31585 Change-Id: Ife12640a61513a0312fcfc3713f1a44f69c1ac9a Reviewed-on: https://dart-review.googlesource.com/28621 Reviewed-by: Vyacheslav Egorov <[email protected]>
whesse
pushed a commit
that referenced
this issue
Dec 12, 2017
This makes isolate tests fail, since we no longer run from "source" (or rather use the kernel-isolate to to "source -> dill" for us). The special vm/cc suite will continue to be run via the kerne-isolate, so we have the coverage for these (which probably include reload tests). Issue #31585 Change-Id: I51bd2f9345d650b4ff2a98aa1c8365c765e0d013 Reviewed-on: https://dart-review.googlesource.com/28722 Commit-Queue: Martin Kustermann <[email protected]> Reviewed-by: Vyacheslav Egorov <[email protected]>
whesse
pushed a commit
that referenced
this issue
Dec 12, 2017
…atch and non-batch mode) Issue #31585 Change-Id: Ibca196103b868177afa0ab9e15c913bbea2474ed Reviewed-on: https://dart-review.googlesource.com/28760 Reviewed-by: Vyacheslav Egorov <[email protected]>
whesse
pushed a commit
that referenced
this issue
Dec 12, 2017
The batch runner uses an exitCode of 1 to signal compile-time errors, which we need to support in the VMKernelCompilationCommandOutput. Furthermore allow running the output of a dart -> kernel compilation on the VM even though we expect an compile-time error (sometimes the frontend has bugs and doesn't emit the compile-time errors and we need to run the VM to get them) Issue #31585 Change-Id: I8b4c34557dbf3de487247d75b02777bacbd452c1 Reviewed-on: https://dart-review.googlesource.com/28642 Reviewed-by: Martin Kustermann <[email protected]>
whesse
pushed a commit
that referenced
this issue
Dec 12, 2017
…el compilation Issue #31585 Change-Id: I0e4c57f57efa39375728f6a718fb675c6f97cd94 Reviewed-on: https://dart-review.googlesource.com/28820 Reviewed-by: Martin Kustermann <[email protected]>
whesse
pushed a commit
that referenced
this issue
Dec 13, 2017
Our build files use non-appjit snapshots for kernel-service for certain architectures, e.g. simulators. Issue #31585 Change-Id: I5162b8fe266f97710c50c347ae20b53cd66cf75d Reviewed-on: https://dart-review.googlesource.com/29240 Commit-Queue: Martin Kustermann <[email protected]> Reviewed-by: Vyacheslav Egorov <[email protected]>
whesse
pushed a commit
that referenced
this issue
Dec 14, 2017
Issue #31585 Change-Id: I19f9507e0f2285c6b2dd29ca5991487dfb99fdb8 Reviewed-on: https://dart-review.googlesource.com/29581 Reviewed-by: Vyacheslav Egorov <[email protected]> Commit-Queue: Martin Kustermann <[email protected]>
whesse
pushed a commit
that referenced
this issue
Dec 14, 2017
Issue #31585 Change-Id: I5211c7d8fb16ea60509916bf525cc36ac05dd3a9 Reviewed-on: https://dart-review.googlesource.com/29591 Reviewed-by: Vyacheslav Egorov <[email protected]> Commit-Queue: Martin Kustermann <[email protected]>
So this has been working for a while, I've kept the bug open so far for the following things:
Will close this issue therefore. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-vm
Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
front-end-kernel
legacy-area-front-end
Legacy: Use area-dart-model instead.
P0
A serious issue requiring immediate resolution
Currently we use kernel isolate in all dartk and non-strong dartkp modes. This allows us to compile to Kernel transparently, but leads to a lot of issues and bad performance of tests especially in simulated architectures (40x slower tests on SIMARM+dartk configuration) and precompiler mode.
Plan:
Some tests that need to perform on the fly compilation (Isolate and reload tests) would continue to use
--dfe
for now.The text was updated successfully, but these errors were encountered: