public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103202] [12 regression] gcc miscompiles ed-1.17 since r12-3876-g4a960d548b7d7d94 Date: Fri, 12 Nov 2021 10:18:40 +0000 [thread overview] Message-ID: <bug-103202-4-V5dK5HjG4U@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103202-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103202 --- Comment #6 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- Not looking at this yet, but disabling jump threading from all passes (dom included) makes the problem go away: $ ./xgcc -B./ a.c -w -O2 -fno-thread-jumps && ./a.out element 1 element 2 element 3 ...so *maybe* threading related. The minimum number of threads that reproduces this is: ./xgcc -B./ a.c -w -O2 -fdbg-cnt=registered_jump_thread:1-1:3-3:5-5 && ./a.out ***dbgcnt: lower limit 1 reached for registered_jump_thread.*** ***dbgcnt: upper limit 1 reached for registered_jump_thread.*** ***dbgcnt: lower limit 3 reached for registered_jump_thread.*** ***dbgcnt: upper limit 3 reached for registered_jump_thread.*** ***dbgcnt: lower limit 5 reached for registered_jump_thread.*** ***dbgcnt: upper limit 5 reached for registered_jump_thread.*** element 1 element 2 $ grep 'Register.*jump' a.c.* a.c.111t.threadfull1: [1] Registering jump thread: (6, 7) incoming edge; (7, 9) nocopy; a.c.126t.thread1: [3] Registering jump thread: (2, 4) incoming edge; (4, 12) nocopy; a.c.191t.thread2: [5] Registering jump thread: (13, 11) incoming edge; (11, 10) nocopy;
next prev parent reply other threads:[~2021-11-12 10:18 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-11 23:59 [Bug tree-optimization/103202] New: [12 regression] gcc miscompiles ed-1.17 slyfox at gcc dot gnu.org 2021-11-12 0:01 ` [Bug tree-optimization/103202] " pinskia at gcc dot gnu.org 2021-11-12 0:05 ` pinskia at gcc dot gnu.org 2021-11-12 1:38 ` pinskia at gcc dot gnu.org 2021-11-12 7:43 ` rguenth at gcc dot gnu.org 2021-11-12 9:15 ` slyfox at gcc dot gnu.org 2021-11-12 9:33 ` rguenth at gcc dot gnu.org 2021-11-12 9:35 ` [Bug tree-optimization/103202] [12 regression] gcc miscompiles ed-1.17 since r12-3876-g4a960d548b7d7d94 marxin at gcc dot gnu.org 2021-11-12 10:18 ` aldyh at gcc dot gnu.org [this message] 2021-11-12 10:19 ` aldyh at gcc dot gnu.org 2021-11-12 15:23 ` aldyh at gcc dot gnu.org 2021-11-12 15:24 ` aldyh at gcc dot gnu.org 2021-11-12 16:42 ` slyfox at gcc dot gnu.org 2021-11-12 19:46 ` cvs-commit at gcc dot gnu.org 2021-11-12 19:47 ` aldyh 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-103202-4-V5dK5HjG4U@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).