public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-110313-4-syUa1VYWqv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110313-4@http.gcc.gnu.org/bugzilla/>

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

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

I claimed that reg_info_size = 3659 > 3483 – 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 == 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 
  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.

  parent reply	other threads:[~2023-06-20 21:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 15:59 [Bug target/110313] New: " tschwinge at gcc dot gnu.org
2023-06-20  8:11 ` [Bug target/110313] " rguenth at gcc dot gnu.org
2023-06-20  9:13 ` ams at gcc dot gnu.org
2023-06-20  9:21 ` tschwinge at gcc dot gnu.org
2023-06-20  9:41 ` ams at gcc dot gnu.org
2023-06-20 15:36 ` tschwinge at gcc dot gnu.org
2023-06-20 15:56 ` ams at gcc dot gnu.org
2023-06-20 20:57 ` burnus at gcc dot gnu.org
2023-06-20 21:48 ` burnus at gcc dot gnu.org [this message]
2023-06-20 22:55 ` burnus at gcc dot gnu.org
2023-06-21  6:49 ` manolis.tsamis at vrull dot eu
2023-06-21  7:25 ` tschwinge at gcc dot gnu.org
2023-06-21  8:45 ` burnus at gcc dot gnu.org
2023-06-28 14:06 ` cvs-commit at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-110313-4-syUa1VYWqv@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).