Hi, On Wed, Apr 02 2025, Leul Abiy via Gcc wrote: > Dear Sir/Madam, > > I would like to work on the rust frontend for this summer.
We are delighted you found contributing to GCC interesting. > I am trying to > break down all the steps for the first project in the rust frontend. So far > I plan on creating the visitor class as stated and then using it to deal > with all the different types of errors such as dead code, and unused > variables. Can you go into a little more depth on the project? Please note that Rust GCC projects are a bit special in the sense that they are often discussed primarily on Zulip of the GCC-Rust team: https://gcc-rust.zulipchat.com/ So you may want to reach out to the GCC-Rust community primarily there. > For example > what is GCC internal infrastructure that is currently being used called? Is > it GIMPLE (according to chatgpt)? While the rust front-end eventually lowers their ASTs into GIMPLE (possibly through GENERIC IR, I'm not actually sure), I assume that most of their projects work on their own AST representation. > > I would also like to maybe test this code with maybe an unused variable and > put a breakpoint in the GIMPLE. This will help me see the workflow better. > Please try to guide me into doing this if possible. I have not double checked, but I think that warnings about totally unused variables is done in the front-ends and so not on GIMPLE (as opposed to e.g. warnings about unused return values of functions which have an attribute that says it should really be used somehow). So I really suggest bringing this up in the Zulip forum. Good luck! Martin
