Re: Rust front-end patches v4

2022-12-13 Thread Arthur Cohen
Hi Martin, On 12/13/22 14:30, Martin Liška wrote: On 12/13/22 14:26, Arthur Cohen wrote: Thank you, and congratulations, to all the contributors. We thank you!! Congratulations. Thank you :) I have one question: do you have a list of supported architectures Rust FE can support right now?

Re: Rust front-end patches v4

2022-12-13 Thread Arthur Cohen
We've also added one more commit, which only affects files inside the Rust front-end folder. This commit adds an experimental flag, which blocks the compilation of Rust code when not used. We hope this helps indicate to users that the compiler is not yet ready, but can still be experimented wit

Re: Rust front-end patches v4

2022-12-13 Thread Martin Liška
On 12/13/22 14:26, Arthur Cohen wrote: > Thank you, and congratulations, to all the contributors. We thank you!! Congratulations. I have one question: do you have a list of supported architectures Rust FE can support right now? What are you plans for GCC 13.1 release? Cheers, Martin > > All th

Re: Rust front-end patches v4

2022-12-13 Thread Arthur Cohen
Hi everyone, I have pushed the commits onto master. Thanks again for all the reviews and support. Thank you, and congratulations, to all the contributors. All the best, Arthur On 12/6/22 12:03, Richard Biener via Gcc-rust wrote: On Tue, Dec 6, 2022 at 11:11 AM wrote: This patchset conta

Re: Rust front-end patches v4

2022-12-10 Thread Thomas Schwinge
Hi Martin! On 2022-12-09T14:24:18+0100, Martin Liška wrote: > I noticed a minor git issues when I tried [applying] the patches: [...] > > Can you please take a look at that? Done via "Fix whitespace errors". I've then force-updated the staging branc

Re: Rust front-end patches v4

2022-12-09 Thread Martin Liška
On 12/6/22 11:13, arthur.co...@embecosm.com wrote: > Similarly to the previous round of patches, this patchset does not contain any > new features - only fixes for the reviews of the v3. New features will follow > shortly once that first patchset is merged. > > Once again, thank you to all the con

Re: Rust front-end patches v4

2022-12-06 Thread Mark Wielaard via Gcc-rust
Hi John, On Tue, Dec 06, 2022 at 12:57:17PM +0100, John Paul Adrian Glaubitz wrote: > On 12/6/22 12:40, Arthur Cohen wrote: > > > Can't wait to see this becoming available in the distributions :D. > > > > > > I will make sure we get the frontend enabled in Debian as soon as > > > possible. > >

Re: Rust front-end patches v4

2022-12-06 Thread John Paul Adrian Glaubitz
On 12/6/22 12:40, Arthur Cohen wrote: Can't wait to see this becoming available in the distributions :D. I will make sure we get the frontend enabled in Debian as soon as possible. Haha, I appreciate the enthusiasm :) Please note however that despite the language being in, the compiler is sti

Re: Rust front-end patches v4

2022-12-06 Thread Iain Buclaw via Gcc-rust
Excerpts from Richard Biener via Gcc-patches's message of Dezember 6, 2022 12:03 pm: > On Tue, Dec 6, 2022 at 11:11 AM wrote: >> >> This patchset contains the fixed version of our most recent patchset. We >> have fixed most of the issues noted in the previous round of reviews, and are >> keeping

Re: Rust front-end patches v4

2022-12-06 Thread Arthur Cohen
On 12/6/22 12:09, John Paul Adrian Glaubitz wrote: On 12/6/22 12:03, Richard Biener via Gcc-rust wrote: On Tue, Dec 6, 2022 at 11:11 AM wrote: This patchset contains the fixed version of our most recent patchset. We have fixed most of the issues noted in the previous round of reviews, and

Re: Rust front-end patches v4

2022-12-06 Thread John Paul Adrian Glaubitz
On 12/6/22 12:03, Richard Biener via Gcc-rust wrote: On Tue, Dec 6, 2022 at 11:11 AM wrote: This patchset contains the fixed version of our most recent patchset. We have fixed most of the issues noted in the previous round of reviews, and are keeping some for later as they would otherwise crea

Re: Rust front-end patches v4

2022-12-06 Thread Richard Biener via Gcc-rust
On Tue, Dec 6, 2022 at 11:11 AM wrote: > > This patchset contains the fixed version of our most recent patchset. We > have fixed most of the issues noted in the previous round of reviews, and are > keeping some for later as they would otherwise create too many conflicts with > our updated developm