public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/61923] [4.8/4.9/4.10 Regression] -fcompare-debug errors while building Linux kernel. Date: Wed, 06 Aug 2014 02:00:00 -0000 [thread overview] Message-ID: <bug-61923-4-VIlCxf5T13@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61923-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61923 --- Comment #5 from Vladimir Makarov <vmakarov at gcc dot gnu.org> --- The difference after scheduling a block is in DFA state because of additional advance_one_cycle call when debug_insns are present. The situation looks like -g last bb insn last real bb insn -> advance_one_cycle ->advance_one_cycle debug_insn ->advance_one_cycle Last advance cycle is done at the end of processing all bb insns. I'll try to produce a patch tomorrow to fix it which is not easy as schedule_block is now very complicated function working in many modes and containing a lot of gotos.
next prev parent reply other threads:[~2014-08-06 2:00 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-26 20:03 [Bug debug/61923] New: " trippels at gcc dot gnu.org 2014-07-28 8:16 ` [Bug debug/61923] " rguenth at gcc dot gnu.org 2014-07-28 8:18 ` pinskia at gcc dot gnu.org 2014-07-29 6:54 ` trippels at gcc dot gnu.org 2014-08-01 11:44 ` jakub at gcc dot gnu.org 2014-08-06 2:00 ` vmakarov at gcc dot gnu.org [this message] 2014-08-06 15:36 ` vmakarov at gcc dot gnu.org 2014-08-06 15:41 ` vmakarov at gcc dot gnu.org 2014-08-06 16:00 ` trippels at gcc dot gnu.org 2014-09-08 19:07 ` [Bug debug/61923] [4.8 " jakub at gcc dot gnu.org 2014-09-08 19:17 ` jakub 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-61923-4-VIlCxf5T13@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).