|
2 | 2 |
|
3 | 3 | This is a full alternative implementation of the Rust language on top of GCC with the goal to become fully upstream with the GNU toolchain. |
4 | 4 |
|
5 | | -As this is a front-end project, the compiler will gain full access to all of GCCs internal middle-end optimization passes which are distinct from LLVM. For example, users of this compiler can expect to use the familiar -O2 flags to tune GCC’s optimizer. Going forward, we will be happy to see more LLVM vs GCC graphs in respect to compilation speed, resulting code size and performance. |
| 5 | +As this is a front-end project, the compiler will gain full access to all of GCC's internal middle-end optimization passes which are distinct from LLVM. For example, users of this compiler can expect to use the familiar -O2 flags to tune GCC’s optimizer. Going forward, we will be happy to see more LLVM vs GCC graphs in respect to compilation speed, resulting code size and performance. |
6 | 6 |
|
7 | | -The project is still in an early phase with the goal to compile the official rust test suite. There are no immediate plans for a borrow checker as this is not required to compile rust code and is the last pass in the RustC compiler. This can be handled as a sperate project when we get to that point. |
| 7 | + |
| 8 | +The project is still in an early phase with the goal to compile the official Rust test suite. There are no immediate plans for a borrow checker as this is not required to compile rust code and is the last pass in the RustC compiler. This can be handled as a sperate project when we get to that point. |
8 | 9 |
|
9 | 10 | You can find compiler status reports over on: [https://github.com/Rust-GCC/Reporting](https://github.com/Rust-GCC/Reporting) and [https://thephilbert.io/](https://thephilbert.io/) |
10 | 11 |
|
| 12 | +### FAQ |
| 13 | + |
| 14 | +For frequently asked questions please see: [https://github.com/Rust-GCC/gccrs/wiki/Frequently-Asked-Questions](https://github.com/Rust-GCC/gccrs/wiki/Frequently-Asked-Questions) |
| 15 | + |
11 | 16 | ### Thanks |
12 | 17 |
|
13 | | -Thank you to [Open Source Security Inc.](https://www.opensrcsec.com/) and [Embecosm](https://www.embecosm.com/) for sponsering this project to move forward. |
| 18 | +Thank you to [Open Source Security Inc.](https://www.opensrcsec.com/) and [Embecosm](https://www.embecosm.com/) for sponsoring this project to move forward. |
14 | 19 |
|
15 | 20 | We appreciate all feedback from individuals on github. |
16 | 21 |
|
17 | 22 | ### Developers |
18 | 23 |
|
19 | 24 | * [Philip Herron](https://github.com/philberty/) |
20 | 25 | * [SimplyTheOther](https://github.com/simplytheother) |
| 26 | +* [Mark Wielaard](https://gnu.wildebeest.org/blog/mjw/) |
| 27 | +* [Arthur Cohen](https://github.com/CohenArthur) |
| 28 | +* [Marc Poulhiès](https://github.com/dkm) |
| 29 | +* [Thomas Schwinge](https://github.com/tschwinge) |
| 30 | +* [Wenzhang Yang](https://github.com/thomasyonug) |
| 31 | +* [John Paul Adrian Glaubitz](https://github.com/glaubitz) |
| 32 | +* [Yizhe](https://github.com/YizhePKU) |
21 | 33 | * [Nala Ginrut](https://github.com/NalaGinrut) |
22 | 34 |
|
| 35 | +Please feel free to raise a PR to add your names. |
| 36 | + |
23 | 37 | ### Get Involved |
24 | 38 |
|
25 | 39 | As this is destined to be upstreamed to GCC we require copyright assignment: [https://gcc.gnu.org/contribute.html](https://gcc.gnu.org/contribute.html). Not all contributions must be code, please try it out and feed us bugs. |
|
0 commit comments