---
# System prepended metadata

title: GCC Rust Meeting 2023-04-03

---

# GCC Rust Meeting 2023-04-03

* Date/Time: 3rd Avril 2023 at 9h00 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-march

## Agenda

- Project Reports
    - Monthly report
    - What are we working on
- Cutoff point for GCC 13
- Questions

## Project Reports

Monthly: TODO

### What are we working on

- Arthur Cohen

- Philip Herron
    - Iterators: https://github.com/Rust-GCC/gccrs/issues/1895
        - Its going very well the full iterator code is _lots_ of libcore
        - Bugs raised a bunch of bugs from rustc 1.29 test suite
        - Bug Fixes

- Thomas Schwinge
    - <https://github.com/Rust-GCC/gccrs/issues/2050> "Add required documentation for GCC13 release"
    - Merge from GCC upstream into GCC/Rust master branch.

- Anyone else?

### When is the GCC 13 cut off?

When do we need to finish the patches we want to get into GCC13?

Philip and Arthur are in favor of having a very early cutoff and polish the release notes instead. We are not expecting that many "important" features to be added before May anyway, and certainly nothing that would be ground breaking for the users like getting `format_args!`/`println!` working, nor do we want to spend a lot of time thinking about build systems for libcore. People who will want to use the compiler at such an early stage are expected to compile the project from source or use our nightly releases when they happen anyway.

This will allow us to spend a lot of time polishing our wording and documentation for GCC 13, as well as take the time to upstream the remaining commits properly.

### Feel free to add more questions!

## Questions

