From: Jeff Law <jeffreyalaw@gmail.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
Vineet Gupta <vineetg@rivosinc.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v2] RISC-V: zicond: Fix opt2 pattern
Date: Mon, 4 Sep 2023 23:33:20 -0600 [thread overview]
Message-ID: <d46c2790-a5bf-4a87-acaf-28977578a283@gmail.com> (raw)
In-Reply-To: <2bc7f639-6fd9-49e6-ba30-03617598ac24@irq.a4lg.com>
On 9/4/23 20:19, Tsukasa OI wrote:
>
> -FAIL: 30_threads/async/async.cc execution test
> +FAIL: gcc.c-torture/execute/pr60003.c -O1 execution test
> +FAIL: gcc.dg/setjmp-3.c execution test
> +FAIL: gcc.dg/torture/stackalign/setjmp-3.c -O1 execution test
> +FAIL: gcc.dg/torture/stackalign/setjmp-3.c -O1 -fpic execution test
FWIW, I've got async.cc marked here as flakey when run under QEMU.
That's also consistent with what I found at a prior employer when
working on a private GCC port.
Jeff
prev parent reply other threads:[~2023-09-05 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 19:53 Vineet Gupta
2023-09-04 23:16 ` Jeff Law
2023-09-05 15:20 ` [Committed] " Vineet Gupta
2023-09-05 2:19 ` [PATCH v2] " Tsukasa OI
2023-09-05 5:33 ` Jeff Law [this message]
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=d46c2790-a5bf-4a87-acaf-28977578a283@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=research_trasio@irq.a4lg.com \
--cc=vineetg@rivosinc.com \
/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).