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 ABF2F3858402; Wed, 22 Nov 2023 23:05:22 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ABF2F3858402
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1700694322;
	bh=AtI7IYoXl1E2ePoXLJUoo8Iq5HVkDYfD4vF+/5wd/sM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=hGmaZ6RojZ4wBUXFajfvA6FcTwbtGnKFgAq+9onRyy854c20kbKFhvqG8B7hW/Vs3
	 zocKwLqbj1da6MNyLY3Dix35YonoQhweLV16myUjr5ipmzt2nb5GjVFKZhjWr6ticX
	 2VwJdVtHIGzijAOswr3dih6rJIhh2SXTFjnm0x5c=
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/112674] [14 Regression] Compare-debug failure after
 recent change on c6x
Date: Wed, 22 Nov 2023 23:05:22 +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: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: <bug-112674-4-lDfLwQOUiW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-112674-4@http.gcc.gnu.org/bugzilla/>
References: <bug-112674-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=3D112674

--- Comment #1 from Jeffrey A. Law <law at gcc dot gnu.org> ---
And possibly more interesting than the compare-debug failure is this patch
seems to be causing Wstringop-overflow-17 to fail on multiple targets,
including c6x.=