public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113009] [14] RISC-V: gcc.c-torture/unsorted/dump-noaddr.c flakey tests
Date: Thu, 14 Dec 2023 00:54:34 +0000	[thread overview]
Message-ID: <bug-113009-4-YlJL2RFHmF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113009-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
(In reply to Edwin Lu from comment #2)
> Re-bisected to r14-6197-g2e7abd09621
> 
> Full steps to reproduce:
> mkdir dump1
> ./build-gcc-linux-stage2/gcc/xgcc -B./build-gcc-linux-stage2/gcc/  
> -march=rv64gcv -mabi=lp64d -mcmodel=medlow   -fdiagnostics-plain-output  -w 
> -O3 -g   -dumpbase dump1/dump-noaddr.c -DMASK=1 -x c --param
> ggc-min-heapsize=1 -fdump-ipa-all -fdump-rtl-all -fdump-tree-all
> -fdump-noaddr -gno-record-gcc-switches -c   -o
> ./build-gcc-linux-stage2/gcc/testsuite/gcc/dump-noaddr.o
> ../gcc/gcc/testsuite/gcc.c-torture/unsorted/dump-noaddr.c
> mv dump1 dump1-comp
> mkdir dump1
> for i in {1..100}; do 
>   ./build-gcc-linux-stage2/gcc/xgcc -B./build-gcc-linux-stage2/gcc/  
> -march=rv64gcv -mabi=lp64d -mcmodel=medlow   -fdiagnostics-plain-output  -w 
> -O3 -g   -dumpbase dump1/dump-noaddr.c -DMASK=1 -x c --param
> ggc-min-heapsize=1 -fdump-ipa-all -fdump-rtl-all -fdump-tree-all
> -fdump-noaddr -gno-record-gcc-switches -c   -o
> ./build-gcc-linux-stage2/gcc/testsuite/gcc/dump-noaddr.o
> ../gcc/gcc/testsuite/gcc.c-torture/unsorted/dump-noaddr.c && diff -d
> dump1/dump-noaddr.c.*r.avlprop ./dump1-comp/dump-noaddr.c.*r.avlprop; 
> done
> 
> may take around 2-3 min for the diff output to start appearing depending on
> whether the expected output is saved into dump-comp or not

Thanks for reporting it.  I will take a look at it.
That commit is to fix ICE and execution issues (real bugs).

We are busy with fixing real bugs (ICE and execution FAILs) on full coverage
testing.
Dump FAILs are bogus FAILs, it's low priority for now.

  parent reply	other threads:[~2023-12-14  0:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 21:50 [Bug target/113009] New: " ewlu at rivosinc dot com
2023-12-13 22:04 ` [Bug target/113009] " ewlu at rivosinc dot com
2023-12-14  0:51 ` ewlu at rivosinc dot com
2023-12-14  0:54 ` juzhe.zhong at rivai dot ai [this message]
2023-12-14  1:09 ` ewlu at rivosinc dot com
2023-12-15  6:50 ` juzhe.zhong at rivai dot ai
2023-12-15 19:27 ` ewlu 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-113009-4-YlJL2RFHmF@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).