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: Mon, 13 Jun 2011 19:32:00 -0000 [thread overview] Message-ID: <bug-49382-4-EifXj5fWfY@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aoliva at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-06-13 19:27:51 UTC --- I'm afraid that without statement frontiers there is nothing that can be done about it, and it is a question whether to call it a bug at all. The side effect (which has been optimized away) just happens so early that there are no real insns left before it. x_2 = x_1(D); # DEBUG x => x_1(D) + 1 clobber (x_2); i = 1; return; simply becomes: # DEBUG x => x_1(D) + 1 clobber (x_1(D)); i = 1; return; Claiming the side effect happens after the call wouldn't be correct, the side effect really happens before the call and the call is the first insn. With statement frontiers you could step through the zero-length insn between start of the function (where x would be live in DW_OP_reg5) to the location before the first call (where x would be already DW_OP_breg5 <1> DW_OP_stack_value).
next prev parent reply other threads:[~2011-06-13 19:32 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 ` jakub at gcc dot gnu.org [this message] 2011-06-13 19:37 ` [Bug debug/49382] " 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 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-EifXj5fWfY@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).