January 2023 Monthly report

Overview

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

Milestone Progress

This month saw an influx of new contributors and pull-requests, which we are extremely happy about. We have opened multiple issues marked as good-first-pr in order to make sure that anyone interested in the project is able to get started. Incidentally, this also caused us to start looking at enhancing the contributing experience regarding GCC ChangeLogs and restrictions earlier than planned. This is fine, as most of the infrastructure was already in place for our work on upstreaming patches to GCC’s master branch. Overall, more than 60 pull-requests were merged this month, with 8 new people contributing to the project!

As a consequence, our continuous integration now checks whether or not your commits contain the proper format of Changelog and respect the Digital Certificate of Origin or were made under an FSF copyright assignment. We are putting together more “interactive” to make it easier for first time contributors to create these ChangeLog entries.

We also submitted our list of Google Summer of Code projects, which you can find here on the GCC wiki, in the Rust frontend section. We put together four different projects, two of them being “short” (175 hours) and the rest being “long” (350 hours) projects.

The project also made the trip to FOSDEM at the beginning of February to give a talk to the Rust devroom about some internal workings of the compiler. You can find the recording of that talk here, on the FOSDEM website.

Finally, the most important news for the project this month is the arrival of Pierre-Emmanuel Patry as a full time contributor to the project. Pierre-Emmanuel is joining us as part of his final year internship for his Masters degree, and will be mostly working on our procedural macros. Notably, his work will consist in working on a reimplementation of libproc_macro as well as the various infrastructure surrounding that crate, such as inter process communication and client/server behavior within the compiler.

Community call

We had our monthly community call on the 13th of February at 10h00 UTC. You can find some notes and minutes about the call in the agenda.

• Date/Time: 13th February 2023 at: 10h00 UTC
• Mailing list: https://gcc.gnu.org/mailman/listinfo/gcc-rust
• Zulip: https://gcc-rust.zulipchat.com/
• IRC: irc.oftc.net #gccrust
• Video Link: https://meet.jit.si/gccrs-community-call-february

Agenda: https://hackmd.io/@Rust-GCC/ByuPb2Uii

You can subscribe to our newly-created Google calendar to get updates and the dates of events the team will attend. It also contains events for our community calls.

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

Completed Activities

• [CL] 24e9bd9..b3fcf32 PR1841

• cli: Update safety warning message PR1839

• typecheck: Refactor rust-hir-trait-reference.h PR1837

• [CL] 849cea5 ec4695a PR1836

• Update `gcc-patch-dev` after first half update PR1833

• ci: Run commit format checker on push to `trying` branch PR1832

• Removed comment copy-pasted from gcc/tree.def PR1826

• parser: Fix parsing of closure param list PR1824

• parser: Improve parsing of complex generic arguments PR1823

• Support for TuplePattern in let statements PR1820

• Implement lowering ReferencePattern from AST to HIR PR1818

• ci: Require commits check to pass for bors to merge and fix CI names PR1817

• Move rust-buffered-queue.h to util folder #1766 PR1816

• parser: Allow parsing multiple reference types PR1812

• Merge upstream (dummy), “Rust front-end patches v4” PR1811

• fixed indentation in AST pretty printed expanded dump of trait. PR1810

• Run workflow PR1789

• ci: Add commit format checker PR1788

• Fix SoB lines PR1784

• Remove HIR::GroupedPattern PR1783

• Add SoB CI PR1779

• Moved operator.h to util/rust-operators.h. PR1778

• Rename file rust-ast-full-test.cc to rust-ast.cc PR1777

• fixed compiler error message on wildcard pattern within expression PR1776

• Create and use CompilePatternLet visitor for compiling let statments PR1775

• Added missing GroupedPattern visitors for code generation PR1772

• Add type resolution for grouped patterns PR1771

• Add HIR lowering for GroupedPattern PR1769

• Do not crash on empty macros expand. Fixes #1712 PR1763

• Support GroupedPattern during name resolution PR1760

• Revert 10-second timeout for each test PR1759

• [CL] ast dump and refactor PR1757

• [CL] const test cases, const generics, various fixes PR1755

• [CL] In place macro expansion and query-based type system PR1754

• [CL] type cleanups + const cleanups PR1753

• README.md: Added experimental flag & updated gccrs path PR1751

• [CL] do not lint public items PR1749

• [CL] cleanup macro expansion and parsing PR1748

• Add CL checking automation to gcc-patch-dev PR1746

• [CL] gccrs: const folding port PR1745

• [CL] Double borrow + arithmetic overflow checks + builtin refactor PR1743

• Initial type bounds checking for all type checks PR1739

• Add support for feature check. PR1737

• Change how CompileVarDecl outputs Bvariable’s PR1736

• macro: Allow builtin `MacroInvocation`s within the AST PR1735

• Add get_locus function for abstract class MetaItemInner. PR1734

• diagnostics: Add underline for tokens in diagnostics. PR1733

• testsuite: Handle Windows carriage returns properly PR1732

• Improve type checking on let statements PR1730

• Add support for generics associated type binding PR1724

• [CL] First update Changelog tryout: Updating AST dump PR1721

• format: Fix git whitespace errors PR1717

• rust: add bound parsing in parse_genericarg. PR1716

• unsafe: check use of `target<sub>feature</sub>` attribute PR1711

• Check const functions for mutable references PR1709

• Parse declarative macro (decl_macro 2.0) PR1708

• Fix frust very long typo PR1707

• update the ubuntu version PR1698

• ci: Use very long -frust flag for testing PR69

• Fix clippy warnings PR67

Contributors this month

• powerboat9 (new contributor!)
• Taym Haddadi (new contributor!)
• Pierre-Emmanuel Patry (new contributor!)
• Mahad (new contributor!)
• Abdul Rafey (new contributor!)
• Parthib (new contributor!)
• Prajwal S N (new contributor!)
• Mohd Arsh Ali (new contributor!)
• Lyra
• Thomas Schwinge
• Marc Poulhiès
• mxlol233
• Dave Evans
• tamaron

Overall Task Status

Test Cases

Bugs

Milestones Progress

We are putting together milestones regarding projects such as libproc and will update the Milestone.

Note that the intrinsics milestone percentage on github is not representative: It shows a 69% completion rate, but does not take into account the tracking issues with dozens of unresolved items. Thus the percentage is computed using the sum of issues and tracked items done divided by the sums of issues and tracked items overall. Similarly, the Update GCC’s master branch milestone contains a tracking issue containing over 200 tasks. The percentage shown here takes this into account.

Risks

Testing project

The testing project is on hold as we try and figure out some of the issues we’re running into with GitHub and our various automations around it.

Planned Activities

• Finish patch upstreaming
• Finish macro name resolution
• libproc

Detailed changelog