public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/54971] SRA pessimizes debug info by not creating debug stmts for fields without replacements Date: Mon, 22 Oct 2012 14:56:00 -0000 [thread overview] Message-ID: <bug-54971-4-x6UqkSP02m@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54971-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54971 --- Comment #4 from Martin Jambor <jamborm at gcc dot gnu.org> 2012-10-22 14:55:35 UTC --- Unfortunately, the patch causes -fcompare-debug issues. The problem is that with it we create some declarations only when producing debug info which can affect UIDs which then changes other stuff. I tried producing DEBUG_EXPR_DECLs instead of regular decls but SET_DECL_DEBUG_EXPR does not accept DEBUG_EXPR_DECLs as an argument, it insists on VAR_DECLs. I tried removing the checking restriction but it turned out that using DEBUG_EXPR_DECLs does not fix the testcase. Jakub, do you think that can be fixed or are DEBUG_EXPR_DECLs a completely different thing that principally canno be used for this purpose? Another alternative is to build full-fledged replacement decls even when not producing debug info, even though we'd never use it. That seems slightly wasteful but can be done. (Some reworking of replacement building would be probably required so that we get rid of lazy replacement building which is no longer necessary).
next prev parent reply other threads:[~2012-10-22 14:56 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-18 9:48 [Bug debug/54971] New: " jakub at gcc dot gnu.org 2012-10-18 13:35 ` [Bug debug/54971] " jakub at gcc dot gnu.org 2012-10-18 17:37 ` jamborm at gcc dot gnu.org 2012-10-19 16:01 ` jamborm at gcc dot gnu.org 2012-10-22 14:56 ` jamborm at gcc dot gnu.org [this message] 2012-10-22 15:09 ` jakub at gcc dot gnu.org 2012-10-22 15:14 ` jamborm at gcc dot gnu.org 2012-10-22 16:19 ` jakub at gcc dot gnu.org 2012-10-22 20:00 ` jakub at gcc dot gnu.org 2012-10-26 9:33 ` jamborm at gcc dot gnu.org 2012-10-26 16:13 ` jamborm at gcc dot gnu.org 2012-10-26 19:20 ` jakub at gcc dot gnu.org 2012-10-27 17:30 ` jakub at gcc dot gnu.org 2012-10-29 8:36 ` jakub at gcc dot gnu.org 2012-10-29 15:20 ` rguenth at gcc dot gnu.org 2012-10-29 15:26 ` jakub at gcc dot gnu.org 2012-11-05 14:37 ` jakub at gcc dot gnu.org 2013-01-04 14:41 ` jamborm 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-54971-4-x6UqkSP02m@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).