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 29EAB3858D32; Mon, 13 Mar 2023 23:48:58 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 29EAB3858D32
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1678751338;
	bh=iUAmxrO4I9R8azsH7gWFSf1473XXB3/1XoR9QuzTI1g=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=gRlGNvrTZFsgimMef5uccE3FT7PMtSNFwWuQCPavk281fvsBRf6LNU6gQ8oKji2Lu
	 XO57k2dUG5KV7UccpESwU84d49WZ1vASzaNvMUo779f7kKra1PGYApYPQ5k7SnkZGg
	 lwMaRk25sPivrJ5NksRSlLQF06ULjiO9x6X1UC/g=
From: "chip.kerchner at ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109116] vector_pair register allocation bug
Date: Mon, 13 Mar 2023 23:48:57 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: chip.kerchner at ibm dot com
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-109116-4-mq57nuRjcM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109116-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109116-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=3D109116

--- Comment #2 from Chip Kerchner <chip.kerchner at ibm dot com> ---
This could be a bigger issue with register allocation after the disassemble=
 of
an opaque object like vector_pair or MMA.=