philberty

6 ms·

1.
by philberty 3y ago
No core _is_ the Rust language, libcore is just a library which adds the "Rust abstractions" so you can actually write a for loop or create a slice or deref, add or anything else. Libcore just gets compiled like any other rust cra
2.
by philberty 3y ago
The biggest problem Rust has is that "no_core" is so poorly understood at this point that i doubt a comprehensive spec is even possible to explain: 1. Type inference taking into account higher ranked trait bounds - Slices in l
3.
by philberty 4y ago
This is true, I tried to make gccrs only have the AST and go from that stright to GCC GENERIC. This had a lot of problems for Rust in my opinion. Many things in Rust are syntactic sugar and can be handled by desugaring the AST into another
4.
by philberty 4y ago
Thanks @steveklabnik we basically have the same in gccrs: 1. AST 2. HIR 3. THIR (side-table lookups) 4. GCC Generic We basically skip MIR in gccrs. Its pretty sensible to have other IR's, we have many passes in gccrs simplifying things
5.
by philberty 4y ago
I'm personally pretty excited to see where this goes. It could be the best way for gccrs to version itself. There are some immediate aspects I am pretty interested in relation to the spec: 1. Method resolution 2. Unstable? In particula
6.
by philberty 4y ago
I would love to do a crater run, it could be be pretty exciting since we have our cargo gccrs layer. I think once we get libcore working, we could look at no_std crates :)
7.
GCC Rust Monthly Report #16 April 2022(thephilbert.io)
28 points by philberty 4y ago|4 comments
8.
by philberty 4y ago
We are starting to track the development progress against portions of the Rustc testsuite. Also finally got slices in! :)
9.
by philberty 5y ago
I can do that. Thats a nice idea too.
10.
by philberty 5y ago
Hello World :) I am working on a blog post reviewing 1 year's worth of progress which should be up some time next week.
11.
by philberty 5y ago
It is indeed early to say, but the design of the compiler pipeline is very different to rustc, it is a more traditional pass based system with plenty of side table lookups. Some of the notions are similar we are using HIR but we are not usi
12.
GCC Rust Monthly Report – October 2021(thephilbert.io)
82 points by philberty 5y ago|17 comments
13.
by philberty 5y ago
Hello world :)
14.
by philberty 5y ago
That's a good idea! Your comment means alot to me, thank you I put alot of work into my reports and will be trying to present them on my YouTube more regularly https://youtube.com/user/redzor812 I am really inspir
15.
by philberty 5y ago
Hello this is Philip the author of these reports and lead for the GCC Rust project. I feel its only fair to point out that the comment you link to the author is not a "main dev for gccrs". I wrote part of the reasons for why I am
16.
by philberty 5y ago
Overall 2 major question come up about GCC Rust and they are not easy to answer but here is part of my perspective on the issue. 1. Keep up with rustc language development 2. How do we handle inconsistencies in behaviour For inconsistencies
17.
by philberty 5y ago
Hi, this is Philip, the author of these reports. Sorry if this is confusing, but these are the reports I make weekly and present to Open Source Security, Embecosm and the GCC Steering committee. As this work is all open-source, I wanted to