13 ms·
GCC Rust Monthly Report #9 August 2021
- rightbyte 5y ago> Risk Impact (1-3) Likelihood (0-10) Risk (I * L) > ... table ... This gave me PTSD from FMEA analysis. Why not just write the arbitrary product only, or rank the risks, or don't rank them at all. No-one is forcing them why do this? Is this curriculum now?
- Dylan16807 5y agoWriting the product would make it confusing how they ranked them. Just ranking them would work but wouldn't represent the relative risk very well. It seems fine to me, and it's just a multiplication of two numbers, that's not overwhelming.
- athrowaway3z 5y agoIirc there are people within the rust community that think this approach to using GCC is suboptimal, and that the reason this project survives is that some professors have decided to use this as an assignment. If this is true , it wouldn't surprise me if this is the effect of them cargo-culting one of their Software-Engineering course
- Subsentient 5y agoThere are also those of us who are thrilled that a total alternative Rust parser is being written. A systems language should never be centralized to the degree Rust is.
- myrrlyn 5y agowhy not
- steveklabnik 5y ago> there are people within the rust community that think this approach to using GCC is suboptimal, This is true. There are also some (like me) who think both are great. > the reason this project survives is that some professors have decided to use this as an assignment. I am not sure that this is true.
- pwr-electronics 5y agoThe product indirectly tells you the criteria for accepting the risk as-is, but it doesn't give you any insight into how to reduce the risk. That's what severity and likelihood are for. You need all three together.
- rightbyte 5y agoI am fine with guesstimates for likelihood and severity, but the product doesn't make sense. When two guesstimates are multiplied like that, you choose the terms to give the product you want, or vice versa. The concept of trying to do a distillation of a risk assessment to a number is flawed.
- pwr-electronics 5y agoYou're right that the product number is not a very meaningful value. https://en.wikipedia.org/wiki/Risk_matrix https://en.wikipedia.org/wiki/Risk_matrix Take a look at this risk matrix. It's divided into cells that are each assigned a category. If you assigned numbers to it, you'd get conflicting results: 1. Possible (3) x Catastrophic (4) = Very High (12) 2. Likely (4) x Critical (3) = High (12) In this case, 12 can mean either High or Very High. Therefore the category is more important than the product. So basically, the product is only meaningful if the categories are defined in terms of it, which I don't think is common. Really, I should have said you need the category, rather than the product.
- htgb 5y agoI wish the blog post opened with a sentence or two for context. This is a snip from the readme [1] on GitHub: > Please note, the compiler is in a very early stage and not usable yet for compiling real Rust programs. > gccrs is a full alternative implementation of the Rust language ontop of GCC with the goal to become fully upstream with the GNU toolchain. I'm happy that there's work on alternative Rust compilers though! [1] https://github.com/Rust-GCC/gccrs https://github.com/Rust-GCC/gccrs
- eptcyka 5y agoIt's a monthly report, it's target audience isn't people who're unaware of the project IMO.
- marcellus23 5y agoIt just got posted to hacker news which is full of people who are unaware of it. It doesn’t take much work to copy paste a paragraph from the readme into the post.
- eptcyka 5y agoIt is not the author's responsibility to change the content of a report because it got linked on a link aggregator website somewhere on the internet. In fact, I'd go so far as to suggest people who feel like the content that's linked here is not too approachable to use the facilities provided to downvote the post to help other people avoid suboptimal content, if they feel it would be called for.
- marcellus23 5y agoNo it's not the author's responsibility, but if a few seconds of work could make the update accessible to far more people (and get more people excited about it), I'm not sure I see an argument against putting that context. Frankly, every article and blog post should be written that way. Sure, it's not required, but how many people were turned off because they had no idea what the article was about?
- solmag 5y agoWhy is Rustc not enough?
- bestouff 5y agoRustc is based on LLVM. A GCC backend would target more architectures and be somewhat more optimized. Plus, a different implementation of a compiler frontend is, for some, a good thing to have for a language.
- volta83 5y agorustc is backend agnostic, and currently has: an LLVM backend, a Cretonne backend, and a GCC backend. So rustc can already target _more_ architectures than this new GCC frontend, because it supports LLVM and Cretonne.
- PoignardAzur 5y ago> a Cretonne backend I think you mean Cranelift?
- volta83 5y agoOops, yes, Cretonne was renamed to Cranelift a while ago. For some reason I still call it Cretonne.
- bestouff 5y agoFor now the only production-ready backend is the historical LLVM backends.
- Tuna-Fish 5y agoBecause GCC is available on almost every platform that is in use, while LLVM is still much more limited. There are tons of embedded platforms that get rust support from this work.
- 5y ago
- als0 5y agoAre they working from a formal spec or are they comparing against rustc? Is anyone working on a spec for Rust 1.0 that could be standardized by ISO?
- volta83 5y agoThe Rust organization maintains, amongst other things, the Rust specification (called The Rust reference). If someone wants to volunteer the 1000 expert man year required to, say in 10 years (with 100 experts), submit a probably 10 year outdated version of Rust that nobody is using anymore for ISO standardization, they are free to do so. Nobody is staying in their way. I doubt anyone would care about evolving Rust in a way that's compatible with such ISO specification. Most people interested in "specification" appear to be interested in doing things that add infinitely more value than an ISO specification, like actually formalizing the language in theorem provers / proof assistants, delivering an operational semantics specification like that of WASM, etc. These deliver almost instantaneous value in that they can be used to analyze existing Rust code for "formal" correctness, can be used to implement interpreters that verify and protect Rust programs at runtime, can be used to verify more aggressive optimizations that make Rust programs faster, can be used to extend the language with new powerful features that solve real problems and are built on a strong formal foundation, etc. If you look at C and C++, which have millions of users, their ISO process only gives a tiny amount of people a lot of control over the language design and evolution. The only barrier of entry is paying the 1000$/year fee or so (no qualification, "Programming Language" background required, etc.). This type of process sounds to me diametrically opposite to anything Rust stands for. But yeah, if someone wants to submit some subset of Rust for ISO standardization, create their own sub-community, and live happily ever after, they can definitely do it.
- pjmlp 5y agoIn some domains, if Rust wants a seat at C, C++, Ada table, that will be a required step.
- galangalalgol 5y ago