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 jit/110466] jit.dg FAILs on ppc64le
Date: Fri, 30 Jun 2023 15:20:33 +0000 [thread overview]
Message-ID: <bug-110466-4-ZL6VuaaJ4m@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110466-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110466
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:
https://gcc.gnu.org/g:6735d66083953315c0d7d491df07d36061093a24
commit r14-2222-g6735d66083953315c0d7d491df07d36061093a24
Author: David Malcolm <dmalcolm@redhat.com>
Date: Fri Jun 30 11:20:02 2023 -0400
jit: avoid using __vector in testcase [PR110466]
r13-4531-gd2e782cb99c311 added test coverage to libgccjit's vector
support, but used __vector, which doesn't work on Power. Additionally
the size param to gcc_jit_type_get_vector was wrong.
Fixed thusly.
gcc/testsuite/ChangeLog:
PR jit/110466
* jit.dg/test-expressions.c (run_test_of_comparison): Fix size
param to gcc_jit_type_get_vector.
(verify_comparisons): Use a typedef rather than __vector.
Co-authored-by: Marek Polacek <polacek@redhat.com>
Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2023-06-30 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 19:28 [Bug jit/110466] New: " mpolacek at gcc dot gnu.org
2023-06-28 19:29 ` [Bug jit/110466] " mpolacek at gcc dot gnu.org
2023-06-28 21:02 ` dmalcolm at gcc dot gnu.org
2023-06-28 21:38 ` dmalcolm at gcc dot gnu.org
2023-06-28 21:42 ` pinskia at gcc dot gnu.org
2023-06-28 21:43 ` pinskia at gcc dot gnu.org
2023-06-28 22:28 ` dmalcolm at gcc dot gnu.org
2023-06-30 15:20 ` cvs-commit at gcc dot gnu.org [this message]
2023-06-30 15:20 ` cvs-commit at gcc dot gnu.org
2023-06-30 16:01 ` dmalcolm at gcc dot gnu.org
2024-05-09 17:11 ` cvs-commit at gcc dot gnu.org
2024-05-09 17:11 ` cvs-commit at gcc dot gnu.org
2024-05-10 18:58 ` dmalcolm 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-110466-4-ZL6VuaaJ4m@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).