From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by sourceware.org (Postfix) with ESMTPS id 8C13F3858C60 for ; Fri, 11 Nov 2022 03:34:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8C13F3858C60 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=owlfolio.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=owlfolio.org Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D814C5C0227; Thu, 10 Nov 2022 22:34:44 -0500 (EST) Received: from imap45 ([10.202.2.95]) by compute1.internal (MEProxy); Thu, 10 Nov 2022 22:34:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=owlfolio.org; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1668137684; x=1668224084; bh=JDDIuamH/v cE1M5PVLLzpTRuc7Xb0Om/kA+a9rZKDxk=; b=JO1OR5giithoSSk41QFXhh+iSG 5rUtEfCn+XG3QItKDDUJmrXVCjmVH4ZRnKQjAiT/AbuntXxANC8NnHyv350KZ1UQ fgXRJjpr2RuSg2aFyKcC9c0EQKx35EOg00PWYeBUrRdjOQ3B9aQrk+BA5A7ldXd4 LHLFetUAMDSykJx2J+ooYShHbjnSLYxuVRN+VGVYuhtFPFH/fGIS9t4hKa/OQOoW ldGfwMt7mM97KYuKQaVmNLZdwzTqGy9Uwb71l40xcBCnCNZU8M9n/hnMe10Tg1uN bE6lQUBd2UyliWbTvhWay5XLgHfwrkinELc0N/ZYaR3UDAIxuethM9uXNOAA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1668137684; x=1668224084; bh=JDDIuamH/vcE1M5PVLLzpTRuc7Xb 0Om/kA+a9rZKDxk=; b=E16kFhXFoAQEhmTJXVwgdoCEIpY5L4fP1uGk2Hearc7R vVrVKg1lDEBEvQd3sfGJQU8Yr6h/Yma8UFKdSjbsUqL/dRyYWGJltgxnsNIW0+8V kGx/NHR1vPJsMZL+T96imlAFP9o3E5b1jeGapBOyYXblb4PDKrugSv7Kc8eF/mr5 Dz9igP2UkyMDILLNpAb+mUUOAL8umK+fZpAnFxqiJe3DyQf7+ZMhcuLU2+ht/av4 2jHvCdjCwO/ArAY/Z/6XVcGJ6zJcjlDb0zUsZFQoA1oiZKPGc4WbZ18A58iubFJD MavBIRLQECDTe3v03tdJR3xSDLuQ+TB+uGKndWYNYg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrfeehgdeivdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvvefutgesthdtredtreertdenucfhrhhomhepfdgkrggt khcuhggvihhnsggvrhhgfdcuoeiirggtkhesohiflhhfohhlihhordhorhhgqeenucggtf frrghtthgvrhhnpeegvefhheehteeljeduueeufeegffeftdetleeggeehueekffekffdu udetffffudenucffohhmrghinhepghhnuhdrohhrghenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpeiirggtkhesohiflhhfohhlihhordhorhhg X-ME-Proxy: Feedback-ID: i876146a2:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9AD59272007A; Thu, 10 Nov 2022 22:34:44 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-1115-g8b801eadce-fm-20221102.001-g8b801ead Mime-Version: 1.0 Message-Id: <1d3109aa-c810-4c20-bcb9-d9d059d530a6@app.fastmail.com> In-Reply-To: References: <24ed5604-305a-4343-a1b6-a789e4723849@app.fastmail.com> Date: Thu, 10 Nov 2022 22:33:08 -0500 From: "Zack Weinberg" To: "Sam James" , "Michael Orlitzky" Cc: "Autoconf Development" , c-std-porting@lists.linux.dev, "GCC Development" Subject: Re: How can Autoconf help with the transition to stricter compilation defaults? Content-Type: text/plain X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,JMQ_SPF_NEUTRAL,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS,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, Nov 10, 2022, at 10:08 PM, Sam James wrote: >> On 10 Nov 2022, at 21:10, Michael Orlitzky wrote: >> While everyone else is discussing big ideas, it would be helpful for me >> personally if autoconf just made a release with the latest bugfixes. > > Before I dive into the rest of this thread: yes, this is one of > my main thoughts on the matter. Autoconf has a huge network > effect problem and letting the existing fixes start to propagate > would be most helpful. It would be relatively easy for me to take a couple hours this weekend and put out a 2.72 release with everything that's already in trunk and nothing else. Anyone have reasons I _shouldn't_ do that? > Note that in autoconf git, we've also got > https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=f6657256a37da44c987c04bf9cd75575dfca3b60 > which is going to affect time_t efforts too I have not been following the y2038 work closely. Is it going to affect things in a good way or a bad way?? zw