public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: "Takayuki 'January June' Suwa" <jjsuwa_sys3175@yahoo.co.jp>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 2/4] xtensa: Consider the Loop Option when setmemsi is expanded to small loop
Date: Fri, 10 Jun 2022 17:12:42 -0700	[thread overview]
Message-ID: <CAMo8BfKxv7oM2cFJ6tz7_Re_fPqndbWMnA6UO6FSBUJ5_JNmDQ@mail.gmail.com> (raw)
In-Reply-To: <842bf876-2f00-7216-b6f4-e625a13868dc@yahoo.co.jp>

Hi Suwa-san,

On Thu, Jun 9, 2022 at 9:26 PM Takayuki 'January June' Suwa
<jjsuwa_sys3175@yahoo.co.jp> wrote:
>
> Now apply to almost any size of aligned block under such circumstances.
>
> gcc/ChangeLog:
>
>         * config/xtensa/xtensa.cc (xtensa_expand_block_set_small_loop):
>         Pass through the block length / loop count conditions if
>         zero-overhead looping is configured and active,
> ---
>   gcc/config/xtensa/xtensa.cc | 65 +++++++++++++++++++++++++------------
>   1 file changed, 45 insertions(+), 20 deletions(-)

This change results in a bunch of ICEs in tests that look like this:

gcc/gcc/testsuite/gcc.c-torture/compile/memtst.c: In function 'main':
gcc/gcc/testsuite/gcc.c-torture/compile/memtst.c:28:1: error:
unrecognizable insn:
(insn 7 6 8 2 (set (reg:SI 45)
       (plus:SI (reg:SI 44)
           (const_int 262144 [0x40000])))
"gcc/gcc/testsuite/gcc.c-torture/compile/memtst.c":23:3 -1
    (nil))
during RTL pass: vregs
gcc/gcc/testsuite/gcc.c-torture/compile/memtst.c:28:1: internal
compiler error: in extract_insn, at recog.cc:2791
0x6a21cf _fatal_insn(char const*, rtx_def const*, char const*, int, char const*)
       gcc/gcc/rtl-error.cc:108
0x6a2252 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
       gcc/gcc/rtl-error.cc:116
0x693824 extract_insn(rtx_insn*)
       gcc/gcc/recog.cc:2791
0xb27647 instantiate_virtual_regs_in_insn
       gcc/gcc/function.cc:1611
0xb27647 instantiate_virtual_regs
       gcc/gcc/function.cc:1985
0xb27647 execute
       gcc/gcc/function.cc:2034

-- 
Thanks.
-- Max

  reply	other threads:[~2022-06-11  0:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10  4:18 Takayuki 'January June' Suwa
2022-06-11  0:12 ` Max Filippov [this message]
2022-06-11  3:31   ` Takayuki 'January June' Suwa

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=CAMo8BfKxv7oM2cFJ6tz7_Re_fPqndbWMnA6UO6FSBUJ5_JNmDQ@mail.gmail.com \
    --to=jcmvbkbc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jjsuwa_sys3175@yahoo.co.jp \
    /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).