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 bootstrap/110324] [14 Regression][bootstrap, nvptx] build/genpreds: Internal error: RTL check: expected elt 2 type 'T', have 's' due to r14-1949-g957ae904065917
Date: Tue, 20 Jun 2023 17:15:51 +0000	[thread overview]
Message-ID: <bug-110324-4-eRWPjnjTbR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110324-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(gdb) p ((enum rtx_code) (x)->code)
$3 = DEFINE_COND_EXEC
(gdb) p (int)((enum rtx_code) (x)->code)
$4 = 172

and hence:

(gdb) p rtx_format[172]
$6 = 0x4bcda0 "EssV"


where we take the index 2 => 's'.

The EssV matches the rtl.def entry:

   DEF_RTL_EXPR(DEFINE_COND_EXEC, "define_cond_exec", "EssV", RTX_EXTRA)

Actually, grepping for 'T' I only find:

 "define_insn", "sEsTV"
 "define_peephole", "EsTV"
 "define_insn_and_split", "sEsTsESV"
 "define_insn_and_rewrite", "sEsTsSV"

  parent reply	other threads:[~2023-06-20 17:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20 16:20 [Bug bootstrap/110324] New: " burnus at gcc dot gnu.org
2023-06-20 16:52 ` [Bug bootstrap/110324] " burnus at gcc dot gnu.org
2023-06-20 17:03 ` burnus at gcc dot gnu.org
2023-06-20 17:15 ` burnus at gcc dot gnu.org [this message]
2023-06-20 17:20 ` [Bug bootstrap/110324] [14 Regression][build][nvptx] " burnus at gcc dot gnu.org
2023-06-20 17:22 ` burnus at gcc dot gnu.org
2023-06-20 22:31 ` cvs-commit at gcc dot gnu.org
2023-06-20 22:34 ` tnfchris 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-110324-4-eRWPjnjTbR@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).