public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/109840] [14 Regression] internal compiler error: in expand_fn_using_insn, at internal-fn.cc:153 when building graphite2
Date: Sat, 13 May 2023 06:53:44 +0000	[thread overview]
Message-ID: <bug-109840-4-gR3Mo1WYTu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109840-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2023-05-13
   Target Milestone|---                         |14.0
            Summary|internal compiler error: in |[14 Regression] internal
                   |expand_fn_using_insn, at    |compiler error: in
                   |internal-fn.cc:153 when     |expand_fn_using_insn, at
                   |building graphite2          |internal-fn.cc:153 when
                   |                            |building graphite2
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
                 CC|                            |pinskia at gcc dot gnu.org,
                   |                            |roger at nextmovesoftware dot com

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(gdb) p debug_gimple_stmt(stmt)
_5 = .POPCOUNT (load_dst_15);


  short unsigned int load_dst_15;

  <bb 2> [local count: 1073741824]:
  load_dst_15 = MEM <short unsigned int> [(unsigned char *)&Loaderthrow_p];
  _5 = .POPCOUNT (load_dst_15);

In forwprop4:
gimple_simplified to _5 = .POPCOUNT (load_dst_15);


Before:
  load_dst_15 = MEM <short unsigned int> [(unsigned char *)&Loaderthrow_p];
  bswapdst_16 = load_dst_15 r>> 8;
  r_14 = (unsigned int) bswapdst_16;
  _5 = .POPCOUNT (r_14);


aarch64 has a popcountsi2 pattern but does not have a popcounthi2 pattern.

Using the internal function here is definitely an issue without checking which
patterns the backend has.

Confirmed.

  parent reply	other threads:[~2023-05-13  6:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-13  6:34 [Bug middle-end/109840] New: " sjames at gcc dot gnu.org
2023-05-13  6:35 ` [Bug middle-end/109840] " sjames at gcc dot gnu.org
2023-05-13  6:53 ` pinskia at gcc dot gnu.org [this message]
2023-05-13  7:01 ` [Bug middle-end/109840] [14 Regression] " pinskia at gcc dot gnu.org
2023-05-14 18:08 ` roger at nextmovesoftware dot com
2023-05-24 16:36 ` cvs-commit at gcc dot gnu.org
2023-05-26 13:20 ` roger at nextmovesoftware dot com

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-109840-4-gR3Mo1WYTu@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).