Skip to content

Add support in the dart VM build process to enable boot strapping of the Dart Front End #30374

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
a-siva opened this issue Aug 9, 2017 · 3 comments
Assignees
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.

Comments

@a-siva
Copy link
Contributor

a-siva commented Aug 9, 2017

Currently the dart VM build process uses the C++ VM parser to run the Dart Front End, this needs to change as we will be deleting the C++ VM parser. We need a scheme of storing a bootstrapped version of the Dart Front End as a kernel dill file and use taht to bootstrap the build process.

@a-siva a-siva added the area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. label Aug 9, 2017
@a-siva a-siva self-assigned this Aug 9, 2017
@a-siva a-siva added this to the 2.0-alpha milestone Nov 7, 2017
@a-siva a-siva modified the milestones: 2.0-alpha1, 2.0-alpha2 Jan 31, 2018
@JekCharlsonYu JekCharlsonYu modified the milestones: 2.0-alpha2, I/O Beta 3 Feb 23, 2018
@dgrove dgrove removed this from the I/O Beta 3 milestone Mar 15, 2018
@dgrove
Copy link
Contributor

dgrove commented Mar 22, 2018

@a-siva is this needed prior to Dart2 Stable?

@a-siva
Copy link
Contributor Author

a-siva commented Mar 22, 2018

This is again something we need before deprecating Dart1, maybe under the bucket 'DeprecateDart'

@a-siva
Copy link
Contributor Author

a-siva commented Dec 10, 2018

This is done, closing issue.

@a-siva a-siva closed this as completed Dec 10, 2018
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.
Projects
None yet
Development

No branches or pull requests

3 participants