[Bug target/94833] vec_first_match_index does not function as described in its description

2020-06-10 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94833

--- Comment #5 from CVS Commits  ---
The releases/gcc-8 branch has been updated by Carl Love :

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

commit r8-10304-gc6dce1d8083a2fdc94be167a2465db7fd837ccae
Author: Carl Love 
Date:   Wed Jun 10 16:12:08 2020 -0500

pr94833, fix vec_first_match_index for nulls

Backported patch from mainline.  Updated ChangeLog format
commit 24f68831d25bad739a6fe167a58b5b4c0c3cbf9a
Author: Carl Love 
Date:   Wed Apr 29 10:23:11 2020 -0500

Note the mainlin patch adds tests to the test case in mainline. 
The test
case does not exist in GCC 8.  Only the functional change in
gcc/config/rs6000/vsx.md was backported.

2020-06-10  Carl Love  

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

[Bug target/94833] vec_first_match_index does not function as described in its description

2020-06-06 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94833

--- Comment #4 from CVS Commits  ---
The releases/gcc-9 branch has been updated by Carl Love :

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

commit r9-8659-ga47259fa7737ff6d4a7def074fb30bc7baef2f86
Author: Carl Love 
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 
Date:   Wed Apr 29 10:23:11 2020 -0500

2020-04-30  Carl Love  

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

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

[Bug target/94833] vec_first_match_index does not function as described in its description

2020-05-18 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94833

--- Comment #3 from CVS Commits  ---
The master branch has been updated by Carl Love :

https://gcc.gnu.org/g:24f68831d25bad739a6fe167a58b5b4c0c3cbf9a

commit r11-458-g24f68831d25bad739a6fe167a58b5b4c0c3cbf9a
Author: Carl Love 
Date:   Wed Apr 29 10:23:11 2020 -0500

pr94833, fix vec_first_match_index for nulls

gcc/ChangeLog

2020-04-30  Carl Love  

PR target/94833
* config/rs6000/vsx.md (define_expand): Fix instruction generation
for
first_match_index_.
* testsuite/gcc.target/powerpc/builtins-8-p9-runnable.c (main): Add
additional test cases with zero vector elements.

[Bug target/94833] vec_first_match_index does not function as described in its description

2020-04-28 Thread carll at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94833

Carl Love  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
   Last reconfirmed||2020-04-28
   Assignee|unassigned at gcc dot gnu.org  |carll at gcc dot gnu.org
 Ever confirmed|0   |1

[Bug target/94833] vec_first_match_index does not function as described in its description

2020-04-28 Thread carll at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94833

--- Comment #2 from Carl Love  ---
The ABI has the builtin VEC_FIRST_MATCH_OR_EOS_
INDEX (ARG1, ARG2) which says

Returns the element index of the position of either the first character match
or an end-of-string (EOS) terminator. If no match or terminator, returns the
number of characters as an element count in the vector argument.

So, I do agree the builtin in question should be treating the EOS (null) as any
other number for comparison purposes.