public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/103241] Odd 0 length entries in location lists Date: Fri, 19 Nov 2021 10:18:11 +0000 [thread overview] Message-ID: <bug-103241-4-9oc8MnSWc8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103241-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103241 --- Comment #14 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- Hi, Will, Jakub, Martin, There's nothing particularly unusual about apparently empty ranges, especially when views are enabled, since the very point of location views is to enable multiple states to be distinguished at the same PC. It is a little odd that an additional location entry gets emitted for prot at function entry. I suppose inspection of gimple dumps will show some SSA assignment apparently setting some prot version, and that we end up outputting a new entry for it. The difference between the two locations, one without and the other with DW_OP_piece, suggests that some internal state change was perceived between one view and the other; it might be something about (do-nothing) promotions between the argument bindings for the prototype and the body. We might be able to get rid of the restatement of the binding with some more effort.
prev parent reply other threads:[~2021-11-19 10:18 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-15 1:17 [Bug debug/103241] New: " wcohen at redhat dot com 2021-11-16 14:11 ` [Bug debug/103241] " jakub at gcc dot gnu.org 2021-11-16 14:46 ` wcohen at redhat dot com 2021-11-16 14:51 ` wcohen at redhat dot com 2021-11-16 15:11 ` marxin at gcc dot gnu.org 2021-11-16 15:24 ` wcohen at redhat dot com 2021-11-16 15:39 ` marxin at gcc dot gnu.org 2021-11-16 16:18 ` wcohen at redhat dot com 2021-11-18 10:24 ` marxin at gcc dot gnu.org 2021-11-18 10:35 ` jakub at gcc dot gnu.org 2021-11-18 15:11 ` wcohen at redhat dot com 2021-11-18 15:23 ` jakub at gcc dot gnu.org 2021-11-18 16:00 ` wcohen at redhat dot com 2021-11-18 16:18 ` jakub at gcc dot gnu.org 2021-11-19 10:18 ` aoliva at gcc dot gnu.org [this message]
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-103241-4-9oc8MnSWc8@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).