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 rtl-optimization/101562] [9/10/11/12 Regression] ICE in insert, at wide-int.cc:682
Date: Fri, 23 Jul 2021 17:56:17 +0000 [thread overview]
Message-ID: <bug-101562-4-SR6abqs9R7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101562-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101562
--- Comment #6 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:8408d34570c9fe9f3d22a25a76df2a4c64f08477
commit r12-2499-g8408d34570c9fe9f3d22a25a76df2a4c64f08477
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Jul 23 19:55:16 2021 +0200
expmed: Fix store_integral_bit_field [PR101562]
Our documentation says that paradoxical subregs shouldn't appear
in strict_low_part:
'(strict_low_part (subreg:M (reg:N R) 0))'
This expression code is used in only one context: as the
destination operand of a 'set' expression. In addition, the
operand of this expression must be a non-paradoxical 'subreg'
expression.
but on the testcase below that triggers UB at runtime
store_integral_bit_field emits exactly that.
The following patch fixes it by ensuring the requirement is satisfied.
2021-07-23 Jakub Jelinek <jakub@redhat.com>
PR rtl-optimization/101562
* expmed.c (store_integral_bit_field): Only use movstrict_optab
if the operand isn't paradoxical.
* gcc.c-torture/compile/pr101562.c: New test.
next prev parent reply other threads:[~2021-07-23 17:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 17:45 [Bug c/101562] New: " gscfq@t-online.de
2021-07-21 17:46 ` [Bug rtl-optimization/101562] " pinskia at gcc dot gnu.org
2021-07-21 18:05 ` pinskia at gcc dot gnu.org
2021-07-21 18:07 ` pinskia at gcc dot gnu.org
2021-07-22 6:55 ` rguenth at gcc dot gnu.org
2021-07-22 8:47 ` jakub at gcc dot gnu.org
2021-07-22 8:53 ` jakub at gcc dot gnu.org
2021-07-22 9:32 ` jakub at gcc dot gnu.org
2021-07-23 17:56 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-23 17:57 ` [Bug rtl-optimization/101562] [9/10/11 " jakub at gcc dot gnu.org
2021-07-28 9:06 ` cvs-commit at gcc dot gnu.org
2021-07-28 9:08 ` [Bug rtl-optimization/101562] [9/10 " jakub at gcc dot gnu.org
2022-05-10 8:20 ` cvs-commit at gcc dot gnu.org
2022-05-11 6:21 ` cvs-commit at gcc dot gnu.org
2022-05-11 6:36 ` 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-101562-4-SR6abqs9R7@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).