From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9ECAF385842A; Thu, 2 Feb 2023 19:45:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9ECAF385842A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675367159; bh=ndwrsY/+3mwKj24D0fsBhjmcDzQDa9DZtrPUaNwSRv0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=wFgReJZyHSdqAtpej+PykeHRxbhuq0GneXBh4DwvuWlLUZWQqOqQZQ1w1SmX7lwaa FIgd2WRf23T6LPZxek3IlyE1hPM1sUurnpiVIetQELPXr2yRGnH5rtG0yz6sLs+PT3 PN8EdUY8KZTzBODIfgCyoXxPhCO5YgIdr6pwKa+Q= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/108085] gcc trunk's ASAN at -O3 missed a stack-use-after-scope Date: Thu, 02 Feb 2023 19:45:59 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.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=3D108085 --- Comment #5 from Andrew Pinski --- The difference between the two front-ends is at the original. The C++ front-end adds a BLOCK around the loop while the C front-end does n= ot. This difference changes where the ASAN_MARK is placed with respect to the return statement.=