public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/94281] [8/9/10 Regression] g++: error: hash.cpp: ‘-fcompare-debug’ failure (length) since r8-5241-g8697bf9f46f36168 Date: Tue, 24 Mar 2020 10:17:17 +0000 [thread overview] Message-ID: <bug-94281-4-mfPOxauR0T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94281-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94281 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW CC| |jakub at gcc dot gnu.org Assignee|marxin at gcc dot gnu.org |unassigned at gcc dot gnu.org --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- It has something to do with end location of function: $ cat hash.c void fn1() { } void fn2() { ; } $ ./xg++ -B. -g hash.c -c -O1 -fno-tree-dce -fipa-icf -fno-tree-forwprop -fdump-rtl-cmpelim=/dev/stdout ... (note 2 3 5 2 NOTE_INSN_FUNCTION_BEG) (debug_insn 5 2 8 2 (debug_marker) "hash.c":6:3 -1 (nil)) $ ./xg++ -B. -g hash.c -c -O1 -fno-tree-dce -fipa-icf -fno-tree-forwprop -fdump-rtl-pro_and_epilogue=/dev/stdout ... (note 2 9 5 2 NOTE_INSN_FUNCTION_BEG) (debug_insn 5 2 10 2 (debug_marker) "hash.c":6:3 -1 (nil)) (note 10 5 11 2 NOTE_INSN_EPILOGUE_BEG) (jump_insn 11 10 12 2 (simple_return) "hash.c":7:1 -1 (nil) -> simple_return) $ ./xg++ -B. -g hash.c -c -O1 -fno-tree-dce -fipa-icf -fno-tree-forwprop -fdump-rtl-pro_and_epilogue=/dev/stdout -g0 ... (note 9 2 10 2 NOTE_INSN_EPILOGUE_BEG) (jump_insn 10 9 11 2 (simple_return) "hash.c":4:6 -1 (nil) -> simple_return) So hash.c:4:6 is DECL_SOURCE_LOCATION while hash.c:7:1 is function_end_locus. So maybe a bad source_location or maybe screwed by IPA ICF. Anyway, leaving for now..
next prev parent reply other threads:[~2020-03-24 10:17 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-23 14:04 [Bug debug/94281] New: " marxin at gcc dot gnu.org 2020-03-23 14:04 ` [Bug debug/94281] [8/9/10 Regression] " marxin at gcc dot gnu.org 2020-03-23 15:23 ` rguenth at gcc dot gnu.org 2020-03-24 9:02 ` marxin at gcc dot gnu.org 2020-03-24 10:17 ` marxin at gcc dot gnu.org [this message] 2020-03-25 13:52 ` jakub at gcc dot gnu.org 2020-03-25 14:40 ` jakub at gcc dot gnu.org 2020-03-26 9:11 ` cvs-commit at gcc dot gnu.org 2020-03-30 15:07 ` [Bug debug/94281] [8/9 " jakub at gcc dot gnu.org 2021-05-14 9:53 ` [Bug debug/94281] [9 " jakub at gcc dot gnu.org 2021-06-01 8:17 ` rguenth at gcc dot gnu.org 2022-05-27 8:49 ` 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-94281-4-mfPOxauR0T@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).