public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "patrick at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/111969] New: RISC-V rv32gcv: 12 grouped flaky failures Date: Tue, 24 Oct 2023 22:49:43 +0000 [thread overview] Message-ID: <bug-111969-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111969 Bug ID: 111969 Summary: RISC-V rv32gcv: 12 grouped flaky failures Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: patrick at rivosinc dot com Target Milestone: --- These 12 testcases are flaky on _only_ the rv32gcv glibc target. They either all fail or all pass as a group. FAIL: gcc.dg/nextafter-2.c execution test FAIL: gfortran.dg/default_format_2.f90 -O0 execution test FAIL: gfortran.dg/default_format_2.f90 -O1 execution test FAIL: gfortran.dg/default_format_2.f90 -O2 execution test FAIL: gfortran.dg/default_format_2.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: gfortran.dg/default_format_2.f90 -O3 -g execution test FAIL: gfortran.dg/default_format_2.f90 -Os execution test FAIL: gfortran.dg/default_format_denormal_2.f90 -O0 execution test FAIL: gfortran.dg/default_format_denormal_2.f90 -O1 execution test FAIL: gfortran.dg/default_format_denormal_2.f90 -O2 execution test FAIL: gfortran.dg/default_format_denormal_2.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: gfortran.dg/default_format_denormal_2.f90 -O3 -g execution test FAIL: gfortran.dg/default_format_denormal_2.f90 -Os execution test FAIL: gfortran.dg/ieee/dec_math_1.f90 -O0 execution test FAIL: gfortran.dg/ieee/dec_math_1.f90 -O1 execution test FAIL: gfortran.dg/ieee/dec_math_1.f90 -O2 execution test FAIL: gfortran.dg/ieee/dec_math_1.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: gfortran.dg/ieee/dec_math_1.f90 -O3 -g execution test FAIL: gfortran.dg/ieee/dec_math_1.f90 -Os execution test FAIL: gfortran.dg/ieee/large_1.f90 -O0 execution test FAIL: gfortran.dg/ieee/large_2.f90 -O0 execution test FAIL: gfortran.dg/ieee/large_2.f90 -O1 execution test FAIL: gfortran.dg/ieee/large_2.f90 -O2 execution test FAIL: gfortran.dg/ieee/large_2.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: gfortran.dg/ieee/large_2.f90 -O3 -g execution test FAIL: gfortran.dg/ieee/large_2.f90 -Os execution test FAIL: gfortran.dg/intrinsic_pack_6.f90 -O2 execution test FAIL: gfortran.dg/intrinsic_pack_6.f90 -O3 -g execution test FAIL: gfortran.dg/large_real_kind_2.F90 -O0 execution test FAIL: gfortran.dg/round_4.f90 -O0 execution test FAIL: gfortran.dg/zero_sized_3.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: gfortran.fortran-torture/execute/intrinsic_count.f90 execution, -O2 -fomit-frame-pointer -finline-functions -funroll-loops FAIL: gfortran.fortran-torture/execute/intrinsic_matmul.f90 execution, -O2 FAIL: gfortran.fortran-torture/execute/intrinsic_matmul.f90 execution, -O2 -fbounds-check FAIL: gfortran.fortran-torture/execute/intrinsic_matmul.f90 execution, -O2 -fomit-frame-pointer -finline-functions FAIL: gfortran.fortran-torture/execute/intrinsic_matmul.f90 execution, -O2 -fomit-frame-pointer -finline-functions -funroll-loops FAIL: gfortran.fortran-torture/execute/intrinsic_matmul.f90 execution, -O3 -g FAIL: gfortran.fortran-torture/execute/intrinsic_sum.f90 execution, -O2 -fomit-frame-pointer -finline-functions -funroll-loops r14-4098-gbdb7d85dde5 is the first time the CI observed these failures. It's also relatively close to when we bumped the CI to QEMU v8.1.0 (~9 days after). It can clearly be seen on the risc-v CI dashboard: https://patrick-rivos.github.io/gcc-postcommit-ci/gcv where the fortran failures for the rv32gcv target goes from ~23 -> ~15 failures and back again. I'm investigating locally but not making much headway. Thought I'd chronicle what I learn in a bugzilla in case anyone else has insight into what this might be. Marking this as a testsuite framework issue as that's my best guess currently. I'll keep this issue updated as I investigate more.
next reply other threads:[~2023-10-24 22:49 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-24 22:49 patrick at rivosinc dot com [this message] 2023-10-24 22:58 ` [Bug testsuite/111969] " pinskia at gcc dot gnu.org 2023-10-25 7:40 ` schwab@linux-m68k.org 2023-10-25 17:36 ` patrick at rivosinc dot com 2023-10-25 17:39 ` patrick at rivosinc dot com 2023-10-25 21:43 ` patrick at rivosinc dot com 2023-10-26 18:46 ` patrick at rivosinc dot com
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-111969-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: linkBe 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).