From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS22989 209.51.188.0/24 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 70BF01F910 for ; Wed, 16 Nov 2022 18:42:03 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="pzBQ68md"; dkim-atps=neutral Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ovNM1-0005H9-Uf; Wed, 16 Nov 2022 13:41:45 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ovNLr-0005GA-Sd; Wed, 16 Nov 2022 13:41:38 -0500 Received: from mail-pg1-x533.google.com ([2607:f8b0:4864:20::533]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ovNLp-0006Sv-D4; Wed, 16 Nov 2022 13:41:35 -0500 Received: by mail-pg1-x533.google.com with SMTP id o13so17475643pgu.7; Wed, 16 Nov 2022 10:41:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=AAFZHLnlVqgesMa+b09QNzjWm+syNhmIMc0ExK9Hdq0=; b=pzBQ68mdL8BUU9CjeqH7bSMjrEAaRXHiJ7tha8Adl+ohNg2g3Q6y4U78lptLzcHXqg e4ueL5lAF+C8Uo6+ijr5DujCZoqbH72m66De0X9nCLRTaQSL5qw8n7qhu9jBc0IHVZeZ XjchaSpLt5MBEUg1eRNglPYjsJyVU07XDpasrTzZuUki5E6GGI1Sw/ngqzmd2MkrDXU9 L+DwayyQ+DSjh+wA9Mi7f8YePPLusXHDLPtAeyT2wyunD0W2EPCz6qyP+J4ys5VlZmrm nfV9VY+B3U6iUASpMwT7AlDN+tbO3QohI1U/WZJ9k9CvkoV77ceEHdZqd1ghBfHQxjXQ s8rA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=AAFZHLnlVqgesMa+b09QNzjWm+syNhmIMc0ExK9Hdq0=; b=NX4SvXVSZXg3sAAE4e9e05C50zcVfNlPu4bT76/bKOGN8RFmkhVtj4xaq5ZUGqiz/q 6EKcVFv6om0QMoStW/5qgZMXei3s1dwzaJcmAuglTsI0p4ZQTmn1+u+qQav7F4RvWUDC mACC1iq4WPRlvk/M9lkLQ1rWWdO8rjuhBRIhQbNkTi0ctnTiMR5BSsMsK3PHghj99JRH T1wONRDvJ+bEBpsMCVMSBlIdV4NwBs45lDTYmn6G4lKYhbbDqR4iFlUuVu4HzX86PWSU bgIWWTEAj3b3/jVAFAZ0Qa2xfTx9eFhDk7omPF1JXpCGhSwSXOaWSMnT3ZlgrF502L+w zdag== X-Gm-Message-State: ANoB5plz5sLPURTQiB5//Hk18RwXaNNyx6mqkFbX5EIAVO3zRAuZzHXj D3SJKrTtDTQ4KauwkC4pd7qp9MFTGtkQ+m0wIQ4= X-Google-Smtp-Source: AA0mqf5HQdkVOkWTgzPQru/+xiz7oXHasA6mzphRCNEr4P+30ubjjgz4lWQ/z0JjZ86XRnsLojmOg0cbWMoSQ7urYHc= X-Received: by 2002:a63:5164:0:b0:46f:ec9f:dcb0 with SMTP id r36-20020a635164000000b0046fec9fdcb0mr21619588pgl.202.1668624066164; Wed, 16 Nov 2022 10:41:06 -0800 (PST) MIME-Version: 1.0 References: <24ed5604-305a-4343-a1b6-a789e4723849@app.fastmail.com> <251923e7-57be-1611-be10-49c3067adf0d@cs.ucla.edu> <7ef0ce03-d908-649a-a6ee-89fea374d2b1@cs.ucla.edu> <9cb106e9-16ff-65ec-6a44-6567c77521dc@cs.ucla.edu> <06a5d2cd-44eb-7404-17f3-ff64dd505427@cs.ucla.edu> <4cfa16b3-e9e0-0ec0-659c-e4aef6090995@cs.ucla.edu> In-Reply-To: <4cfa16b3-e9e0-0ec0-659c-e4aef6090995@cs.ucla.edu> From: Jeffrey Walton Date: Wed, 16 Nov 2022 13:40:27 -0500 Message-ID: Subject: Re: How can Autoconf help with the transition to stricter compilation defaults? To: Paul Eggert Cc: c-std-porting@lists.linux.dev, autoconf@gnu.org, gcc@gcc.gnu.org, cfe-commits@lists.llvm.org, Gnulib bugs Content-Type: text/plain; charset="UTF-8" Received-SPF: pass client-ip=2607:f8b0:4864:20::533; envelope-from=noloader@gmail.com; helo=mail-pg1-x533.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: bug-gnulib@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gnulib discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: noloader@gmail.com Errors-To: bug-gnulib-bounces+normalperson=yhbt.net@gnu.org Sender: bug-gnulib-bounces+normalperson=yhbt.net@gnu.org On Wed, Nov 16, 2022 at 1:18 PM Paul Eggert wrote: > ... > If Clang's threatened pickiness were of some real use elsewhere, it > might be justifiable for default Clang to break Autoconf. But so far we > haven't seen real-world uses that would justify this pickiness for > Autoconf's use of 'char memset_explicit(void);'. This line of arguments is not persuasive. It is full of logical fallacies. Maybe the Autoconf folks should argue something along the lines of, "this is the _only_ way to do it because <...>." Jeff