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,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,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 6D23D1F910 for ; Tue, 15 Nov 2022 00:09:41 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=aaronballman.com header.i=@aaronballman.com header.b="XPgNPmUx"; dkim-atps=neutral Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ouiit-0002Ul-FL; Mon, 14 Nov 2022 18:18:39 -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 1ouieU-0001yn-Bv for bug-gnulib@gnu.org; Mon, 14 Nov 2022 18:14:06 -0500 Received: from mail-qk1-x72f.google.com ([2607:f8b0:4864:20::72f]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oueIm-00065w-7H for bug-gnulib@gnu.org; Mon, 14 Nov 2022 13:35:26 -0500 Received: by mail-qk1-x72f.google.com with SMTP id 8so8009532qka.1 for ; Mon, 14 Nov 2022 10:35:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aaronballman.com; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Voy3B0RGB1s+lkXDZ/t1tDGskLd8YPh62hI4yS08Apk=; b=XPgNPmUx9ORjerJkzqcO/6i8C7wxAJwFiiELw1R8lKmi5ga3cgzDKeU1UEKJs7WDza 7SyebN8+IRbYEWh3LQcy7lcoyBoB1RxaK9FNwQoDhJpg/udYjcSW6p4hxVuLHjgaTXwD sKyNYfX9cirriOgwES+4FT0+Dhe1ppiHMTsqzCSa0n7v6Z3jXs2B0d8Cid34BhpPsGP8 wlb498bHB42PJe1LiEdBLJhISKnG6slDi+9rPsk/qY3sGXTDv+zyri9JVwf+8l79s903 tW+MBETXidr6jtrv5BMSydTEj/fWImdj9ug3Y7oztaAR0xGogIjTr4+s1mx1EAle82Vd +YSA== 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:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Voy3B0RGB1s+lkXDZ/t1tDGskLd8YPh62hI4yS08Apk=; b=okT/qKmCG3KBDpXPM/ItQOFr9TgLSCrRUfF8pd967izeoACbIUTO6913URzTcP/ucu x/kmwcQuswwBylWB+WgcO2+6Xrm2dnuNaKluR3YtJjfMdy+XoGLgNVGzKxUVsXjbNnM0 yYgVz9rjn25u8YRX+K8NAvseFJxiR9eYY5/iJCAYyyQBaFT3QwVwgQ0u/+72owNfsncj 7HGYAP7OmxL0JhZobarXeUn49Ls85Hjw1gLUlCmzqEYIRl64db+t5JjqFARYUNIXN4Ru FdymnKRGzLnVcJC0RwPsaEBsiTI5a+5rF3FXe1zoKQwLx+NZZ6glnYJSpWKw7bLHhkFV 7d0g== X-Gm-Message-State: ANoB5pmWfAU+ZZcOn2FdWJY3bQnBMSsNvoKvyHBVLzkaG28czCzawc86 Rz/tvojT1HxVApP3z+FAFgJIIg== X-Google-Smtp-Source: AA0mqf6P1vn0vNmWKT8ayvzOtsaew06F8qdYEOJ6q9k2f3/EL1qx2mhVfUcuu2cFZPeoq8A5GKOtbg== X-Received: by 2002:a37:b2c6:0:b0:6fa:39f6:8c13 with SMTP id b189-20020a37b2c6000000b006fa39f68c13mr12468953qkf.113.1668450922769; Mon, 14 Nov 2022 10:35:22 -0800 (PST) Received: from mail-yw1-f179.google.com (mail-yw1-f179.google.com. [209.85.128.179]) by smtp.gmail.com with ESMTPSA id y22-20020a37f616000000b006cf19068261sm6706005qkj.116.2022.11.14.10.35.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 14 Nov 2022 10:35:20 -0800 (PST) Received: by mail-yw1-f179.google.com with SMTP id 00721157ae682-382f0906929so23642967b3.10; Mon, 14 Nov 2022 10:35:20 -0800 (PST) X-Received: by 2002:a81:5547:0:b0:357:de11:394a with SMTP id j68-20020a815547000000b00357de11394amr14110710ywb.113.1668450919886; Mon, 14 Nov 2022 10:35:19 -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> In-Reply-To: From: Aaron Ballman Date: Mon, 14 Nov 2022 13:35:08 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: How can Autoconf help with the transition to stricter compilation defaults? To: Paul Eggert Cc: Zack Weinberg , 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::72f; envelope-from=aaron@aaronballman.com; helo=mail-qk1-x72f.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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham 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: , Errors-To: bug-gnulib-bounces+normalperson=yhbt.net@gnu.org Sender: bug-gnulib-bounces+normalperson=yhbt.net@gnu.org On Mon, Nov 14, 2022 at 1:14 PM Paul Eggert wrote: > > On 2022-11-14 04:41, Aaron Ballman wrote: > > it's generally a problem when autoconf relies on invalid > > language constructs > > Autoconf *must* rely on invalid language constructs, if only to test > whether the language constructs work. And Clang therefore must be > careful about how it diagnoses invalid constructs. Clang shouldn't > willy-nilly change the way it reports invalid constructs, as that can > break Autoconf. > > > issues of security > > like statically known instances of UB > > It's fine to report those; I'm not saying don't report them. All I'm > saying is that Clang should be careful about *how* it reports them. > > At the very least if there are going to be changes in this area, the > Clang developers should notify Autoconf (and presumably other) > downstream users of the changes, and provide a supported way to get the > old behavior for reporting, and give downstream time to adapt. Definitely agreed about the communication aspects! I mentioned this upthread: FWIW, we're working on improving communication about potentially disruptive changes to Clang, so you might want to consider either subscribing to the clang-vendors code review group at https://reviews.llvm.org/project/members/113/ (if you want to be involved in code review before things land) or the Announcements discourse channel at https://discourse.llvm.org/c/announce/ (if you want to be notified after something lands but before Clang ships). One other thing we've done recently is starting to call out potentially disruptive changes in the release notes as well: https://clang.llvm.org/docs/ReleaseNotes.html#potentially-breaking-changes -- but this is more for notifying folks after a release goes out, so one of the other approaches is more proactive if the goal is to alert Clang developers to serious deployment problems before we ship. ~Aaron