public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/109179] [13 Regression] addkf3-sw.c:51:1: internal compiler error: RTL check: expected elt 3 type 'e' or 'u', have '0'
Date: Fri, 17 Mar 2023 21:27:24 +0000	[thread overview]
Message-ID: <bug-109179-4-nAwQxQanAR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109179-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Can't you move all the tests that don't need id or static_id (all but one)
before the
  lra_insn_recog_data_t id = lra_get_insn_recog_data (to);
  struct lra_static_insn_data *static_id = id->insn_static_data;
instead?
Ok, single_set is also a call, so maybe keep that one too?

I know, microoptimizations...

  parent reply	other threads:[~2023-03-17 21:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 19:38 [Bug target/109179] New: " bergner at gcc dot gnu.org
2023-03-17 19:39 ` [Bug target/109179] " bergner at gcc dot gnu.org
2023-03-17 19:43 ` bergner at gcc dot gnu.org
2023-03-17 20:05 ` bergner at gcc dot gnu.org
2023-03-17 20:12 ` bergner at gcc dot gnu.org
2023-03-17 20:14 ` bergner at gcc dot gnu.org
2023-03-17 20:18 ` [Bug rtl-optimization/109179] " bergner at gcc dot gnu.org
2023-03-17 20:29 ` vmakarov at gcc dot gnu.org
2023-03-17 20:29 ` [Bug rtl-optimization/109179] [13 Regression] " pinskia at gcc dot gnu.org
2023-03-17 20:38 ` jakub at gcc dot gnu.org
2023-03-17 20:46 ` bergner at gcc dot gnu.org
2023-03-17 20:48 ` vmakarov at gcc dot gnu.org
2023-03-17 20:50 ` bergner at gcc dot gnu.org
2023-03-17 20:51 ` jakub at gcc dot gnu.org
2023-03-17 21:04 ` bergner at gcc dot gnu.org
2023-03-17 21:09 ` bergner at gcc dot gnu.org
2023-03-17 21:13 ` vmakarov at gcc dot gnu.org
2023-03-17 21:23 ` bergner at gcc dot gnu.org
2023-03-17 21:27 ` jakub at gcc dot gnu.org [this message]
2023-03-17 21:34 ` bergner at gcc dot gnu.org
2023-03-17 21:54 ` bergner at gcc dot gnu.org
2023-03-17 22:03 ` bergner at gcc dot gnu.org
2023-03-17 22:06 ` jakub at gcc dot gnu.org
2023-03-17 22:13 ` vmakarov at gcc dot gnu.org
2023-03-18  0:03 ` cvs-commit at gcc dot gnu.org
2023-03-18  0:05 ` bergner 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-109179-4-nAwQxQanAR@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).