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:11:43 +0000	[thread overview]
Message-ID: <bug-108688-4-qlQpgnrPzs@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 #11 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:bcca64d70ce91e29717fb70cff252639df6902be

commit r13-5758-gbcca64d70ce91e29717fb70cff252639df6902be
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Feb 9 16:07:40 2023 +0100

    match.pd: Simplify BFR of insert when extracting exactly all inserted bits
[PR108688]

    On Thu, Feb 09, 2023 at 09:16:17AM +0100, Richard Biener via Gcc-patches
wrote:
    > Hmm.  Can we handle the case of the extraction exactly covering the
    > insertion separately then and simplify to plain @1?

    I was suggesting that in the PR.  Here it is as an incremental patch
    on top of Andrew's patch.

    On the newly added testcase the ifcvt-folding difference without/with the
    incremental patch is:
    --- pr108688.c.171t.ifcvt_      2023-02-09 10:47:30.169916845 +0100
    +++ pr108688.c.171t.ifcvt       2023-02-09 10:48:44.942793453 +0100
    @@ -25,6 +25,8 @@ Number of blocks in CFG: 11
     Number of blocks to update: 5 ( 45%)

    +Applying pattern match.pd:7487, gimple-match.cc:243200
    +Applying pattern match.pd:3987, gimple-match.cc:75423
     Matching expression match.pd:1677, gimple-match.cc:209
     Applying pattern match.pd:1733, gimple-match.cc:109481
     Matching expression match.pd:2393, gimple-match.cc:852
    @@ -70,7 +72,6 @@ void foo ()
       signed char _29;
       <unnamed-signed:7> _30;
       unsigned int ivtmp_33;
    -  <unnamed-signed:7> _ifc__35;
       unsigned char _ifc__37;
       unsigned char _ifc__38;
       unsigned char _ifc__39;
    @@ -91,8 +92,7 @@ void foo ()
       _2 = (<unnamed-signed:7>) a.0_1;
       _ifc__38 = u.D.2741;
       _ifc__39 = BIT_INSERT_EXPR <_ifc__38, _2, 0 (7 bits)>;
    -  _ifc__35 = BIT_FIELD_REF <_ifc__39, 7, 0>;
    -  _4 = (signed char) _ifc__35;
    +  _4 = (signed char) _2;
       b.1_5 = b;
       _6 = (signed char) b.1_5;
       _7 = _4 ^ _6;

    2023-02-09  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/108688
            * match.pd (bit_field_ref [bit_insert]): Simplify BIT_FIELD_REF
            of BIT_INSERT_EXPR extracting exactly all inserted bits even
            when without mode precision.  Formatting fixes.

            * gcc.c-torture/compile/pr108688-1.c: Add PR number as comment.
            * gcc.dg/pr108688.c: New test.

  parent reply	other threads:[~2023-02-09 15:11 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
2023-02-09 15:11 ` cvs-commit at gcc dot gnu.org [this message]
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-qlQpgnrPzs@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).