From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) by sourceware.org (Postfix) with ESMTPS id B345B3858D1E for ; Tue, 18 Apr 2023 15:34:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org B345B3858D1E Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dabbelt.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=dabbelt.com Received: by mail-pf1-x42c.google.com with SMTP id d2e1a72fcca58-63b50a02bffso1977397b3a.2 for ; Tue, 18 Apr 2023 08:34:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dabbelt-com.20221208.gappssmtp.com; s=20221208; t=1681832075; x=1684424075; h=content-transfer-encoding:mime-version:message-id:to:from :in-reply-to:subject:date:from:to:cc:subject:date:message-id :reply-to; bh=yrL/GNSm0k+gC6E7RPc3m9L/5Clfmq29R3t/5PjLJ7U=; b=zgX9sRVi1exMcKxXzKivFFnGpV+yKF6eQQWDMAanXXToyH2j23lcMoB0C3mUTlAlpJ tGeERXHsxMHN3pt4ITuamzvdwYe4e/4xJC1iGN3pJZmQc6f9uxxyILJnWbbZJ+qL/Ztt ol6BkIbLfGVwRqPJThHhs6IqFvZjzRmIM4e+0UNmPbNxysW2YqRAIfzQ8wbcOjLZtPpL EoGrkmJxXKSVoFsaqmiWgi2vZMw6DblZYdBgjDM5duCpvqow50EL7eBKHstNtvLBd7V8 JcjEDI6KwM/jotc3oeeRVpgtafKU+WI+VvboJd9dW15dWASayd0KJEbbLpd9ZO1jSORr CYLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681832075; x=1684424075; h=content-transfer-encoding:mime-version:message-id:to:from :in-reply-to:subject:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=yrL/GNSm0k+gC6E7RPc3m9L/5Clfmq29R3t/5PjLJ7U=; b=WwQoxmX+RN1eoavBMgfH2rAVF/NwaCh7JPT1ljkL+4mMbbHdklV4w06h4wmCm4Gxzf 5d8vIIBdnLufLT4CtpTpzdwwROTZf0L9068xGIOIwG/dWlj7ymRSiMt10ujK0G1t1gpj jfszMQYFR9z825doVUyb3qUpb2B+M2tN62hnie8v82Z/PmO2TSbR34fSXnkctXBqqd2o p3xNg2VK95bAVvAeMj82Jgg3iCsVUVMewCwGIajroeO+/je8XJMhXyId5csvLdyfzo8+ X/R6MEShXrYkSDAVQ12w2O0krBXSCf1CAjuB6tAaWqsuyScv+oE+oV43vZwOFhc1CCgU DugA== X-Gm-Message-State: AAQBX9cmo1Nu+iQe1ugBpHcZXFK6Tv3vtNFGbViuK/Otv3WgdA01pa/k /8o5rY+604wLB04XkbDb/Zj83Roz2UXhq7NARKQ= X-Google-Smtp-Source: AKy350bH7hYhvqc/BIdjMIh79XbZF9M5mfRBXswMqgnyvKmkat8lUfKwHA4LW0QmXsGIZ5yg4Hbjag== X-Received: by 2002:a17:902:c941:b0:1a6:387a:6572 with SMTP id i1-20020a170902c94100b001a6387a6572mr2808304pla.13.1681832074963; Tue, 18 Apr 2023 08:34:34 -0700 (PDT) Received: from localhost ([135.180.227.0]) by smtp.gmail.com with ESMTPSA id jh17-20020a170903329100b001a04ff0e2eesm9803080plb.58.2023.04.18.08.34.34 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 18 Apr 2023 08:34:34 -0700 (PDT) Date: Tue, 18 Apr 2023 08:34:34 -0700 (PDT) X-Google-Original-Date: Tue, 18 Apr 2023 08:34:28 PDT (-0700) Subject: Re: RISC-V GCC Patchwork Sync-Up Meeting In-Reply-To: From: Palmer Dabbelt To: gcc@gcc.gnu.org Message-ID: Mime-Version: 1.0 (MHng) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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 ). 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.