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 target/112583] RISC-V regression testsuite errors with rv64gcv_zvl128b
Date: Mon, 27 Nov 2023 17:25:38 +0000	[thread overview]
Message-ID: <bug-112583-4-vGf4MREtH8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112583-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583

Patrick O'Neill <patrick at rivosinc dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #56659|0                           |1
        is obsolete|                            |

--- Comment #7 from Patrick O'Neill <patrick at rivosinc dot com> ---
Created attachment 56698
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56698&action=edit
rv64gcv_zvl128b testsuite failures 2023-11-27

Tested with hash 9866c98e1015d98b8fc346d7cf73a0070cce5f69
CI run:
https://github.com/patrick-rivos/gcc-postcommit-ci/actions/runs/6988591247

Resolved failures (improved from 30d8188e6d1b450533ab0055b951ebfc75022219)
ERROR: gcc.dg/tree-ssa/return-value-range-1.c: 1: syntax error for " dg-do 1
ling "
ERROR: gcc.dg/tree-ssa/return-value-range-1.c: 1: syntax error for " dg-do 1
ling "
FAIL: gcc.dg/tree-ssa/ssa-lim-11.c scan-tree-dump-times lim2 "Executing store
motion of __gcov0.access_buf\\[[12]\\] from loop 1" 2
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c
execution test
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c
execution test
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c
execution test
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c
execution test
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c
execution test
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c
execution test
FAIL: gcc.dg/gomp/pr27573.c (internal compiler error: verify_gimple failed)
FAIL: gcc.dg/gomp/pr27573.c (test for excess errors)
FAIL: gfortran.dg/gomp/pr27573.f90   -O  (internal compiler error:
verify_gimple failed)
FAIL: gfortran.dg/gomp/pr27573.f90   -O  (test for excess errors)
FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++2b (test for excess errors)

New failures (regression from 30d8188e6d1b450533ab0055b951ebfc75022219)
FAIL: gcc.dg/tree-prof/time-profiler-3.c scan-ipa-dump-times profile "Read
tp_first_run: 0" 1
FAIL: gcc.dg/tree-prof/time-profiler-3.c scan-ipa-dump-times profile "Read
tp_first_run: 2" 1

These new fails were introduced in this range of commits: 
https://github.com/gcc-mirror/gcc/compare/7bf1de918608e2d0b5a3ad0923040acb1819d9a5...41aacdea55c5d795a7aa195357d966645845d00e
Postcommit CI run:
https://github.com/patrick-rivos/gcc-postcommit-ci/issues/200

  parent reply	other threads:[~2023-11-27 17:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17  8:08 [Bug target/112583] New: " patrick at rivosinc dot com
2023-11-17 21:21 ` [Bug target/112583] " patrick at rivosinc dot com
2023-11-20 10:11 ` juzhe.zhong at rivai dot ai
2023-11-20 16:08 ` rdapp at gcc dot gnu.org
2023-11-20 18:04 ` patrick at rivosinc dot com
2023-11-20 23:45 ` patrick at rivosinc dot com
2023-11-21 17:25 ` patrick at rivosinc dot com
2023-11-27 17:25 ` patrick at rivosinc dot com [this message]
2023-11-27 17:34 ` pinskia at gcc dot gnu.org
2023-12-04  4:01 ` juzhe.zhong at rivai dot ai
2023-12-04 10:23 ` rdapp at gcc dot gnu.org
2023-12-04 12:53 ` rdapp at gcc dot gnu.org
2023-12-04 13:09 ` rdapp at gcc dot gnu.org
2023-12-04 21:21 ` patrick at rivosinc dot com
2023-12-05  7:42 ` rdapp at gcc dot gnu.org
2023-12-11 19:57 ` patrick at rivosinc dot com
2024-01-24 23:53 ` 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-112583-4-vGf4MREtH8@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).