public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112337] arm: ICE in arm_effective_regno when compiling for MVE
Date: Wed, 08 Nov 2023 12:41:08 +0000	[thread overview]
Message-ID: <bug-112337-4-vdRnhQXLiU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112337-4@http.gcc.gnu.org/bugzilla/>

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

Vladimir Makarov <vmakarov at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vmakarov at gcc dot gnu.org

--- Comment #7 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Alex Coplan from comment #6)
> Confirmed. Here's a slightly cleaned up reproducer that doesn't warn:
> 
> #pragma GCC arm "arm_mve_types.h"
> int32x4_t h(void *p) { return __builtin_mve_vldrwq_sv4si(p); }
> void g(int32x4_t);
> void f(int, int, int, short, int *p) {
>   int *bias = p;
>   for (;;) {
>     int32x4_t d = h(bias);
>     bias += 4;
>     g(d);
>   }
> }
> 
> ICEs with -O2 -march=armv8.1-m.main+mve -mfloat-abi=hard on the trunk.

Looking at the dump, I can guess INC/DEC operand is not a reg after IRA
temporary transformation.  It can be fixed in arm.cc by checking that the
operand is reg instead of using the assert but it could be wrong because the
documentation says the operand should be a reg.  Also such solution would not
work for possible problem on other targets.

Could you provide me preprocessed test file. I'll try to find a solution as
soon as possible.

  parent reply	other threads:[~2023-11-08 12:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 15:49 [Bug target/112337] New: arm: ICE in arm_effective_regno stammark at gcc dot gnu.org
2023-11-02 10:02 ` [Bug target/112337] arm: ICE in arm_effective_regno when compiling for MVE rguenth at gcc dot gnu.org
2023-11-02 15:04 ` stammark at gcc dot gnu.org
2023-11-02 15:05 ` stammark at gcc dot gnu.org
2023-11-02 15:05 ` stammark at gcc dot gnu.org
2023-11-07 16:11 ` saurabh.jha at arm dot com
2023-11-07 16:49 ` pinskia at gcc dot gnu.org
2023-11-07 17:10 ` acoplan at gcc dot gnu.org
2023-11-08 12:41 ` vmakarov at gcc dot gnu.org [this message]
2023-11-08 12:50 ` acoplan at gcc dot gnu.org
2023-11-10 16:47 ` cvs-commit at gcc dot gnu.org
2023-11-14 14:41 ` saurabh.jha at arm dot com
2023-11-14 14:50 ` cvs-commit at gcc dot gnu.org
2024-01-18 13:21 ` adhemerval.zanella at linaro dot org
2024-01-18 18:01 ` clyon at gcc dot gnu.org
2024-01-19  9:12 ` saurabh.jha at arm dot com
2024-02-05  9:30 ` saurabh.jha at arm dot com
2024-03-05 15:27 ` rearnsha at gcc dot gnu.org
2024-03-05 15:29 ` cvs-commit at gcc dot gnu.org
2024-03-05 15:35 ` rearnsha 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-112337-4-vdRnhQXLiU@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).