Re: Rust front-end

Hi Jakub, Thanks for this, as I mentioned in my response to David we have made a table and use this link to try and see what's going on https://inbox.sourceware.org/gcc-patches/20220824115956.737931-9-philip.her...@embecosm.com/T/#rbff0bb3df2780fecd9ee3d2baa864d9140d24b54 Do you think I should se

Re: Rust front-end

Hi David We made a table to try and track this a bit better: | Patch | Reviewed | Accepted | |-+--+--| | 0001-Use-DW_ATE_UTF-for-the-Rust-char-type.patch

Re: Rust front-end

On Tue, Oct 04, 2022 at 08:42:58AM -0400, David Malcolm via Gcc wrote: > On Tue, 2022-10-04 at 13:29 +0100, Philip Herron wrote: > > Hi everyone, > > > > As the cut-off for merging is coming up in November, quite a few of > > our patches have not been reviewed yet. > > > > There are a few main is

Re: Rust front-end

On Tue, 2022-10-04 at 13:29 +0100, Philip Herron wrote: > Hi everyone, > > As the cut-off for merging is coming up in November, quite a few of > our patches have not been reviewed yet. > > There are a few main issues that have been raised so far, and we are > fixing those at the moment in prepara

Re: Rust front-end

Hi everyone, As the cut-off for merging is coming up in November, quite a few of our patches have not been reviewed yet. There are a few main issues that have been raised so far, and we are fixing those at the moment in preparation for version 3 of the patches. Is there anything else we can do to

Re: Rust front-end

On Mon, Jun 27, 2022 at 10:52 AM Philip Herron wrote: > > Hi everyone, > > Since November 2020, I've worked full-time on the Rust front-end for > GCC, thanks to Open Source Security, Inc and Embecosm. As a result, I > am writing to this mailing list to seek feedback from the collective > experienc

Re: Rust front-end

On Fri, Jul 8, 2022 at 7:32 PM Philip Herron wrote: > > Hi Richard > > Thanks for your detailed response, I took some time to figure this out > myself to give a decent response. It seems like we should keep the end > of the year as our goal to aim for but in the meantime see if we can > split patc

Re: Rust front-end

Hi Richard Thanks for your detailed response, I took some time to figure this out myself to give a decent response. It seems like we should keep the end of the year as our goal to aim for but in the meantime see if we can split patches which affect GCC over the next month or so. We have no changes

Re: Rust front-end

On Mon, Jun 27, 2022 at 4:52 PM Philip Herron wrote: > > Hi everyone, > > Since November 2020, I've worked full-time on the Rust front-end for > GCC, thanks to Open Source Security, Inc and Embecosm. As a result, I > am writing to this mailing list to seek feedback from the collective > experience

Re: Rust front-end

> One approach would be something like how the GCC Go frontend works, > which uses a library shared with the other Go compiler implementation > to parse the code, and turn it into GCC's IR, which then goes through GCC's optimizer and backend. I'm not familiar with rustc's internal working. Its cod

Re: Rust front-end

On Fri, 2019-08-23 at 11:10 -0300, Mateus Carmo Martins de Freitas Barbosa wrote: > I'm interested in working on the Rust front-end for GCC. > > So far I've cloned the repository git> > and tried to compile it as described in tF

Re: Rust front-end

On Tue, 27 Aug 2019 at 09:10, Bin.Cheng wrote: > And couple of words to the community, we may need to be more active in > order to attract new developers. IMHO, messages asking for information > shouldn't need one week to be answered? This is not really the right place to ask for information about

Re: Rust front-end

On Fri, Aug 23, 2019 at 10:11 PM Mateus Carmo Martins de Freitas Barbosa wrote: > > I'm interested in working on the Rust front-end for GCC. > > So far I've cloned the repository > and tried to compile it as described in >