public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/95123] [10/11 Regression] Wrong code w/ -O2 -fselective-scheduling2 -funroll-loops --param early-inlining-insns=5 --param loop-invariant-max-bbs-in-loop=3 --param max-jump-thread-duplication-stmts=0 Date: Thu, 14 May 2020 09:53:15 +0000 [thread overview] Message-ID: <bug-95123-4-rkJa6DGpqS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95123-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95123 Alexander Monakov <amonakov at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amonakov at gcc dot gnu.org --- Comment #1 from Alexander Monakov <amonakov at gcc dot gnu.org> --- This is probably due to sel-sched, and very sensitive to compiler revision: I tried checking with a 20200511 (one day difference) on Compiler Exporer, and could not reproduce the miscompilation. If you still have the compiler binary, you can help out by testing with sel-sched debug counters: if you append -fdbg-cnt=sel_sched_insn_cnt:0 to the "bad" command line, it should work again (as sel-sched will not move anything), with -fdbg-cnt=sel_sched_insn_cnt:99999 it should fail. We use this for isolating a problematic transformation (by bisecting on the counter value). (other sel-sched debug counters are sel_sched_cnt and sel_sched_region_cnt, but they are more coarse-grained, by pass and region, instead of insn, respectively)
next prev parent reply other threads:[~2020-05-14 9:53 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-14 8:20 [Bug rtl-optimization/95123] New: " asolokha at gmx dot com 2020-05-14 9:53 ` amonakov at gcc dot gnu.org [this message] 2020-05-14 10:16 ` [Bug rtl-optimization/95123] " marxin at gcc dot gnu.org 2020-05-14 10:33 ` asolokha at gmx dot com 2020-05-14 10:35 ` asolokha at gmx dot com 2020-05-14 10:39 ` asolokha at gmx dot com 2020-05-14 10:41 ` amonakov at gcc dot gnu.org 2020-05-14 10:47 ` asolokha at gmx dot com 2020-05-14 11:11 ` marxin at gcc dot gnu.org 2020-05-14 11:57 ` rguenth at gcc dot gnu.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2021-01-14 8:48 ` rguenth at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2022-01-30 0:26 ` [Bug rtl-optimization/95123] [10/11/12 Regression] Wrong code w/ -O2 -fselective-scheduling2 -funroll-loops --param early-inlining-insns=5 --param loop-invariant-max-bbs-in-loop=3 --param max-jump-thread-duplication-stmts=0 -fPIE pinskia at gcc dot gnu.org 2022-01-31 9:04 ` marxin at gcc dot gnu.org 2022-06-28 10:40 ` [Bug rtl-optimization/95123] [10/11/12/13 " jakub at gcc dot gnu.org 2023-07-07 10:37 ` [Bug rtl-optimization/95123] [11/12/13/14 " rguenth 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-95123-4-rkJa6DGpqS@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).