Crossover points

(I was unable to find an email for you so feel free to close this issue)

Hello Antoyo,

Congratulations on all your success with passing libcore tests and upstream alignment with Rustc.

I thought I would reach out as I am the maintainer for GCC Rust, the front-end project. I believe there is plenty of cross over moments for both projects, and I thought I would share some of my experience with GCC for Rust. https://github.com/Rust-GCC/gccrs

As part of developing the compiler, I have found unit-type support to have some issues in GCC. First, GCC does not seem to understand zero-sized types fully, so my initial implementation for the unit type was by trying void_type_node, which has a special meaning in GCC; this caused crashes with simple assignments. Then, Tom Tromey suggested a zero precision integer to represent it; this seemed to work until we activated optimizations. So now I am using a mixture of zero precision integer and void_type_node, which is working.

For reference, here is a message I posted to GCC: https://gcc.gnu.org/pipermail/gcc-rust/2021-June/000055.html

We have also found that to make sure we support debugging in gdb correctly, we must prefix tuple field names with __, and GDB understands this convention. https://github.com/Rust-GCC/gccrs/pull/514

I hope this information is helpful; I think there is a cross over with both projects, and we can help one another with issues like this to get GENERIC to understand rust :).

Brilliant work, hope all is well. Thanks

The issue is an information-sharing discussion rather than a defined implementation task, and it names no repository files or tests. Read the linked GCC Rust message and PR 514 for context on unit types and tuple-field debugging; work is only ready once maintainers define a concrete scope and acceptance criteria.