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 828D13858D35 for ; Sun, 7 Jan 2024 22:22:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 828D13858D35 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 828D13858D35 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=1704666134; cv=none; b=NPQzumjB8Z91jktN+bpKAjZz/JoQJkgL5fGHyH13YXST8QnPkXIBNwm+JglTotuCA7LiFZBAvSTLKjfIL7rgtM69S/23bC3o8vdw1l8RpOrJtz+97Uz5xwb1a3lC7b20hsUnDbnMLBDPQiAi89qcoWYkLQOlDG0/9TO7ZKyd1pM= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1704666134; c=relaxed/simple; bh=G4Iqv0Rejz8T861xULwdEMA5/Dc0FkY9IRST/W9GBVQ=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=KRKtIrbDG8FzvWZKiQzRWpdpQT0al16y3xUWRnWY6XHjWdfaWqqHzlDLh2HoKBk8ovJWzlol35FFPGVxP6SCftab9qLh33YBbjgsH5Y9mV4OxsLejJxJyS3jCJ7uO7Y6T2Ps1YhM01AvGTtqjjQS0vOwc9B52X/BdZLxOgbnJto= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1704666132; 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=FpkeMumTTxI/qbz7eUPYNpfCaomSGQ1M50oUftDJD7Q=; b=DGGUx7ZSsWI+9ly5bbP56b16E5/p9HXzoiQKljyq/m2aW0DJ+7d9M/alDTHUtKDi8dLqgH PLCtIiKr/8vwbhqCASPIr6EuFKT+boGGnuEhf3TYEqueJhBbDiAmqtH4tMj94MldBMTuS5 Z5qf+B7Qyx6YGV9mqvTcWDGVJpJzzK8= 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-504-96Y0TuJROGeD7go6rKq2pw-1; Sun, 07 Jan 2024 17:22:08 -0500 X-MC-Unique: 96Y0TuJROGeD7go6rKq2pw-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (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 4863D185A780; Sun, 7 Jan 2024 22:22:08 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.39.192.92]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 0888DC159B0; Sun, 7 Jan 2024 22:22:07 +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 407MM5QM2750131 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Sun, 7 Jan 2024 23:22:05 +0100 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 407MM4gm2750130; Sun, 7 Jan 2024 23:22:04 +0100 Date: Sun, 7 Jan 2024 23:22:04 +0100 From: Jakub Jelinek To: Jeff Law Cc: waffl3x , "gcc@gcc.gnu.org" Subject: Re: Stage 4 date Message-ID: Reply-To: Jakub Jelinek References: <56f14678-20d5-4cff-85b5-7a12c13ef22f@gmail.com> MIME-Version: 1.0 In-Reply-To: <56f14678-20d5-4cff-85b5-7a12c13ef22f@gmail.com> X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.8 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=-4.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_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,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 Sun, Jan 07, 2024 at 03:12:32PM -0700, Jeff Law via Gcc wrote: > On 1/7/24 08:48, waffl3x via Gcc wrote: > > https://gcc.gnu.org/develop.html#timeline > > The date for stage 4 is listed as the 8th on here, is that date final? > > There is at least 1 patch pending (mine) that is complete but Jason > > Merril hasn't been active for a few days. He had expressed to me that > > he expected the date to be next week on the 14th. Is it possible to > > push back the date for stage 4 a little bit? I've been working hard on > > my patch and would be very disappointed if it did not make it in for > > GCC14. > Note there is generally allowances made for patches that were posted before > the deadline, but are still going through the review/iterate process. Also, not really sure why the stage 4 start is relevant to this patch, it is a new feature, not a bug fix, which admittedly had some versions posted already during stage 1, so if Jason accepts it soon I have no problem with it getting in (in fact I'd appreciate if it got in soon), but end of stage 3 is deadline for patches which are fixing bugs but not regression bugs. Jakub