From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 99A283858D37; Thu,  6 Oct 2022 19:32:15 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 99A283858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1665084735;
	bh=iT2ZRkIz5/zptKPqCdbHj8dXipgi/MC/4qF75suxIVo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=f7YvY+OupVIROtOj+ywtTDdRcTGcdrPKYTkuLsEL1CsUFAsKvgMnB7XTduDX6xKiL
	 JRwHtmXD6NmCLWpeELZI+fUe4rW7CqHoEqnJkK9LFZFbD6nEqC8+w/6bwqdRQDjDfZ
	 0Lb1XVziAdABDx89ae1QJBkKiEyL1bPKv3q3Ixqw=
From: "erozen at microsoft dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/107169] [13 Regression] -fcompare-debug failure at -O and
 above since r13-2921-gf1adf45b17f7f1ed
Date: Thu, 06 Oct 2022 19:32:15 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: compare-debug-failure
X-Bugzilla-Severity: normal
X-Bugzilla-Who: erozen at microsoft dot com
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: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107169-4-gWHTqkKzvr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107169-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107169-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107169

--- Comment #2 from Eugene Rozenfeld <erozen at microsoft dot com> ---
When -gstatement-frontiers is on, the IR coming from the front end may be
different with and without debug information turned on. That may cause e.g.,
different discriminator values and -fcompare-debug failures.

See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100733.

In  https://gcc.gnu.org/git/gitweb.cgi?p=3Dgcc.git;h=3Df1adf45b17f7f1ed I a=
dded
-gno-statement-frontiers to gcc/testsuite/c-c++-common/ubsan/pr85213.c
b/gcc/testsuite/c-c++-common/ubsan/pr85213.c to work around this problem for
that test.=