public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/110466] New: jit.dg FAILs on ppc64le
Date: Wed, 28 Jun 2023 19:28:17 +0000 [thread overview]
Message-ID: <bug-110466-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110466
Bug ID: 110466
Summary: jit.dg FAILs on ppc64le
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: jit
Assignee: dmalcolm at gcc dot gnu.org
Reporter: mpolacek at gcc dot gnu.org
Target Milestone: ---
On ppc64le:
$ make check RUNTESTFLAGS=jit.exp
Running /home/polacek/src/gcc/gcc/testsuite/jit.dg/jit.exp ...
FAIL: jit.dg/test-combination.c, initial compilation
FAIL: FAIL
FAIL: FAIL
FAIL: FAIL
FAIL: jit.dg/test-expressions.c, initial compilation
FAIL: jit.dg/test-threads.c, initial compilation
=== jit Summary ===
# of expected passes 6632
# of unexpected failures 6
# of unsupported tests 4
make[1]: Leaving directory `/home/polacek/x/trunk/gcc'
I suspect that's so since
commit d2e782cb99c3116c389d6a9565678c4ffe267777
Author: Antoni Boucher <bouanto@zoho.com>
Date: Sun Nov 20 10:22:53 2022 -0500
libgccjit: Fix float vector comparison
next reply other threads:[~2023-06-28 19:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 19:28 mpolacek at gcc dot gnu.org [this message]
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
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@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).