T0b1/wasmtime
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add a note about the "rustc" tag in the issue tracker.

Browse Source 
And other minor documentation fixes.
This commit is contained in:
Dan Gohman
2018-08-03 08:18:29 -07:00
parent 76a7efc8db
commit 217786e969
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
cranelift/rustc.md
View File

@@ -18,10 +18,13 @@ compete with LLVM-based release builds in terms of optimization, but for
some users, completely unoptimized code is too slow to test with, so a some users, completely unoptimized code is too slow to test with, so a
"pretty good" mode might be good enough. "pretty good" mode might be good enough.
There's plenty of work to do to achieve these goals, and if achieve There's plenty of work to do to achieve these goals, and if we achieve
them, we'll have enabled a Rust compiler written entirely in Rust, and them, we'll have enabled a Rust compiler written entirely in Rust, and
enabled faster Rust compile times for important use cases. enabled faster Rust compile times for important use cases.
See [issues tagged "rustc"](https://github.com/CraneStation/cranelift/labels/rustc)
for a list of some of the things that will be needed.
With all that said, there is a potential goal beyond that, which is to With all that said, there is a potential goal beyond that, which is to
build a full optimizing release-capable backend. We can't predict how build a full optimizing release-capable backend. We can't predict how
far Cranelift will go yet, but we do have some crazy ideas about what far Cranelift will go yet, but we do have some crazy ideas about what
@@ -34,7 +37,7 @@ such a thing might look like, including:
relationships that Rust provides directly has the potential to be relationships that Rust provides directly has the potential to be
very powerful without the need for complex alias analysis logic. very powerful without the need for complex alias analysis logic.
Unsafe blocks are an interesting challenge, however in many simple Unsafe blocks are an interesting challenge, however in many simple
cases, like Vec, it may be possible to recover what the optimizer cases, like `Vec`, it may be possible to recover what the optimizer
needs to know. needs to know.
- Design for superoptimization. Traditionally, compiler development - Design for superoptimization. Traditionally, compiler development
teams have spent many years of manual effort to identify patterns of teams have spent many years of manual effort to identify patterns of