From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E57863858CDB; Thu, 4 May 2023 13:30:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E57863858CDB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683207027; bh=dWIejntRy3s5aY+cCWmGE1unXOFxKKSIMj3mzYggvDo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KazbSnwpt824NY8KwWZG05VI27Uyi3cDcsOg/QFPReHDCQuuWJQQ3HNytrXyblH1I jI2tLhrfrdAWLBXOWJz+vc/q9wwkOZW5/KxEb065nyK8DPa3cxaCIhVTs43/iQbFne i0/200CxMZZ0pbPhw8abXfw5Lm1AX+eqkJdnhMkA= From: "psmith at gnu dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109717] -Warray-bound error with gnu++20 and fmt library Date: Thu, 04 May 2023 13:30:27 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 13.1.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: psmith at gnu dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109717 --- Comment #9 from Paul Smith --- > Now they're issued even when the "problem" is in a system header. Oh interesting: I have been in the habit of including all my 3rdparty libra= ry headers using -isystem to avoid worrying about warnings/errors in them. Regarding this issue I understand the rock versus hard place situation. If there's an assert or something that can help, I can suggest it to the fmt folks; they have been receptive to adding compiler-specific tricks in the p= ast. If I can find the time I'll try to test this by editing my copy. I still = find it strange that I can't reproduce this failure using the GDB 13.1 / fmt 9.1= .0 libraries available on godbolt: it works fine there. It would be great if this warning could be split into "this is a definite problem" versus "this might be a problem", as some others have been, but I understand that could be complex and a lot of work.=