From: Vineet Gupta <vineetg@rivosinc.com>
To: Thomas Schwinge <thomas.schwinge@siemens.com>,
Andreas Schwab <schwab@suse.de>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Jeff Law <jlaw@ventanamicro.com>,
gcc-patches@gcc.gnu.org, Kito Cheng <kito.cheng@sifive.com>,
"Maciej W . Rozycki" <macro@embecosm.com>
Subject: Re: RISC-V Test Errors and Failures
Date: Thu, 25 May 2023 17:04:12 -0700 [thread overview]
Message-ID: <ad8a98da-0231-7a95-017b-ea5d8ae65678@rivosinc.com> (raw)
In-Reply-To: <87h6s0rw7b.fsf@dem-tschwing-1.ger.mentorg.com>
On 5/25/23 13:29, Thomas Schwinge wrote:
> Hi!
>
> On 2023-05-17T09:52:13+0200, Andreas Schwab via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>> On Mai 16 2023, Vineet Gupta wrote:
>>
>>> Yes I was seeing similar tcl errors and such - and in my case an even
>>> higher count.
>> They are coming from commit d6654a4be3b.
> I call FUD. Until you prove otherwise, of coures.
>
>
> Grüße
> Thomas
Just as a data point, with those patches reverted, I don't see the tcl
errors.
2023-05-25 7a3c9f8e8362 Revert "Let each 'lto_init' determine the
default 'LTO_OPTIONS', and 'torture-init' the 'LTO_TORTURE_OPTIONS'"
2023-05-25 22206cb760ee Revert "Testsuite: Add missing
'torture-init'/'torture-finish' around 'LTO_TORTURE_OPTIONS' usage"
2023-05-25 db46b946dd6d Revert "Testsuite: Add 'torture-init-done', and
use it to conditionalize implicit 'torture-init'"
2023-05-25 bd412162fd0d Revert "xxx vineet fixup"
2023-05-22 97a5e2241d33 xxx vineet fixup
2023-05-24 ec2e86274427 Fortran: reject bad DIM argument of SIZE
intrinsic in simplification [PR104350]
...
========= Summary of gcc testsuite =========
| # of unexpected case / # of unique
unexpected case
| gcc | g++ | gfortran |
rv64imafdc/ lp64d/ medlow | 25 / 4 | 1 / 1 | 72 / 12 |
rv32imafdc/ ilp32d/ medlow | 26 / 5 | 3 / 2 | 72 / 12 |
rv32imac/ ilp32/ medlow | 25 / 4 | 3 / 2 | 109 / 19 |
rv64imac/ lp64/ medlow | 26 / 5 | 1 / 1 | 109 / 19 |
next prev parent reply other threads:[~2023-05-26 0:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 23:06 Palmer Dabbelt
2023-05-17 0:16 ` Vineet Gupta
2023-05-17 0:20 ` Palmer Dabbelt
2023-05-17 1:04 ` Vineet Gupta
2023-05-17 1:29 ` Palmer Dabbelt
2023-05-17 2:00 ` Jeff Law
2023-05-17 2:05 ` Palmer Dabbelt
2023-05-17 2:32 ` Jeff Law
2023-05-17 2:39 ` Palmer Dabbelt
2023-05-17 4:08 ` Jeff Law
2023-05-17 2:08 ` Vineet Gupta
2023-05-17 2:12 ` Jeff Law
2023-05-17 7:52 ` Andreas Schwab
2023-05-19 0:13 ` Vineet Gupta
2023-05-25 20:29 ` Thomas Schwinge
2023-05-26 0:04 ` Vineet Gupta [this message]
2023-05-17 1:57 juzhe.zhong
2023-05-17 2:02 ` Andrew Pinski
2023-05-17 2:07 juzhe.zhong
2023-05-17 2:13 ` Palmer Dabbelt
2023-05-17 2:20 ` Kito Cheng
2023-05-17 2:21 ` Kito Cheng
2023-05-17 2:46 ` Vineet Gupta
2023-05-17 2:47 ` Palmer Dabbelt
2023-05-17 2:51 ` Patrick O'Neill
2023-05-17 2:53 ` Palmer Dabbelt
2023-05-17 3:08 ` Vineet Gupta
2023-05-17 3:11 ` Palmer Dabbelt
2023-05-17 3:33 ` Kito Cheng
2023-05-17 4:04 ` Jeff Law
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=ad8a98da-0231-7a95-017b-ea5d8ae65678@rivosinc.com \
--to=vineetg@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.com \
--cc=kito.cheng@sifive.com \
--cc=macro@embecosm.com \
--cc=palmer@dabbelt.com \
--cc=schwab@suse.de \
--cc=thomas.schwinge@siemens.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).