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/99882] [11 Regression] ICE in bswap_view_convert, at gimple-ssa-store-merging.c:988 since r11-7946-g5b9a65ecbeb22ef6
Date: Sat, 03 Apr 2021 08:08:43 +0000 [thread overview]
Message-ID: <bug-99882-4-enGxfImYnj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99882-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99882
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:a40015780f8cc49476741b6914bd5ee97bd10f1d
commit r11-7971-ga40015780f8cc49476741b6914bd5ee97bd10f1d
Author: Jakub Jelinek <jakub@redhat.com>
Date: Sat Apr 3 10:08:08 2021 +0200
bswap: Fix up bswap_view_convert after the recent change [PR99882]
Martin reported that my recent change to allow pointer types in bswap
broke valgrind. The bswap_view_convert function used for the
initialization
of vector CONSTRUCTOR from the identity or byte-swapped pieces
unfortunately
didn't handle pointer types. The following patch handles it there.
2021-04-03 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/99882
* gimple-ssa-store-merging.c (bswap_view_convert): Handle val with
pointer type.
* gcc.dg/pr99882.c: New test.
next prev parent reply other threads:[~2021-04-03 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 12:06 [Bug tree-optimization/99882] New: " marxin at gcc dot gnu.org
2021-04-02 12:06 ` [Bug tree-optimization/99882] " marxin at gcc dot gnu.org
2021-04-02 14:55 ` jakub at gcc dot gnu.org
2021-04-03 8:08 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-03 8:17 ` jakub 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-99882-4-enGxfImYnj@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).