# GCC Rust Meeting 2022-07-01

- Date/Time: 1st July 2022 at: 09h00 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

## Agenda

- Project Reports
- What are we working on
- Upstreaming
- Questions

## Project Reports

Monthly report: WIP

### What are we working on

Philbert:

1. Reply's to emails
2. Constexpr code
1. Branching off master to allow more aggressive porting approach in porting
1. no need for bors
2. allows some experimentation around some of the specific TREE_LANG_FLAGS like marking const code properly
2. I think bjorn3 has a good point here about sharing the constexpr there might be _some_ rust specific behaviour
1. see https://github.com/Rust-GCC/gccrs/issues/1334
4. Metadata exports
1. Got a basic hello wite working to a custom section in the object file
2. Working on Reading it back in when required (need to reuse code to lookup search paths i think)

Arthur:

1. Const Generics
1. Lowering, Resolving, Typechecking

### Upstreaming

https://gcc.gnu.org/pipermail/gcc/2022-June/238991.html

- Is merging up stream the same as releasing gcc-rs?
- "If it is not useful at all for (basic) real-world usage then it might be not ready yet."
- It seems that we need to make sure we have libcore libstd and liballoc all working before it makes sense at all

Response:

- Driver changes
- none
- GENERIC changes
- none
- Backend/config
- Target Options changes
- lang.opt changes?
- Thomas Schwinge WIP
- Selftest changes
- Arthur already merged them
- GCC Build changes
- None (yet) we need to add in support to compile libcore, libstd and liballoc eventually
- How our link model works
- Still WIP

Overall

Definitely still too early to answer some of the questions.

### Thanks

I wish to say thank you to the community keeping the lights on while I was away and for the support this week.