From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 845F03858C98; Thu, 29 Feb 2024 16:08:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 845F03858C98 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1709222899; bh=hmL5FCbcn1djNKnJnnIJ9zBE+b1GDAx2FNWJuz7bsBg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=IIbFX7kkN/Daqn3nw+zOJ4HLbHunbMqEdJ5ltjDbBxZiJ6HklEIFmW4rb2Juc6oI+ 9Gv2Xx49wN3MPYlLldmXDIJu0b8064lVZUIeBHkQHIauPeQoRFaJHIymMaNz7Re/z0 Vct6iF5iPZOvnb+rj95k16L91Fllc6/WTGa5YVyc= From: "dmalcolm at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/110483] [14 Regression] Several gcc.dg/analyzer/out-of-bounds-diagram-*.c tests FAIL Date: Thu, 29 Feb 2024 16:08:18 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: analyzer X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: dmalcolm at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 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=3D110483 --- Comment #6 from David Malcolm --- Thanks; let's keep using this PR for the stuff in comment #5. I've been looking at these on gcc211 in the compile farm: * I see out-of-bounds-diagram-11.c failing as you describe (the overflow = in test6 isn't reported with g++ for some reason; it is for gcc) * out-of-bounds-diagram-3.c gets skipped on that machine due to=20 { dg-require-effective-target lp64 } "check_cached_effective_target lp64: returning 0 for unix" Is there a config/cfarm machine you see the out-of-bounds-diagram-3.c failu= re on?=