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/108688] [13 Regression] error: ‘bit_field_ref’ of non-mode-precision operand
Date: Thu, 09 Feb 2023 15:07:09 +0000 [thread overview]
Message-ID: <bug-108688-4-wR8rUmmx7I@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108688-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108688
--- Comment #10 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:44f308e59bfa0f93ae05b17e257d8563c12399fd
commit r13-5757-g44f308e59bfa0f93ae05b17e257d8563c12399fd
Author: Andrew Pinski <apinski@marvell.com>
Date: Thu Feb 9 16:03:54 2023 +0100
match.pd: When simplifying BFR of an insert, require a mode precision
integral type [PR108688]
The same problem as PR 88739 has crept in but
this time in match.pd when simplifying bit_field_ref of
an bit_insert. That is we are generating a BIT_FIELD_REF
of a non-mode-precision integral type.
PR tree-optimization/108688
* match.pd (bit_field_ref [bit_insert]): Avoid generating
BIT_FIELD_REFs of non-mode-precision integral operands.
* gcc.c-torture/compile/pr108688-1.c: New test.
next prev parent reply other threads:[~2023-02-09 15:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 19:50 [Bug c/108688] New: " dcb314 at hotmail dot com
2023-02-06 19:52 ` [Bug tree-optimization/108688] [13 Regression] " pinskia at gcc dot gnu.org
2023-02-06 19:54 ` pinskia at gcc dot gnu.org
2023-02-06 20:16 ` pinskia at gcc dot gnu.org
2023-02-07 14:07 ` rguenth at gcc dot gnu.org
2023-02-08 11:49 ` jakub at gcc dot gnu.org
2023-02-08 12:15 ` jakub at gcc dot gnu.org
2023-02-08 12:18 ` pinskia at gcc dot gnu.org
2023-02-08 12:41 ` jakub at gcc dot gnu.org
2023-02-08 16:26 ` pinskia at gcc dot gnu.org
2023-02-08 16:40 ` pinskia at gcc dot gnu.org
2023-02-08 21:15 ` pinskia at gcc dot gnu.org
2023-02-09 15:07 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-09 15:11 ` cvs-commit at gcc dot gnu.org
2023-02-09 15:15 ` jakub at gcc dot gnu.org
2023-02-10 17:46 ` cvs-commit at gcc dot gnu.org
2023-05-02 20:14 ` cvs-commit at gcc dot gnu.org
2023-05-03 15:21 ` 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-108688-4-wR8rUmmx7I@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).