From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id BE1E33858C98 for ; Thu, 4 Apr 2024 14:38:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org BE1E33858C98 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org BE1E33858C98 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.133.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1712241505; cv=none; b=MHixP/w4Mll7PqFaF2eoQyXlAXLz1DRzo38SGU3KKjNR6bz+6Wrv7at6pPzNjB8Qt0CTJTlbdNBqP0rT04kJuchy140Zr79bxDFx4JYtEWPVFj2xsEhZ44gXU1ZBTIbTl8CbmIAmevEdiJIBRIny5gd1bzYdtPRR7SPaK+lBbb8= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1712241505; c=relaxed/simple; bh=aqguxb57KnZI6tmPw9UXE7g4hm1nNf4f4lzpvDXvod4=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=FUU1sojYfZwY+20bNHpuT/49MbephkjS2MYqGrgjhPyiXidDIaCLy9cuifXUdsajYh8A28CU/p5TyLGYcLiYgOlEWk1CAjLMl1XSZ34uGqZ/OasurKVmKQtpJQ38hcn7fyIDAuXp+7OnEZyV0bxr28jzG79BWnXK9RPrVTshBV8= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1712241503; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=7m7o86nqdp0dTK24+Qjx7kOjvYq1nZhNFz8dBjYgCOE=; b=UMnQM6W889vVvKj/cJsRyx+qsNwVDJjWycmdA7T+fSYqDkQfN1AHTFP36aUisK85uagXMi hTtvPE1vCJf3ljLKNBSpZAFtmnlX0RhPILfOy80gymmZxty+hNm4tFJBAFHvVZ4FSRYow9 KvjZZrXuFOlngzZWQ775kvMiXYK0I9Y= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-630-GenX6FwSMA2X66rjPQigLg-1; Thu, 04 Apr 2024 10:38:20 -0400 X-MC-Unique: GenX6FwSMA2X66rjPQigLg-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id A3BC58F4126; Thu, 4 Apr 2024 14:38:19 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.45.224.14]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 64A7C37FC; Thu, 4 Apr 2024 14:38:19 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.17.1/8.17.1) with ESMTPS id 434EbvNU793964 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Thu, 4 Apr 2024 16:37:57 +0200 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 434Ebv82793963; Thu, 4 Apr 2024 16:37:57 +0200 Date: Thu, 4 Apr 2024 16:37:56 +0200 From: Jakub Jelinek To: Palmer Dabbelt Cc: ewlu@rivosinc.com, gcc-patches@gcc.gnu.org, gnu-toolchain@rivosinc.com Subject: Re: [gcc-13 backport PATCH] RISC-V: Fix C23 (...) functions returning large aggregates [PR114175] Message-ID: Reply-To: Jakub Jelinek References: <20240403201736.3021296-1-ewlu@rivosinc.com> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-3.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP 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 Thu, Apr 04, 2024 at 07:28:40AM -0700, Palmer Dabbelt wrote: > I'm not sure if we need release maintainer approval, For cherry-picking one's own non-risky bugfixes for regression or documentation bugs from trunk to release branches no special approval is needed, or maintainer of the corresponding code can approve that, release manager approval is only needed when a branch is frozen before a release. > all I can find is the > 13.2.1 status report saying 13.3 is expected in the spring > . My allergies > certainly indicate it's spring, but that's kind of a wide time window... > > Maybe Jakub knows? Most likely some short time after 14.1 is released, so that one can still cherry-pick whatever was fixed on the 14 branch and there is time for those cherry-picks and testing. https://gcc.gnu.org/releases.html#timeline gives some hints... Jakub