From: Tom Tromey <tromey@adacore.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Allow dynamic DW_AT_bit_stride on DW_TAG_array_type
Date: Mon, 06 Apr 2026 10:36:11 -0600 [thread overview]
Message-ID: <875x64yrk4.fsf@tromey.com> (raw)
In-Reply-To: <192dd160-d97c-4ba3-8917-a6e1bbaba6b0@redhat.com> (Keith Seitz's message of "Fri, 3 Apr 2026 12:56:21 -0700")
>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
Keith> I think this is relatively straightforward, and aside from a few
Keith> minor observations, LGTM.
Thanks.
Keith> I see the above code is duplicated below -- is it worth the bother to
Keith> separate into a function? Not an action item. Just a question.
I think the two functions can probably be merged.
I'll take a look at that separately.
>> /* If the stride is seen and used, byte_stride_prop will be
>> non-NULL. In this case stride_storage will be used to store the
>> data locally. */
Keith> I think the above comment should now refer to `stride_prop' instead of
Keith> `byte_stride_prop'.
Yeah, fixed.
>> + IS_BYTE_STRIDE is true, then this is a byte stride; when false this
>> + is a bit stride. This stride property is added to the resulting
>> + array type as a DYN_PROP_BYTE_STRIDE or a DYN_PROP_BIT_SIZE, as
Keith> Should this refer to DYN_PROP_BIT_STRIDE?
Yes, thank you.
I'm going to check this in now.
Tom
prev parent reply other threads:[~2026-04-06 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 12:53 Tom Tromey
2026-04-03 19:56 ` Keith Seitz
2026-04-06 16:36 ` Tom Tromey [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=875x64yrk4.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
/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