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/99225] [8/9/10/11 Regression] ICE in wide_int_to_tree_1, at tree.c:1644
Date: Wed, 24 Feb 2021 11:11:25 +0000	[thread overview]
Message-ID: <bug-99225-4-72tlIfrV8G@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99225-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99225

--- Comment #3 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:6e646abbe02f2c79cc3ba1f3de705ee62ff9dcd1

commit r11-7356-g6e646abbe02f2c79cc3ba1f3de705ee62ff9dcd1
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Feb 24 12:10:25 2021 +0100

    fold-const: Fix up ((1 << x) & y) != 0 folding for vectors [PR99225]

    This optimization was written purely with scalar integers in mind,
    can work fine even with vectors, but we can't use build_int_cst but
    need to use build_one_cst instead.

    2021-02-24  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/99225
            * fold-const.c (fold_binary_loc) <case NE_EXPR>: In (x & (1 << y))
!= 0
            to ((x >> y) & 1) != 0 simplifications use build_one_cst instead of
            build_int_cst (..., 1).  Formatting fixes.

            * gcc.c-torture/compile/pr99225.c: New test.

  parent reply	other threads:[~2021-02-24 11:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 18:29 [Bug c/99225] New: " gscfq@t-online.de
2021-02-23 18:46 ` [Bug c/99225] [8/9/10/11 Regression] " jakub at gcc dot gnu.org
2021-02-23 18:52 ` jakub at gcc dot gnu.org
2021-02-23 19:16 ` jakub at gcc dot gnu.org
2021-02-24 11:11 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-24 11:15 ` [Bug tree-optimization/99225] [8/9/10 " jakub at gcc dot gnu.org
2021-03-19 23:29 ` cvs-commit at gcc dot gnu.org
2021-03-20  8:08 ` [Bug tree-optimization/99225] [8/9 " jakub at gcc dot gnu.org
2021-04-20 23:32 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:51 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:11 ` 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-99225-4-72tlIfrV8G@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).