July 2024 Monthly report

Overview

Thanks again to Open Source Security, inc and Embecosm for their ongoing support for this project.

Project update

The progress done by students this month has been amazing, with multiple improvements on all projects. The tool developed by Muhammad Mahad to adapt rustc testcases into gccrs ones is almost ready, and will soon be used to import the entire rustc testsuite to our project. Jasmine Tang has made great progress on compiling her inline assembly nodes, and is now figuring out the last few details in order to support all of the inline assembly concepts used by GCC. Finally, Kushal Pal has been adding location information throughout the entire borrow-checking pass of the compiler, and we are now able to emit proper errors with nice hints for users to benefit from.

We are also joined by two new contributors this month, both spending a lot of time on some long-standing compiler issues and producing good quality work. Thank you both :)

Our 14.2 patches have not been reviewed, and thus did not make it into the 14.2 release. This is not important, as the patches only concerned documentation changes. Instead, we will be able to upstream these patches without prior reviewing from the GCC maintainers in time for the 15.1 release, as they only concern the Rust frontend files. Regarding our 15.1 milestones, we are currently tackling name resolution issues as well as solving the issue of lang_items, which have been a long-standing pain point in the compiler. They are supported in all of their facets, except when used for code generation, which has to do with how gccrs handles paths in general. Fixing this will make it easier for us to properly desugar for-loops, as well as a few other language constructs.

Community call

We will have our next monthly community call on the 12th of August at 9am UTC. You can subscribe to our calendar to see when the next one will be held. The call is open to everyone, even if you would just like to sit-in and listen. You can also subscribe to our mailing-list or join our Zulip chat to be notified of upcoming events.

• Jitsi link
• Calendar ID: 7060a0923ffebd3cb52b1afef35a28ff7b64f05962c9af84c23b1847f1f5f894@group.calendar.google.com
• Google calendar link
• iCal link

Call for contribution

• Issue 3001: Generic arguments are not disambiguated on error propagation expressions

Our error propagation expressions (expressions which use the question mark operator, of the form <expr>?) are currently forgotten in many of our AST visitors. As a result, there are unexpected cases when it comes to various parts of the compiler pipeline handling them. In that particular case, the function call’s generic arguments are not disambiguated - the compiler does not know if it needs to be handling a generic type, or a const generic value. You will need to add handling to our name resolution pass for these error propagation expressions. It would be helpful to look at the current generic disambiguation to start figuring out where it is called from, and where you need to call it.

Completed Activities

• Remove dependency on nightly Rust PR3101
• Move procedural macro tests to their own directory PR3097
• Change bug report issue template PR3095
• Change assertion of asm operand constructor PR3093
• [#2987] Patch ICE when deriving Clone and Copy PR3091
• Added options for ParseMode PR3090
• gccrs: [E0576] Associated `item` not found in given `type` PR3089
• Properly striping struct fields when using attrs PR3087
• Fix CI bootstrap build with a nightly rust compiler PR3085
• Improve error messages for operator expressions PR3084
• Add compile error to fix ICE when failing to find enum variants. PR3083
• Pin node16 by allowing old version PR3081
• gccrs: Add external test directory for testsuite adaptor PR3080
• #[may_dangle] in safe impl PR3078
• Remove unnecessary #include from rust-expr.h PR3077
• New class for bck diagnostics PR3076
• rust: fix HIR dump for MatchExpr PR3075
• Safe-guard InlineAsm structs PR3074
• Store parse result of parse_formatstring(s) PR3073
• Added FFIVector to get Polonius output on C++ side PR3058
• Fix all tests in execute to be ]

Contributors this month

• Liam Naddell (new contributor!)
• antoniospg (new contributor!)
• Mahad Muhammad
• Kushal Pal
• Jasmine Tang
• Marc Poulhiès
• Pierre-Emmanuel Patry
• Arthur Cohen

Overall Task Status

Test Cases

Bugs

Milestones Progress

Planned Activities

• Start work on required items for for loops
• Continue work on name resolution and macro expansion for core 1.49
• Start adding Detailed Changelogs to the reports again

Risks

There have been no changes to the Risk table this month

Detailed changelog