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 middle-end/64937] [5 Regression] compare debug failure with -fsanitize=address Date: Thu, 05 Feb 2015 12:00:00 -0000 [thread overview] Message-ID: <bug-64937-4-1iYE8pXWbf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64937-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64937 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu.org --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I think the problem is that cgraph etc. uses the DECL_ABSTRACT_P flag, which is set in two different places: 1) in the C++ FE 2) in dwarf2out In the latter, it does: was_abstract = DECL_ABSTRACT_P (decl); set_decl_abstract_flags (decl, 1); dwarf2out_decl (decl); if (! was_abstract) set_decl_abstract_flags (decl, 0); So, if the decl was already abstract, it doesn't reset anything. But, unfortunately, the set_decl_abstract_flags call is recursive, and not all the vars in there necessary have DECL_ABSTRACT_P flag already set. Thus, I think either we should make sure that when the C++ FE sets DECL_ABSTRACT_P flag on something, it is always set on all the contained decls too (but how to ensure this if we e.g. further decls are added in various passes to those functions?), or we should change dwarf2out.c to reset it always to the previous state, rather than sometimes clearing it (despite it might be set already before) and sometimes setting it and not clearing it afterwards. For the latter, guess we could just add a vec<tree> into which we'd push the decls on which we set the flag, and reversion would be performed by walking the vector and clearing DECL_ABSTRACT_P flags. I guess I'll try to implement the dwarf2out.c change.
next prev parent reply other threads:[~2015-02-05 12:00 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-04 17:15 [Bug middle-end/64937] New: " burnus at gcc dot gnu.org 2015-02-04 17:56 ` [Bug middle-end/64937] " burnus at gcc dot gnu.org 2015-02-04 21:11 ` jakub at gcc dot gnu.org 2015-02-05 11:16 ` jakub at gcc dot gnu.org 2015-02-05 12:00 ` jakub at gcc dot gnu.org [this message] 2015-02-06 8:59 ` jakub at gcc dot gnu.org 2015-02-06 18:27 ` jakub at gcc dot gnu.org 2015-02-06 18:32 ` 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-64937-4-1iYE8pXWbf@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).