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 target/104474] [12 Regression] ICE: in output_constant_pool_2, at varasm.cc:4062 with -mcpu=neoverse-512tvb  -msve-vector-bits=512
Date: Wed, 09 Feb 2022 19:45:29 +0000	[thread overview]
Message-ID: <bug-104474-4-Rb1KvtpOBF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104474-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
            Summary|[12 Regression] ICE: in     |[12 Regression] ICE: in
                   |output_constant_pool_2, at  |output_constant_pool_2, at
                   |varasm.cc:4062 with         |varasm.cc:4062 with
                   |-mcpu=neoverse-512tvb       |-mcpu=neoverse-512tvb
                   |-frounding-math             |-msve-vector-bits=512
                   |-msve-vector-bits=512       |
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2022-02-09

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed, the problem is the backend replaces the non-constant parts with
(const_int 0) rather than zero in the mode.
You can also reproduce the failure with just -mcpu=neoverse-512tvb
-msve-vector-bits=512 and:
typedef float __attribute__((__vector_size__ (64))) F;

F
foo (float t)
{
  return (F){t, 0, 0, 0, 0, 0, 0, 5, 0, t};
}

  parent reply	other threads:[~2022-02-09 19:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 19:27 [Bug target/104474] New: [12 Regression] ICE: in output_constant_pool_2, at varasm.cc:4062 with -mcpu=neoverse-512tvb -frounding-math -msve-vector-bits=512 zsojka at seznam dot cz
2022-02-09 19:32 ` [Bug target/104474] " pinskia at gcc dot gnu.org
2022-02-09 19:45 ` pinskia at gcc dot gnu.org [this message]
2022-02-09 19:54 ` [Bug target/104474] [12 Regression] ICE: in output_constant_pool_2, at varasm.cc:4062 with -mcpu=neoverse-512tvb -msve-vector-bits=512 pinskia at gcc dot gnu.org
2022-02-09 20:00 ` pinskia at gcc dot gnu.org
2022-02-10  0:49 ` cvs-commit at gcc dot gnu.org
2022-02-10  0:53 ` pinskia at gcc dot gnu.org
2022-02-10  9:08 ` [Bug target/104474] [10/11 " pinskia at gcc dot gnu.org
2022-04-07  9:53 ` cvs-commit at gcc dot gnu.org
2022-06-28 10:48 ` [Bug target/104474] [10 " jakub at gcc dot gnu.org
2023-07-07  9:56 ` rguenth 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-104474-4-Rb1KvtpOBF@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).