From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) by sourceware.org (Postfix) with ESMTPS id AB4E53896C21 for ; Mon, 14 Nov 2022 18:35:22 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org AB4E53896C21 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=aaronballman.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=aaronballman.com Received: by mail-qt1-x82c.google.com with SMTP id l15so7320943qtv.4 for ; Mon, 14 Nov 2022 10:35:22 -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=EeksPAbnKuDJlw1e78LlJ5feKFqnN1n2dyO5euZVXs3MFGegegP801zs7jaH/LNHPy N6CNHzXJyfboVRFq7AM6uK+9zkZvs5lPbJXxUdW4XPMjzr27ure6yLo0TROmaUxRyb1a YPktilr/WVVpyzd71ajQRnOvL89DbW6I/tpMbV3t8nTwXn8em/j0YamPNMacOpkv2TCo rw9euGwLTU3nwluZK05bKedYB3NEWYbvR6jmxhJ2tu88Kmyll/y1kQrSZHuVNQGLzLBE VbcRMju34GHKsA4sua6/89NPZGFcEQSBe/vzOWSFnis40IpXRcdN6I0VVk2FFoU/BT6S 9wNQ== X-Gm-Message-State: ANoB5plewDEk3QInjAEhwXg/KwBGgTC865Q8Xav/xPV7g00J7yV6z7gY ITQx+jfUb8jld2lhfbHr0x+HYF+5KMO2Wh/4 X-Google-Smtp-Source: AA0mqf7FjXptQtVbP6GO2IIo36fjrvTmhAgWYxKFW2b2KbZSzUxqz9k+rcCcyAxoafuSVa2wMZuYrA== X-Received: by 2002:ac8:48cc:0:b0:3a5:1bd9:fc1 with SMTP id l12-20020ac848cc000000b003a51bd90fc1mr13481332qtr.315.1668450921161; Mon, 14 Nov 2022 10:35:21 -0800 (PST) Received: from mail-yw1-f180.google.com (mail-yw1-f180.google.com. [209.85.128.180]) by smtp.gmail.com with ESMTPSA id g10-20020a05620a40ca00b006faf76e7c9asm7001396qko.115.2022.11.14.10.35.20 for (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-f180.google.com with SMTP id 00721157ae682-369426664f9so114951837b3.12 for ; 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" X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,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 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