public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/48220] DW_OP_GNU_entry_value/DW_TAG_GNU_call_site_parameter vs register window
Date: Fri, 15 Jul 2011 17:10:00 -0000	[thread overview]
Message-ID: <bug-48220-4-DUxIVjlHU7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48220-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48220

--- Comment #10 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-07-15 17:10:00 UTC ---
Author: ebotcazou
Date: Fri Jul 15 17:09:56 2011
New Revision: 176318

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=176318
Log:
    PR target/48220
    * doc/md.texi (Standard Names): Document window_save.
    * cfgexpand.c (expand_debug_parm_decl): New function extracted from
    expand_debug_expr and expand_debug_source_expr.  If the target has
    a window_save instruction, adjust the ENTRY_VALUE_EXP.
    (expand_debug_expr) <SSA_NAME>: Call expand_debug_parm_decl if the
    SSA_NAME_VAR is a parameter.
    (expand_debug_source_expr) <PARM_DECL>: Call expand_debug_parm_decl.
    * var-tracking.c (parm_reg_t): New type and associated vector type.
    (windowed_parm_regs): New variable.
    (adjust_insn): If the target has a window_save instruction and this
    is the instruction, make its effect on parameter registers explicit.
    (next_non_note_insn_var_location): New function.
    (emit_notes_in_bb): Use it instead of NEXT_INSN throughout.
    (vt_add_function_parameter): If the target has a window_save insn,
    adjust the incoming RTL and record that in windowed_parm_regs.
    (vt_finalize): Free windowed_parm_regs.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/cfgexpand.c
    trunk/gcc/doc/md.texi
    trunk/gcc/var-tracking.c


  parent reply	other threads:[~2011-07-15 17:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 16:35 [Bug debug/48220] New: DW_OP_GNU_entry_value/DW_TAG_GNU_call_site_parameter vs. register window targets jakub at gcc dot gnu.org
2011-03-21 16:56 ` [Bug debug/48220] " jakub at gcc dot gnu.org
2011-03-22 22:04 ` ebotcazou at gcc dot gnu.org
2011-03-23 17:07 ` jakub at gcc dot gnu.org
2011-03-23 17:50 ` ebotcazou at gcc dot gnu.org
2011-03-23 21:13 ` jakub at gcc dot gnu.org
2011-06-02 19:40 ` ebotcazou at gcc dot gnu.org
2011-07-11 16:02 ` [Bug debug/48220] DW_OP_GNU_entry_value/DW_TAG_GNU_call_site_parameter vs register window ebotcazou at gcc dot gnu.org
2011-07-11 16:42 ` jakub at gcc dot gnu.org
2011-07-14 21:49 ` ebotcazou at gcc dot gnu.org
2011-07-15 17:10 ` ebotcazou at gcc dot gnu.org [this message]
2011-08-04 11:52 ` 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-48220-4-DUxIVjlHU7@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: link
Be 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).