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 debug/54970] Missing DW_OP_GNU_implicit_pointer in debuginfo Date: Fri, 26 Oct 2012 19:20:00 -0000 [thread overview] Message-ID: <bug-54970-4-5J7mw7Oh0r@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54970-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54970 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-10-26 19:19:30 UTC --- Author: jakub Date: Fri Oct 26 19:19:25 2012 New Revision: 192860 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=192860 Log: PR debug/54970 * cfgexpand.c (expand_debug_expr): Expand &MEM_REF[&var, n] as DEBUG_IMPLICIT_PTR + n if &var expands to DEBUG_IMPLICIT_PTR. * tree-sra.c (create_access_replacement): Allow also MEM_REFs with ADDR_EXPR first operand in DECL_DEBUG_EXPR expressions. * var-tracking.c (track_expr_p): Handle MEM_REFs in DECL_DEBUG_EXPR expressions. * dwarf2out.c (add_var_loc_to_decl): Likewise. PR debug/54971 * gcc.dg/guality/pr54970.c: New test. Added: trunk/gcc/testsuite/gcc.dg/guality/pr54970.c Modified: trunk/gcc/ChangeLog trunk/gcc/cfgexpand.c trunk/gcc/dwarf2out.c trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-sra.c trunk/gcc/var-tracking.c
next prev parent reply other threads:[~2012-10-26 19:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-18 8:45 [Bug debug/54970] New: " jakub at gcc dot gnu.org 2012-10-18 8:46 ` [Bug debug/54970] " jakub at gcc dot gnu.org 2012-10-18 8:55 ` jakub at gcc dot gnu.org 2012-10-18 9:27 ` jakub at gcc dot gnu.org 2012-10-26 19:20 ` jakub at gcc dot gnu.org [this message] 2012-11-05 14:37 ` jakub at gcc dot gnu.org 2012-12-04 13:17 ` jakub at gcc dot gnu.org 2013-03-12 17:09 ` steven at gcc dot gnu.org 2013-03-12 17:51 ` jakub at gcc dot gnu.org 2013-03-12 18:55 ` steven 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-54970-4-5J7mw7Oh0r@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).