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/105532] [11/12 Regression] UBSAN: gcc/hwint.h:293:61: runtime error: shift exponent 64 is too large for 64-bit type 'long unsigned int'
Date: Sat, 11 Mar 2023 01:29:29 +0000	[thread overview]
Message-ID: <bug-105532-4-HO47ozewe8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105532-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Andrew Pinski
<pinskia@gcc.gnu.org>:

https://gcc.gnu.org/g:67608f7a2cf3eff99654ab3f44d5183049e3b36c

commit r12-9241-g67608f7a2cf3eff99654ab3f44d5183049e3b36c
Author: Andrew Pinski <apinski@marvell.com>
Date:   Wed Nov 2 15:56:31 2022 +0000

    Fix PR 105532: match.pd patterns calling tree_nonzero_bits with vector
types

    Even though this PR was reported with an ubsan issue, the problem is
    tree_nonzero_bits is being called with an expression which is a vector
type.
    This fixes three patterns I noticed which does that.
    And adds a testcase for one of the patterns.

    Committed after a bootstrapped and tested on x86_64-linux-gnu with no
regressions

    gcc/ChangeLog:

            PR tree-optimization/105532
            * match.pd (~(X >> Y) -> ~X >> Y): Check if it is an integral
            type before calling tree_nonzero_bits.
            (popcount(X) + popcount(Y)): Likewise.
            (popcount(X&C1)): Likewise.

    gcc/testsuite/ChangeLog:

            * gcc.c-torture/compile/vector-shift-1.c: New test.

    (cherry picked from commit 193fccaa5c3525e979a989835c47c76d2c49d10c)

  parent reply	other threads:[~2023-03-11  1:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 10:54 [Bug tree-optimization/105532] New: " zsojka at seznam dot cz
2022-11-02  1:42 ` [Bug tree-optimization/105532] " pinskia at gcc dot gnu.org
2022-11-02  1:51 ` [Bug tree-optimization/105532] [11/12/13 Regression] " pinskia at gcc dot gnu.org
2022-11-02  6:36 ` pinskia at gcc dot gnu.org
2022-11-02 16:24 ` pinskia at gcc dot gnu.org
2022-11-02 16:30 ` pinskia at gcc dot gnu.org
2022-11-02 21:47 ` pinskia at gcc dot gnu.org
2022-12-20 13:45 ` rguenth at gcc dot gnu.org
2022-12-21 18:33 ` cvs-commit at gcc dot gnu.org
2022-12-21 18:34 ` [Bug tree-optimization/105532] [11/12 " pinskia at gcc dot gnu.org
2023-03-11  1:29 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-11  1:30 ` [Bug tree-optimization/105532] [11 " pinskia at gcc dot gnu.org
2023-05-29 10:06 ` 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-105532-4-HO47ozewe8@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).