From: Palmer Dabbelt <palmer@dabbelt.com>
To: gcc@gcc.gnu.org
Subject: Re: RISC-V GCC Patchwork Sync-Up Meeting
Date: Tue, 18 Apr 2023 08:34:34 -0700 (PDT) [thread overview]
Message-ID: <mhng-3986b957-ad4e-43f9-a7e8-99f55e76fc39@palmer-ri-x1c9> (raw)
In-Reply-To: <mhng-cd68e0ab-6052-4b6a-8f33-2e12de59accf@palmer-ri-x1c9a>
On Mon, 17 Apr 2023 08:08:42 PDT (-0700), Palmer Dabbelt wrote:
> The topic of having some sort of RISC-V development meeting has come up
> a handful of times, but we never got around to actually setting anything
> up. We've had a patchwork sync meeting for the RISC-V Linux port for a
> few months now and it's been super helpful, I figured it be best to just
> do something similar for GCC.
>
> The idea is sort of copied from the glibc patchwork meeting, but I've
> never been to that before so it's a bit freeform. Essentially we just
> run through the patch backlog and try to make sure everything has been
> triaged, which can go a lot quicker in real-time. We also generally
> have time after the triaging to go through and talk about anything
> that's of interest. Like the other meetings this is very much optional
> -- in other words, we'll still reflect anything discussed onto the
> mailing lists, this is just an additional place to talk.
>
> Here's the Google Meet invite link:
>
> RISC-V GCC Patchwork Sync
> Tuesday, April 18 · 7:30 – 8:30am
> Google Meet joining info
> Video call link: https://meet.google.com/gsf-dchk-ijn
>
> Happy to move to some other service if that's better for folks, this is
> just easy to set up on my end. We can also move to another time if
> that's better for folks. We'll start with every week at 7:30am Pacific.
> I've also got a calendar with just this meeting on it, in case it's
> easier to have that imported.
>
> https://calendar.google.com/calendar/u/0?cid=Y18xZGUzNDJiN2I4ZmNhNWY4ODg3MWY5NmNkMTkzYmJmOTJkMDNiNmY0NDdlMzk5ZjFlNzA1ZWJjM2Y3Nzg5YTlkQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20
>
> Sorry for the late notice, but I'd forgotten to actually send out an
> email.
A handful of us met today and we decided a few things:
We're going to use the sourceware GCC patchwork. That's shared between
all GCC targets and there's a lot of outstanding patches for other
ports, so we're just going to look at patches with "risc-v" in the
subject (specifically
<https://patchwork.sourceware.org/project/gcc/list/?q=risc-v>). That
doesn't mean we're going to stop looking at anything else, just that
we're going to make sure all those patches get triaged regularly.
To make things manageable, we're going to just bulk archive everything
from 2022 and earlier. If there's anything in there folks want looked
it then please ping it, but the assumption is that everything is
sufficiently out of date that it at least needs to be rebased.
If that's OK with folks then I'll go archive the old RISC-V patches so
we can get things triaged more easily.
next prev parent reply other threads:[~2023-04-18 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 15:08 Palmer Dabbelt
2023-04-18 15:34 ` Palmer Dabbelt [this message]
2023-05-23 17:19 ` Palmer Dabbelt
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=mhng-3986b957-ad4e-43f9-a7e8-99f55e76fc39@palmer-ri-x1c9 \
--to=palmer@dabbelt.com \
--cc=gcc@gcc.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).