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 target/94833] vec_first_match_index does not function as described in its description
Date: Sat, 06 Jun 2020 16:46:44 +0000	[thread overview]
Message-ID: <bug-94833-4-zwH5EvB98o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94833-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Carl Love <carll@gcc.gnu.org>:

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

commit r9-8659-ga47259fa7737ff6d4a7def074fb30bc7baef2f86
Author: Carl Love <cel@us.ibm.com>
Date:   Wed Apr 29 10:23:11 2020 -0500

    pr94833, fix vec_first_match_index for nulls

    Backported patch from mainline.  Updated ChangeLog format
            commit 24f68831d25bad739a6fe167a58b5b4c0c3cbf9a
            Author: Carl Love <cel@us.ibm.com>
            Date:   Wed Apr 29 10:23:11 2020 -0500

    2020-04-30  Carl Love  <cel@us.ibm.com>

    gcc/
            PR target/94833
            * config/rs6000/vsx.md (define_expand): Fix instruction generation
for
            first_match_index_<mode>.

    gcc/testsuite/
            PR target/94833
            * gcc.target/powerpc/builtins-8-p9-runnable.c (main): Add
            additional test cases with zero vector elements.

  parent reply	other threads:[~2020-06-06 16:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 20:43 [Bug c/94833] New: " cjashfor at linux dot ibm.com
2020-04-28 20:56 ` [Bug c/94833] " cjashfor at linux dot ibm.com
2020-04-28 22:13 ` [Bug target/94833] " carll at gcc dot gnu.org
2020-04-28 22:14 ` carll at gcc dot gnu.org
2020-05-18 17:14 ` cvs-commit at gcc dot gnu.org
2020-06-06 16:46 ` cvs-commit at gcc dot gnu.org [this message]
2020-06-10 21:16 ` 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-94833-4-zwH5EvB98o@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).