public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stammark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/96974] [10/11 Regression] ICE in vect_get_vector_types_for_stmt compiling for SVE
Date: Thu, 15 Oct 2020 15:36:25 +0000 [thread overview]
Message-ID: <bug-96974-4-npzZ5StjMk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96974-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96974
Stam Markianos-Wright <stammark at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Host| |x86_64-linux-gnu
CC| |stammark at gcc dot gnu.org
Last reconfirmed| |2020-10-15
--- Comment #1 from Stam Markianos-Wright <stammark at gcc dot gnu.org> ---
Also confirmed on today's trunk aarch64-none-elf
Seems to relate to use of that specific type of builtin or type of builtins (I
tested some other math builtins and they were ok, but e.g. __builtin_llrintf
produced the same ICE), and only inside the `d ? b() : 0` condition (i.e.
changing that `coeffs[e] = b()` makes the ICE go away)
next prev parent reply other threads:[~2020-10-15 15:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 11:20 [Bug tree-optimization/96974] New: " ktkachov at gcc dot gnu.org
2020-09-08 11:21 ` [Bug tree-optimization/96974] " ktkachov at gcc dot gnu.org
2020-09-08 13:03 ` rguenth at gcc dot gnu.org
2020-10-15 15:36 ` stammark at gcc dot gnu.org [this message]
2021-01-05 10:09 ` ktkachov at gcc dot gnu.org
2021-01-18 10:29 ` stammark at gcc dot gnu.org
2021-01-18 10:38 ` rsandifo at gcc dot gnu.org
2021-01-18 13:32 ` stammark at gcc dot gnu.org
2021-01-18 13:48 ` rsandifo at gcc dot gnu.org
2021-01-18 13:52 ` stammark at gcc dot gnu.org
2021-01-28 11:47 ` stammark at gcc dot gnu.org
2021-01-28 11:47 ` stammark at gcc dot gnu.org
2021-01-28 11:59 ` rsandifo at gcc dot gnu.org
2021-01-28 13:12 ` rguenth at gcc dot gnu.org
2021-03-25 15:30 ` cvs-commit at gcc dot gnu.org
2021-03-25 15:32 ` cvs-commit at gcc dot gnu.org
2021-03-31 9:42 ` ktkachov at gcc dot gnu.org
2021-03-31 9:54 ` rguenth at gcc dot gnu.org
2021-03-31 13:57 ` cvs-commit at gcc dot gnu.org
2021-03-31 13:59 ` cvs-commit 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-96974-4-npzZ5StjMk@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).