GCC Rust Meeting 2022-12-12

• Date/Time: 12th December 2022 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-november

Agenda

• Project Reports
  • Monthly report
  • What are we working on
• Upstreaming approved patches
• Questions

Project Reports

Monthly report: https://rust-gcc.github.io/reporting/2022-11-monthly-report.html

What are we working on

• Arthur:
  • Backporting patch reviews to master

GCC Patch Status

Patch status table

Rust Foundation blog-post

Should be out this week :)

Upstreaming approved patches

• PR 1673
  • Is it still needed since we'll just get squashed and merged?
    • TS: Before the git push to GCC upstream, you'll still want to test that everything works, which is what such a PR achieves.
  • Do we kill the gcc-patch-dev branch?
  • Updating and development strategy

We could do similarly to what AdaCore does, which isn't the best way to go about things :) Or we could force pull requests to have proper Changelog entry, etc. We also cannot assume that every change in the compiler will happen on github. The consensus is that we will try as we go, experiment, figure it out.

-frust-very-long and compiler explorer

• https://github.com/Rust-GCC/gccrs/pull/1540 "Implement -frust-incomplete-and-experimental-compiler-do-not-use flag"
• https://github.com/compiler-explorer/compiler-explorer/pull/4401 "Add special option for gccrs"
• Conditions for removing the flag?
  • Passing the rustc 1.49 testsuite
  • Borrow-checker
    • Subset of borrow-checking/polonius rules? (rejects more code than rustc, more restrictive, incomplete)
    • Complete borrow-checker? (all polonius rules implemented properly and passing the borrowck tests)

These conditions seem fine. Let's open up a github issue to discuss it further.

Questions

Feel free to add questions