public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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: Wed, 08 Feb 2023 12:41:52 +0000 [thread overview]
Message-ID: <bug-108688-4-497eVcMur8@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 #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #5)
> Oh I might have a fix for this already just didn't have a testcase for the
> upstream compiler at the time.
Note, it is just the first case from the above because @0 already ought to be
guaranteed to have mode precision because BIT_INSERT_EXPR requires it too.
On the other side, we should for the first case differentiate between @1 has
mode precision, then we can do what we do right now, or when isize == rsize and
rpos == ipos (then we can just simplify to possibly casted @1) and finally
otherwise, IMHO we should just punt.
next prev parent reply other threads:[~2023-02-08 12:41 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 [this message]
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
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-497eVcMur8@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).