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/49382] -O2 -g: DW_AT_location at the very first PC is already modified
Date: Wed, 15 Jun 2011 09:57:00 -0000	[thread overview]
Message-ID: <bug-49382-4-YzKUDABYku@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49382-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-06-15 09:56:36 UTC ---
Author: jakub
Date: Wed Jun 15 09:56:33 2011
New Revision: 175076

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=175076
Log:
    PR debug/49382
    * dwarf2out.c (dw_loc_list_node): Add force field.
    (add_var_loc_to_decl): For PARM_DECL, attempt to keep
    the incoming location in the list, even if it is modified
    before first real insn.
    (output_loc_list): Emit empty ranges with force flag set.
    (dw_loc_list): If first range of a PARM_DECL is empty,
    set force flag.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/dwarf2out.c


  parent reply	other threads:[~2011-06-15  9:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-12 11:15 [Bug debug/49382] New: " jan.kratochvil at redhat dot com
2011-06-13 19:32 ` [Bug debug/49382] " jakub at gcc dot gnu.org
2011-06-13 19:37 ` jakub at gcc dot gnu.org
2011-06-13 19:53 ` jan.kratochvil at redhat dot com
2011-06-14 10:30 ` jakub at gcc dot gnu.org
2011-06-14 12:51 ` jan.kratochvil at redhat dot com
2011-06-14 12:55 ` jakub at gcc dot gnu.org
2011-06-15  9:57 ` jakub at gcc dot gnu.org [this message]
2011-06-15  9:59 ` 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-49382-4-YzKUDABYku@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).