From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8943F3858C50; Sat, 21 Oct 2023 10:46:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8943F3858C50 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1697885189; bh=kPFHbGmxGr+iC3lHvU7MDAIkpzlu6YiggOOP+xlQL0A=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lyoPT6t+ym0bJ67Io8OLxmKtRoW7F+Px5373tAAAV6neOZGtfuKXVgWQ1DBMAiC20 F7KT8n4drONbUhSLeBF9iIgiwL1CMXwOgGxcwF+61mpLgbKeLXu+7L5x9hRTDB5Y3P agz2W168h+z1eTJK9moY+5FSZiYSrisQ602NWrDw= From: "egallager at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/80532] warning on pointer access after free Date: Sat, 21 Oct 2023 10:46:28 +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: 7.0 X-Bugzilla-Keywords: diagnostic, missed-optimization, patch X-Bugzilla-Severity: normal X-Bugzilla-Who: egallager at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.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=3D80532 --- Comment #11 from Eric Gallager --- (In reply to CVS Commits from comment #9) > The master branch has been updated by Martin Sebor : >=20 > https://gcc.gnu.org/g:671a283636de75f7ed638ee6b01ed2d44361b8b6 >=20 > commit r12-6605-g671a283636de75f7ed638ee6b01ed2d44361b8b6 > Author: Martin Sebor > Date: Sat Jan 15 16:37:54 2022 -0700 >=20 [...snip...] > libiberty/ChangeLog: >=20=20=20=20=20 > * regex.c: Suppress -Wuse-after-free. Was this part necessary? I'm wondering if it might be covering up an actual error that I'm seeing on CheriBSD on cfarm240...=