From: Dodji Seketeli <dodji@seketeli.org>
To: "Guillermo E. Martinez via Libabigail" <libabigail@sourceware.org>
Subject: Re: [PATCH v3] ctf-reader: shows incomplete summary changes
Date: Fri, 13 May 2022 14:09:30 +0200 [thread overview]
Message-ID: <87o801vdl1.fsf@seketeli.org> (raw)
In-Reply-To: <20220507014305.1416381-1-guillermo.e.martinez@oracle.com> (Guillermo E. Martinez via Libabigail's message of "Fri, 6 May 2022 20:43:05 -0500")
> * src/abg-ctf-reader.cc (read_context::exported_decls_builder_):
> Add new data member.
> (read_context::exported_decls_builder): Add new get/set member functions.
> (read_context::maybe_add_{fn,var}_to_exported_decls): Likewise.
> (read_context::initialize): Initialize exported_decls_builder_ member.
> (read_context::build_ir_node_for_variadic_parameter_type): Add new function.
> (read_context::process_ctf_function_type): Add additional code to handle
> function's variadic parameter.
> (read_context::process_ctf_archive): Rename variable for clarity
> from `ctf_var_type' to `ctf_sym_type', using new member functions
> `maybe_add_{fn,var}_to_exported_decls'.
> (read_context::read_corpus): Set `exported_decls_builder'.
> * tests/test-read-common.cc (test_task::run_abidw): Fix error message.
> * tests/data/test-read-ctf/test-PR26568-1.o.abi: Adjust test case.
> * tests/data/test-read-ctf/test-PR26568-2.o.abi: Likewise.
> * tests/data/test-read-ctf/test-anonymous-fields.o.abi Likewise.
> * tests/data/test-read-ctf/test5.o.abi: Likewise.
> * tests/data/test-read-ctf/test7.o.abi: Likewise.
Applied to master, thanks!
[...]
Cheers,
--
Dodji
prev parent reply other threads:[~2022-05-16 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 16:38 [PATCH] " Guillermo E. Martinez
2022-05-02 15:38 ` Dodji Seketeli
2022-05-02 22:50 ` Guillermo E. Martinez
2022-05-02 22:46 ` [PATCH v2] " Guillermo E. Martinez
2022-05-07 1:43 ` [PATCH v3] " Guillermo E. Martinez
2022-05-13 12:09 ` Dodji Seketeli [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=87o801vdl1.fsf@seketeli.org \
--to=dodji@seketeli.org \
--cc=libabigail@sourceware.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).