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/111648] [14 Regression] Wrong code at -O2/3 on x86_64-linux-gnu since r14-3243-ga7dba4a1c05
Date: Wed, 18 Oct 2023 19:04:02 +0000	[thread overview]
Message-ID: <bug-111648-4-HcR67u7pCs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111648-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Prathamesh Kulkarni
<prathamesh3492@gcc.gnu.org>:

https://gcc.gnu.org/g:3ec8ecb8e92faec889bc6f7aeac9ff59e82b4f7f

commit r14-4726-g3ec8ecb8e92faec889bc6f7aeac9ff59e82b4f7f
Author: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
Date:   Thu Oct 19 00:29:38 2023 +0530

    PR111648: Fix wrong code-gen due to incorrect VEC_PERM_EXPR folding.

    gcc/ChangeLog:
            PR tree-optimization/111648
            * fold-const.cc (valid_mask_for_fold_vec_perm_cst_p): If a1
            chooses base element from arg, ensure that it's a natural stepped
            sequence.
            (build_vec_cst_rand): New param natural_stepped and use it to
            construct a naturally stepped sequence.
            (test_nunits_min_2): Add new unit tests Case 6 and Case 7.

  parent reply	other threads:[~2023-10-18 19:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-30 14:04 [Bug tree-optimization/111648] New: " shaohua.li at inf dot ethz.ch
2023-09-30 16:48 ` [Bug tree-optimization/111648] " prathamesh3492 at gcc dot gnu.org
2023-10-01 18:49 ` [Bug tree-optimization/111648] [14 Regression] " pinskia at gcc dot gnu.org
2023-10-03 12:19 ` prathamesh3492 at gcc dot gnu.org
2023-10-03 12:21 ` prathamesh3492 at gcc dot gnu.org
2023-10-04  9:25 ` rguenth at gcc dot gnu.org
2023-10-18 19:04 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-18 19:06 ` prathamesh3492 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-111648-4-HcR67u7pCs@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).