public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111362] [14 Regression] '-fcompare-debug' failure (length) with -O -fno-tree-ch --param=max-completely-peel-times=0 -march=rv64iv
Date: Thu, 14 Sep 2023 15:10:55 +0000 [thread overview]
Message-ID: <bug-111362-4-nG96v7Z8Nz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111362-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111362
--- Comment #2 from Zdenek Sojka <zsojka at seznam dot cz> ---
Thank you the fix; the testcase is still failing with a bit different flags
though:
Adding -fno-dce -fschedule-insns:
$ riscv64-unknown-linux-gnu-gcc -O -fno-tree-ch
--param=max-completely-peel-times=0 -march=rv64iv -fcompare-debug -fno-dce
-fschedule-insns testcase.c -save-temps
riscv64-unknown-linux-gnu-gcc: error: testcase.c: '-fcompare-debug' failure
$ diff -u *gkd
--- a-testcase.c.gkd 2023-09-14 17:09:28.262936149 +0200
+++ a-testcase.gk.c.gkd 2023-09-14 17:09:28.342935710 +0200
@@ -51,14 +51,6 @@
(sign_extend:DI (plus:SI (reg:SI 8 s0 [orig:134 ivtmp_6 ] [134])
(const_int -1 [0xffffffffffffffff])))) "testcase.c":3:26
discrim 1# {addsi3_extended}
(nil))
-(insn # 0 0 (set (reg:DI 11 a1)
- (const_int 0 [0])) "testcase.c":4:5# {*movdi_64bit}
- (nil))
-(insn # 0 0 (set (reg:DI 10 a0)
- (lo_sum:DI (reg/f:DI 9 s1 [138])
- (symbol_ref/f:DI ("*.LC0") [flags 0x82] <var_decl # *.LC0>)))
"testcase.c":4:5# {*lowdi}
- (expr_list:REG_EQUAL (symbol_ref/f:DI ("*.LC0") [flags 0x82] <var_decl #
*.LC0>)
- (nil)))
(jump_insn # 0 0 (set (pc)
(if_then_else (ne (reg:DI 8 s0 [orig:134 ivtmp_6 ] [134])
(const_int 0 [0]))
@@ -104,6 +96,14 @@
(barrier # 0 0)
(code_label # 0 0 3 (nil) [1 uses])
(note # 0 0 [bb 5] NOTE_INSN_BASIC_BLOCK)
+(insn # 0 0 (set (reg:DI 11 a1)
+ (const_int 0 [0])) "testcase.c":4:5# {*movdi_64bit}
+ (nil))
+(insn # 0 0 (set (reg:DI 10 a0)
+ (lo_sum:DI (reg/f:DI 9 s1 [138])
+ (symbol_ref/f:DI ("*.LC0") [flags 0x82] <var_decl # *.LC0>)))
"testcase.c":4:5# {*lowdi}
+ (expr_list:REG_EQUAL (symbol_ref/f:DI ("*.LC0") [flags 0x82] <var_decl #
*.LC0>)
+ (nil)))
(call_insn # 0 0 (parallel [
(set (reg:DI 10 a0)
(call (mem:SI (symbol_ref:DI ("printf") [flags 0x41]
<function_decl # __builtin_printf>) [ __builtin_printf S4 A32])
next prev parent reply other threads:[~2023-09-14 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 11:15 [Bug target/111362] New: " zsojka at seznam dot cz
2023-09-12 12:20 ` [Bug target/111362] " rguenth at gcc dot gnu.org
2023-09-13 6:19 ` cvs-commit at gcc dot gnu.org
2023-09-14 15:10 ` zsojka at seznam dot cz [this message]
2024-03-09 17:46 ` law at gcc dot gnu.org
2024-03-09 23:45 ` law at gcc dot gnu.org
2024-03-10 2:39 ` cvs-commit at gcc dot gnu.org
2024-03-10 2:40 ` law at gcc dot gnu.org
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-111362-4-nG96v7Z8Nz@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).