From nobody Wed Jan 29 00:01:09 2025 X-Original-To: dev-commits-src-main@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YjMkr74SJz5mNSX for ; Wed, 29 Jan 2025 00:01:24 +0000 (UTC) (envelope-from jrtc27@jrtc27.com) Received: from mail-wm1-f47.google.com (mail-wm1-f47.google.com [209.85.128.47]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YjMkr3K7pz3X1h for ; Wed, 29 Jan 2025 00:01:24 +0000 (UTC) (envelope-from jrtc27@jrtc27.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-wm1-f47.google.com with SMTP id 5b1f17b1804b1-4364a37a1d7so63763265e9.3 for ; Tue, 28 Jan 2025 16:01:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738108882; x=1738713682; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Pgk2svU6KZmA/eyUkU0hmLhhxatWCThZx+rruoxxETk=; b=T/gmNTjKqJ1yx41KyywxYaFbHPPd+xZRC5jttWtQ2oIKVx3p+zFu3Dh4kSHl2AL8JF 7CnNC6sy7ClVzRBFcURKzGPOhgbTxebHhPV8trd1MsZT5zo2nRDSa5gLez6/RCHVdJ/b swXPt53D6RSsfroscuh3zKSdRJSOh9X+z9c0rzI4l7Q9myqpTm1EUP+5p4bSd2seIE+V sZBYCqP42nEqbsAYyN+RmySDhrugm5uCM7BSgNBSdQn910vxpLYvvhcXHLIO/eerlsxt 6HM6VTYTo4P/Hc4dmRVWkS/7QwysP7Vqvmh0acLhKAlx1tntFxNIKcmM+M/L/il7gdgP UJaA== X-Forwarded-Encrypted: i=1; AJvYcCVQ1vq0+LiIQkNHgwP5l0jQo/cd7ufgD4FPqLnLMdvMuvjF8h+JAHpeu4+GuJ5NdVOCS8hocjkPi6WbAhMQeMrkNHu94A==@freebsd.org X-Gm-Message-State: AOJu0YxPTMKAQgycvN9QEad00yolftHdKtf8hWlqcArut9giJ9nSEBrX 8q+axq0x5MU4/HGo5++oApORAtVhE1LtF7nbERnh656UF8ZWeTi86/JNcz665WTfdSEVArn1MWU O X-Gm-Gg: ASbGncu+QQRs73A59NZABTRgnqkNjPaWFN3Kr/cV+0J2VySfa8m6Y2f0Y8fyK4wdVjA ruunPkpgkRDvQzJGz+XCK+37kVs93ZsWM3+Fdb0IONbTUblk6smuxx3LmVBO7vgEJF+CfUB5aFZ i7rUgyIlPlLJ3T3um7t0yqDgk5XBtP28tA3AbUTDv+zQSnUj1cDbHEa9N9kZ2SRltMJuRqUKshD V4Ifu6V0mwKYo1mIRghpiQHNaXrzQo4V3D0gGGFfFxVrZSjdHox5lqBkhMaei5b3+vIWBVpua8t sItJ/cGZjEW2I69VlPO36DpRqQgAmQ== X-Google-Smtp-Source: AGHT+IGd3dnAKLdyOLMrH+iQy+Nu8JgHA8Q2V8iKPiOQRHPWr0EPpvYJ/sa4e4o5l+ofyZBdA6KdeQ== X-Received: by 2002:a5d:5988:0:b0:385:fd07:8616 with SMTP id ffacd0b85a97d-38c5167d80bmr760690f8f.0.1738108881692; Tue, 28 Jan 2025 16:01:21 -0800 (PST) Received: from smtpclient.apple ([131.111.5.201]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-38c2a188673sm15077691f8f.46.2025.01.28.16.01.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Jan 2025 16:01:20 -0800 (PST) Content-Type: text/plain; charset=utf-8 List-Id: Commit messages for the main branch of the src repository List-Archive: https://lists.freebsd.org/archives/dev-commits-src-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: dev-commits-src-main@freebsd.org Sender: owner-dev-commits-src-main@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.300.87.4.3\)) Subject: Re: git: c3450ad127e9 - main - clang: re-downgrade implicit int/function declarations to warning only From: Jessica Clarke In-Reply-To: <90D8C9F1-0634-44E5-B5B5-20455A91E042@FreeBSD.org> Date: Wed, 29 Jan 2025 00:01:09 +0000 Cc: "src-committers@freebsd.org" , "dev-commits-src-all@freebsd.org" , "dev-commits-src-main@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <277132FC-870F-48C7-A874-210789C71BD2@freebsd.org> References: <202306222111.35MLBAqB066211@gitrepo.freebsd.org> <90D8C9F1-0634-44E5-B5B5-20455A91E042@FreeBSD.org> To: Dimitry Andric X-Mailer: Apple Mail (2.3826.300.87.4.3) X-Rspamd-Queue-Id: 4YjMkr3K7pz3X1h X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] On 28 Jan 2025, at 23:20, Dimitry Andric wrote: > On 28 Jan 2025, at 19:32, Jessica Clarke wrote: >>=20 >> On 22 Jun 2023, at 22:11, Dimitry Andric wrote: >>=20 >>> The branch main has been updated by dim: >>>=20 >>> URL: = https://cgit.FreeBSD.org/src/commit/?id=3Dc3450ad127e94d3fa67ae337310e59c0= 02f51bfc >>>=20 >>> commit c3450ad127e94d3fa67ae337310e59c002f51bfc >>> Author: Dimitry Andric >>> AuthorDate: 2023-04-25 19:24:04 +0000 >>> Commit: Dimitry Andric >>> CommitDate: 2023-06-22 18:22:33 +0000 >>>=20 >>> clang: re-downgrade implicit int/function declarations to warning = only >>>=20 >>> This reapplies upstream commit c0141f3c300f by Aaron Ballman: >>>=20 >>> Downgrade implicit int and implicit function declaration to = warning only >>>=20 >>> The changes in Clang 15.0.0 which enabled these diagnostics as a >>> warning which defaulted to an error caused disruption for people >>> working on distributions such as Gentoo. There was an explicit = request >>> to downgrade these to be warning-only in Clang 15.0.1 with the >>> expectation that Clang 16 will default the diagnostics to an = error. >>>=20 >>> See >>> = https://discourse.llvm.org/t/configure-script-breakage-with-the-new-werror= -implicit-function-declaration/65213 >>> for more details on the discussion. >>>=20 >>> See https://reviews.llvm.org/D133800 for the public review of = these >>> changes. >>>=20 >>> As noted in the upstream discussion, there are many programs that = fail >>> to configure or build correctly, if these warnings are turned into >>> errors by default. >>>=20 >>> Note that most affected programs in ports are relatively old, and = are >>> unlikely to be fixed by actually adjusting their declarations, but = by >>> compiling with -std=3Dgnu89, which downgrades the errors back to = warning >>> again. Lots of tedious work for very little gain. >>=20 >> This remains as a downstream divergence 1.5 years later, but I do not >> think we should be carrying this indefinitely. Software needs to = build >> with upstream LLVM, and the fact that many ports do not is now biting >> us for CheriBSD where we use our own external toolchain that does not >> have such a diff. In my opinion this should be reverted for FreeBSD = 15 >> and it=E2=80=99s long time for ports people to step up or have the = broken ports >> removed; we can=E2=80=99t keep going on like this with abandonware = holding back >> forward progress. >=20 > While I agree, at the least a full exp-run should be done, and even = then > you can't be entirely sure if ports that build are built the same as > before, for example due to bad configure tests. So this is potentially = a > massive undertaking. I=E2=80=99m aware of the problem. Red Hat put in a lot of engineering = effort to find and fix such bugs. GCC 14.1 makes it an error by default for C99 too. Clang 16 kept it as an error. FreeBSD is now an outlier in turning this off, and non-obscure ports really should already be fixed if they=E2=80=99re being kept up-to-date. I appreciate that there will be = fallout, but we can=E2=80=99t just do nothing because nobody in ports has stepped = up in the past 1.5 years to act on this. We need to commit to this happening and then ports will have to deal with it. Otherwise another year will go by and we=E2=80=99ll still be doing this. Jess