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 16:00:55 +0000 [thread overview]
Message-ID: <bug-103241-4-DiDQb59NVx@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 #12 from Will Cohen <wcohen at redhat dot com> ---
What is the "-dA" option?
What are the .LVUS* labels referencing in the generated set_memory.s referring
to? They are paired up with the .LLST* labels. From the earlier set_memory.s
that appears to be associated with prot parameter:
.LVUS627:
.uleb128 0
.uleb128 .LVU2887
.uleb128 .LVU2887
.uleb128 .LVU2895
.uleb128 .LVU2910
.uleb128 .LVU2939
.uleb128 .LVU2946
.uleb128 .LVU2974
.uleb128 .LVU2983
.uleb128 .LVU2987
.uleb128 .LVU2987
.uleb128 .LVU3000
.uleb128 .LVU3000
.uleb128 .LVU3004
.uleb128 .LVU3004
.uleb128 .LVU3016
.uleb128 .LVU3016
.uleb128 0
.uleb128 0
.uleb128 .LVU3027
.uleb128 .LVU3029
.uleb128 .LVU3036
.uleb128 .LVU3036
.uleb128 0
This looks to be the location list for prot variable from set_memory.s earlier
attached to this bug:
.LLST627:
.byte 0x6
.quad .LVL615
.byte 0x4
.uleb128 .LVL615-.LVL615
.uleb128 .LVL615-.LVL615
.uleb128 0x1
.byte 0x55
.byte 0x4
.uleb128 .LVL615-.LVL615
.uleb128 .LVL616-.LVL615
.uleb128 0x3
.byte 0x55
.byte 0x93
.uleb128 0x8
.byte 0x4
.uleb128 .LVL619-.LVL615
.uleb128 .LVL623-.LVL615
.uleb128 0x1
.byte 0x55
.byte 0x4
.uleb128 .LVL625-.LVL615
.uleb128 .LVL628-.LVL615
.uleb128 0x1
.byte 0x53
.byte 0x4
.uleb128 .LVL630-.LVL615
.uleb128 .LVL631-.LVL615
.uleb128 0x1
.byte 0x55
.byte 0x4
.uleb128 .LVL631-.LVL615
.uleb128 .LVL634-.LVL615
.uleb128 0x3
.byte 0x53
.byte 0x93
.uleb128 0x8
.byte 0x4
.uleb128 .LVL634-.LVL615
.uleb128 .LVL634-.LVL615
.uleb128 0x3
.byte 0x53
.byte 0x93
.uleb128 0x8
.byte 0x4
.uleb128 .LVL634-.LVL615
.uleb128 .LVL637-.LVL615
.uleb128 0x1
.byte 0x53
.byte 0x4
.uleb128 .LVL637-.LVL615
.uleb128 .LHOTE19-.LVL615
.uleb128 0x3
.byte 0x53
.byte 0x93
.uleb128 0x8
.byte 0x6
.quad .LFSB4151
.byte 0x4
.uleb128 .LFSB4151-.LFSB4151
.uleb128 .LVL642-.LFSB4151
.uleb128 0x3
.byte 0x53
.byte 0x93
.uleb128 0x8
.byte 0x4
.uleb128 .LVL644-.LFSB4151
.uleb128 .LVL646-.LFSB4151
.uleb128 0x1
.byte 0x53
.byte 0x4
.uleb128 .LVL646-.LFSB4151
.uleb128 .LFE4151-.LFSB4151
.uleb128 0x3
.byte 0x53
.byte 0x93
.uleb128 0x8
.byte 0
next prev parent reply other threads:[~2021-11-18 16:00 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 [this message]
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-DiDQb59NVx@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).