From: David Edelsohn <dje.gcc@gmail.com>
To: Jeff Law <law@redhat.com>, Eric Gallager <egall@gwmail.gwu.edu>
Cc: Nala Ginrut <mulei@gnu.org>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: Copyright assignment for Rust-GCC
Date: Tue, 5 Jan 2021 10:53:48 -0500 [thread overview]
Message-ID: <CAGWvnym5n-qsC60DzaW5x7wrFSw3YQLt-egDBEQ3iG9tJ2REqw@mail.gmail.com> (raw)
In-Reply-To: <9c7c0853-9fa3-95aa-9068-db4f20e8ae81@redhat.com>
On Tue, Jan 5, 2021 at 10:48 AM Jeff Law <law@redhat.com> wrote:
>
> On 1/4/21 11:01 PM, Eric Gallager via Gcc wrote:
> > On Mon, Jan 4, 2021 at 11:13 AM David Edelsohn via Gcc <gcc@gcc.gnu.org>
> > wrote:
> >
> >> On Mon, Jan 4, 2021 at 5:29 AM Nala Ginrut via Gcc <gcc@gcc.gnu.org>
> >> wrote:
> >>> Hi Folks!
> >>> This mail is about the development of Rust frontend of GCC.
> >>>
> >>> To avoid misunderstanding, please let me introduce Rust-GCC briefly.
> >>> In 2013, Philip Herron had announced the project in GCC mailing-list:
> >>> https://gcc.gnu.org/legacy-ml/gcc/2013-12/msg00017.html
> >>> In 2019, @SimplyTheOther had contributed the almost complete parser and
> >>> AST.
> >>> And I helped to do some trivial work to make it work with the latest GCC
> >>> at that time.
> >>> Of course there are more contributors that I can't mention one by one.
> >>> At that time, a small community of Rust-GCC had formed. We're interested
> >>> in continuing it till it can be merged into GCC.
> >>> https://github.com/Rust-GCC/gccrs
> >>> So this is the brief history.
> >>>
> >>> Now we have a question, when should we assign copyright paper for GNU?
> >>> Last time I assigned the copyright paper, I noticed that the paper
> >>> mentioned the project name. But Rust-GCC hasn't been recognized by GCC
> >>> community yet, so I'm not sure if it's the correct time to consider this
> >>> issue.
> >>>
> >>> Comments are welcome.
> >> As Jeff wrote, the assignment is for the GNU Compiler Collection (GCC)
> >> project, not for specific languages. One does /not/ submit separate
> >> assignments for GNU Fortran, GNU C++, GNU Go, GNU Ada, GNU Modula2,
> >> etc.
> >>
> >>
> > Speaking of Modula2, has that frontend made it into mainline GCC yet? I see
> > there was a bugzilla component for it added, but I don't remember seeing
> > anything about it in the changes.html file for any existing releases...
> No. I haven't seen anyone even trying in a while.
Maybe Jeff is not caught up with his email.
The GCC SC previously accepted Modula2 support. Richard Biener
approved the patch merge a few days ago and Gaius is planning to
proceed.
Thanks, David
next prev parent reply other threads:[~2021-01-05 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 10:28 Nala Ginrut
2021-01-04 16:04 ` Jeff Law
2021-01-04 16:12 ` David Edelsohn
2021-01-05 6:01 ` Eric Gallager
2021-01-05 15:48 ` Jeff Law
2021-01-05 15:53 ` David Edelsohn [this message]
2021-01-05 16:24 ` Nala Ginrut
2021-01-05 16:32 ` David Edelsohn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGWvnym5n-qsC60DzaW5x7wrFSw3YQLt-egDBEQ3iG9tJ2REqw@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=egall@gwmail.gwu.edu \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
--cc=mulei@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).