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 E9B633858D28; Tue, 20 Jun 2023 21:48:00 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E9B633858D28
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1687297680;
	bh=YPKpnIHw7e1uhQJv9t2zan5n1RGTEqgjn+0ThtZk/Tk=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Q6HEP80/D4m1McFTvbV4UBGFT+hLQoWdYIUuvfQInJxGn9zklebkFcX7j9ADHBOVD
	 apnxwQViOiRVwaJl4yXhf+EOjUluYp5Tx7TNYXaLga5Z6anVL1eC+E53nBFAz4Jk7y
	 2LIBgyrt8C0zPcmK/bqyi+0HmPbflLpQYnQnT93c=
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110313] [14 Regression] GCN Fiji reload ICE in
 'process_alt_operands'
Date: Tue, 20 Jun 2023 21:48:00 +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: 14.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus 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: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110313-4-syUa1VYWqv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110313-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110313-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=3D110313

--- Comment #7 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Correction with regards to reg_info_size:

I claimed that reg_info_size =3D 3659 > 3483 =E2=80=93 but that's not quite=
 true.

That's the result when doing 'p reg_info_size' in lra-constraints.cc.
When going 'up' in the debugger to lra.cc, the value is there:

  reg_info_size =3D=3D 2723

It is not completely clear which 'reg_info_size' gdb picks up in
lra-constraints.cc as there are:

lra.cc:static int reg_info_size;
reginfo.cc:static int reg_info_size;

and none in lra-constraints.cc.

* * *

In any case, the lra.c's reg_info_size is increased via
* lra.c's init_reg_info + expand_reg_info;
  the latter is also called via expand_reg_data
  and add_regs_to_insn_regno_info. And indirectly via lra_emit_move,
  lra_create_new_reg_with_unique_value and lra_emit_add.

  The last 3 are non-static and also called in lra-constraints.cc

* reginfo.cc's allocate_reg_info is set in allocate_reg_info,
  reginfo_init and resize_reg_info - and the last one is non-static
  and called via:
  lra_get_regno_hard_regno and lra_get_allocno_class=20
  and togather with the lra.c's one in via the lra_emit_* and
  lra_create_*

It seems as if some of the lra-constraints.cc calls that call
lra_get_allocno_class or lra_get_regno_hard_regno - also need to
call something which increases the size of lra.c's reg_info_size
and the associated lra_reg_info array.=