public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98726] [10/11 Regression] SVE: tree check: expected integer_cst, have poly_int_cst in to_wide, at tree.h:5984
Date: Fri, 23 Apr 2021 09:10:44 +0000 [thread overview]
Message-ID: <bug-98726-4-XEvXWK6bHJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98726-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98726
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Richard Sandiford
<rsandifo@gcc.gnu.org>:
https://gcc.gnu.org/g:8849e4a94550ffc9a564c105f0cefed5f42b3a7d
commit r10-9752-g8849e4a94550ffc9a564c105f0cefed5f42b3a7d
Author: Richard Biener <rguenther@suse.de>
Date: Fri Apr 23 10:09:40 2021 +0100
middle-end/98726 - fix VECTOR_CST element access
This fixes VECTOR_CST element access with POLY_INT elements and
allows to produce dump files of the PR98726 testcase without
ICEing.
2021-04-23 Richard Biener <rguenther@suse.de>
PR middle-end/98726
* tree.h (vector_cst_int_elt): Remove.
* tree.c (vector_cst_int_elt): Use poly_wide_int for computations,
make static.
(cherry picked from commit 4b59dbb5d6759e43bfa23161a8d3feb9ae969e1a)
next prev parent reply other threads:[~2021-04-23 9:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 11:44 [Bug tree-optimization/98726] New: aarch64: " acoplan at gcc dot gnu.org
2021-01-18 11:44 ` [Bug tree-optimization/98726] SVE: " acoplan at gcc dot gnu.org
2021-01-18 12:25 ` [Bug tree-optimization/98726] [10/11 Regression] " ktkachov at gcc dot gnu.org
2021-01-26 12:29 ` rguenth at gcc dot gnu.org
2021-01-26 12:30 ` rguenth at gcc dot gnu.org
2021-01-26 12:42 ` rguenth at gcc dot gnu.org
2021-01-26 13:27 ` cvs-commit at gcc dot gnu.org
2021-01-26 13:30 ` rguenth at gcc dot gnu.org
2021-02-19 12:26 ` avieira at gcc dot gnu.org
2021-02-19 12:27 ` avieira at gcc dot gnu.org
2021-03-17 15:41 ` rsandifo at gcc dot gnu.org
2021-03-30 11:04 ` rsandifo at gcc dot gnu.org
2021-03-31 18:34 ` cvs-commit at gcc dot gnu.org
2021-03-31 20:38 ` rsandifo at gcc dot gnu.org
2021-04-23 9:10 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-23 9:10 ` 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-98726-4-XEvXWK6bHJ@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).