public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/94439] [10 Regression] gcc: error: gcc/testsuite/gcc.dg/torture/builtin-complex-1.c: ‘-fcompare-debug’ failure since r10-3499-g0ce77f463d1d150e Date: Wed, 01 Apr 2020 13:17:37 +0000 [thread overview] Message-ID: <bug-94439-4-pVa0tQY4gy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94439-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94439 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- This diverges during sched2, on the reduced testcase with additional --param=min-nondebug-insn-uid=10000 I see: -(insn 10076 10075 10055 2 (set (reg:SI 43 r15) - (mem/c:SI (const:DI (plus:DI (symbol_ref:DI ("cs.0") [flags 0x2] <var_decl 0x7f4364f38900 cs>) +(insn 10076 10075 221 2 (set (reg:SI 40 r12) + (mem/c:SI (const:DI (plus:DI (symbol_ref:DI ("cs.0") [flags 0x2] <var_decl 0x7f4bee787900 cs>) (const_int 24 [0x18]))) [1 cs+24 S4 A64])) "builtin-complex-1.c":50:3 67 {*movsi_internal} (nil)) difference between -g0 and -g.
next prev parent reply other threads:[~2020-04-01 13:17 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-01 12:35 [Bug debug/94439] New: " marxin at gcc dot gnu.org 2020-04-01 12:36 ` [Bug debug/94439] [10 Regression] " marxin at gcc dot gnu.org 2020-04-01 12:57 ` jakub at gcc dot gnu.org 2020-04-01 13:17 ` jakub at gcc dot gnu.org [this message] 2020-04-02 11:16 ` jakub at gcc dot gnu.org 2020-04-17 18:11 ` law at redhat dot com 2020-04-17 19:16 ` law at redhat dot com 2020-04-17 19:21 ` law at redhat dot com 2020-04-18 15:40 ` cvs-commit at gcc dot gnu.org 2020-04-18 15:41 ` law at redhat 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-94439-4-pVa0tQY4gy@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).