From: Giuliano Procida <gprocida@google.com>
To: Mark Wielaard <mark@klomp.org>
Cc: libabigail@sourceware.org, dodji@seketeli.org,
kernel-team@android.com, maennich@google.com
Subject: Re: [PATCH] DWARF reader: use size_t for DWARF expression length
Date: Tue, 18 Jan 2022 09:57:49 +0000 [thread overview]
Message-ID: <CAGvU0H=1RxvMFPBVmeGw51N0VNtwg5MwiZhxnLvUqK1+jNHYQg@mail.gmail.com> (raw)
In-Reply-To: <YeaN94a4DNyiDbM6@wildebeest.org>
The latest merged commit doesn't have the extra fixes you mentioned.
I'm happy to replicate your work, but I risk leaving something out again.
Let me know,
Giuliano.
On Tue, 18 Jan 2022 at 09:52, Mark Wielaard <mark@klomp.org> wrote:
>
> Hi Giuliano,
>
> On Mon, Jan 17, 2022 at 02:51:15PM +0000, Giuliano Procida wrote:
> > A recent change broke 32-bit builds due to an implicit assumption that
> > size_t == uint64_t. This appears in the elfutils dwarf_getlocation*
> > functions' types.
> >
> > This commit updates callers and other functions to use size_t
> > consistently for such expression lengths and indexes.
> >
> > * src/abg-dwarf-reader.cc (die_location_expr): Change expr_len
> > argument type to size_t*.
> > (op_manipulates_stack): Change expr_len and index argument
> > types to size_t; change next_index argument type to size_t&.
> > (eval_last_constant_dwarf_sub_expr): Change expr_len argument
> > and local variables index and next_index types to size_t.
> > (die_member_offset): Change local variable expr_len type to
> > size_t.
> > (die_location_address): Likewise.
> > (die_virtual_function_index): Likewise.
>
> I also needed to change the len and index arguments of
> eval_last_constant_dwarf_sub_expr, op_pushes_constant_value,
> op_pushes_non_constant_value, op_is_arith_logic and
> op_is_control_flow.
>
> See attached.
>
> Cheers,
>
> Mark
next prev parent reply other threads:[~2022-01-18 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 14:51 Giuliano Procida
2022-01-18 9:52 ` Mark Wielaard
2022-01-18 9:57 ` Giuliano Procida [this message]
2022-01-18 12:03 ` Dodji Seketeli
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='CAGvU0H=1RxvMFPBVmeGw51N0VNtwg5MwiZhxnLvUqK1+jNHYQg@mail.gmail.com' \
--to=gprocida@google.com \
--cc=dodji@seketeli.org \
--cc=kernel-team@android.com \
--cc=libabigail@sourceware.org \
--cc=maennich@google.com \
--cc=mark@klomp.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).