public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/43983] var-tracking needlessly throws away location info for SRAed vars Date: Thu, 13 May 2010 10:41:00 -0000 [thread overview] Message-ID: <20100513104120.7205.qmail@sourceware.org> (raw) In-Reply-To: <bug-43983-87@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from jakub at gcc dot gnu dot org 2010-05-13 10:41 ------- Subject: Bug 43983 Author: jakub Date: Thu May 13 10:40:51 2010 New Revision: 159357 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=159357 Log: PR debug/43983 * var-tracking.c (track_expr_p): Allow tracking of variables optimized by SRA. * Makefile.in (dwarf2out.o): Depend on $(TREE_FLOW_H). * tree-sra.c (create_access_replacement): Call unshare_expr before passing expr to SET_DECL_DEBUG_EXPR, and remove any SSA_NAMEs from it. * dwarf2out.c: Include tree-flow.h. (struct var_loc_node): Rename var_loc_note field to loc, add comment. (size_of_loc_descr, output_loc_operands, output_loc_operands_raw): Handle DW_OP_bit_piece. (decl_piece_bitsize, decl_piece_varloc_ptr, decl_piece_node, construct_piece_list, adjust_piece_list): New functions. (add_var_loc_to_decl): Handle SRA optimized variables. Adjust for var_loc_note to loc field renaming. (dw_loc_list_1): For WANT_ADDRESS == 2 prefer DECL_MODE of decl in VAR_LOCATION note. (new_loc_descr_op_bit_piece): New function. (dw_sra_loc_expr): New function. (dw_loc_list): Use it. Don't handle the last range after the loop, handle it inside of the loop. Adjust for var_loc_note to loc field renaming. (add_location_or_const_value_attribute): Only special case single entry loc lists if loc is NOTE_P. Adjust for var_loc_note to loc field renaming. (dwarf2out_var_location): Don't set newloc->var_loc_note and newloc->next here. * gcc.dg/guality/sra-1.c: New test. Added: trunk/gcc/testsuite/gcc.dg/guality/sra-1.c Modified: trunk/gcc/ChangeLog trunk/gcc/Makefile.in trunk/gcc/dwarf2out.c trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-sra.c trunk/gcc/var-tracking.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43983
next prev parent reply other threads:[~2010-05-13 10:41 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-04 15:11 [Bug debug/43983] New: " jakub at gcc dot gnu dot org 2010-05-04 15:13 ` [Bug debug/43983] " jakub at gcc dot gnu dot org 2010-05-05 15:22 ` jakub at gcc dot gnu dot org 2010-05-05 19:07 ` jakub at gcc dot gnu dot org 2010-05-05 20:03 ` rguenth at gcc dot gnu dot org 2010-05-06 8:45 ` jakub at gcc dot gnu dot org 2010-05-13 10:41 ` jakub at gcc dot gnu dot org [this message] 2010-05-13 10:53 ` jakub at gcc dot gnu dot 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=20100513104120.7205.qmail@sourceware.org \ --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).