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 middle-end/100672] wrong code with vector shift and unary minus
Date: Fri, 25 Jun 2021 09:05:55 +0000	[thread overview]
Message-ID: <bug-100672-4-r7G6SYTKuP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100672-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:e0dae9c92aa248c858f682f03ee1b16471297718

commit r11-8652-ge0dae9c92aa248c858f682f03ee1b16471297718
Author: Richard Biener <rguenther@suse.de>
Date:   Wed May 19 13:35:07 2021 +0200

    middle-end/100672 - fix bogus right shift folding

    This fixes the bogus use of TYPE_PRECISION on vector types
    from optimizing -((int)x >> 31) into (unsigned)x >> 31.

    2021-05-19  Richard Biener  <rguenther@suse.de>

            PR middle-end/100672
            * fold-const.c (fold_negate_expr_1): Use element_precision.
            (negate_expr_p): Likewise.

            * gcc.dg/torture/pr100672.c: New testcase.

    (cherry picked from commit 8d51039cb7c807ed84ff7df5416a1e3ba07a5e63)

  parent reply	other threads:[~2021-06-25  9:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 10:30 [Bug tree-optimization/100672] New: " zsojka at seznam dot cz
2021-05-19 10:32 ` [Bug tree-optimization/100672] " zsojka at seznam dot cz
2021-05-19 11:23 ` rguenth at gcc dot gnu.org
2021-05-19 11:26 ` rguenth at gcc dot gnu.org
2021-05-19 11:29 ` rguenth at gcc dot gnu.org
2021-05-19 11:32 ` rguenth at gcc dot gnu.org
2021-05-19 11:33 ` [Bug middle-end/100672] " rguenth at gcc dot gnu.org
2021-05-19 11:44 ` zsojka at seznam dot cz
2021-05-19 11:54 ` rguenth at gcc dot gnu.org
2021-05-19 11:56 ` zsojka at seznam dot cz
2021-05-19 12:00 ` zsojka at seznam dot cz
2021-05-19 13:41 ` cvs-commit at gcc dot gnu.org
2021-05-19 13:41 ` rguenth at gcc dot gnu.org
2021-06-25  9:05 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-09 13:05 ` cvs-commit at gcc dot gnu.org
2021-11-09 13:45 ` cvs-commit at gcc dot gnu.org
2021-11-09 13:45 ` rguenth 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-100672-4-r7G6SYTKuP@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).