public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/103241] Odd 0 length entries in location lists
Date: Thu, 18 Nov 2021 15:11:36 +0000	[thread overview]
Message-ID: <bug-103241-4-1FusmB9YK0@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 #10 from Will Cohen <wcohen at redhat dot com> ---
That example in comment #5 at [0x0000000000000055, 0x0000000000000055) looks
different than the original example as it is referring to an argument for an
inlined function.  The function mentioned in the original description
static_protections is declared as inlined but is actually generated as an
non-inlined function.

Would https://dwarfstd.org/ShowIssue.php?issue=170427.1  apply in the original
example?  Are there actual multiple views of the parameters in the places with
0-length location list entries?

The first 0-length location list entry for prot would be 

        .byte   0x4
        .uleb128 .LVL615-.LVL615
        .uleb128 .LVL615-.LVL615
        .uleb128 0x1
        .byte   0x55

The second 0-length location list entry in the location list would be:

        .byte   0x4
        .uleb128 .LVL637-.LVL615
        .uleb128 .LHOTE19-.LVL615
        .uleb128 0x1
        .byte   0x52

  parent reply	other threads:[~2021-11-18 15:11 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 [this message]
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

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-1FusmB9YK0@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).