From: Dodji Seketeli <dodji@seketeli.org>
To: "Guillermo E. Martinez via Libabigail" <libabigail@sourceware.org>
Subject: Re: [PATCH v2] ctf-reader: Add support to undefined forward declaration types
Date: Fri, 29 Apr 2022 12:57:27 +0200 [thread overview]
Message-ID: <87wnf8f97s.fsf@seketeli.org> (raw)
In-Reply-To: <20220318013036.2306102-1-guillermo.e.martinez@oracle.com> (Guillermo E. Martinez via Libabigail's message of "Thu, 17 Mar 2022 19:30:36 -0600")
Hello,
"Guillermo E. Martinez via Libabigail" <libabigail@sourceware.org> a
écrit:
[...]
> +static type_base_sptr
> +process_ctf_forward_type(read_context *ctxt,
> + corpus_sptr corp,
> + translation_unit_sptr tunit,
> + ctf_dict_t *ctf_dictionary,
> + ctf_id_t ctf_type)
This function lacks a doxgen comment. I have added it.
Also, the 'corp' parameter is not used in the body of the function. So
I have removed it.
[...]
> /// Build and return a struct type libabigail IR.
> ///
> /// @param ctxt the read context.
> @@ -813,6 +860,12 @@ process_ctf_type(read_context *ctxt,
> result = is_type(struct_decl);
> break;
> }
> + case CTF_K_FORWARD:
> + {
> + result = process_ctf_forward_type(ctxt, corp, tunit, ctf_dictionary,
> + ctf_type);
I have updated this call to remove the "corp" parameter as it's not
there anymore.
> + }
> + break;
> case CTF_K_UNION:
> {
[...]
> * src/abg-ctf-reader.cc (process_ctf_forward_type): New
> function.
> (process_ctf_type): New CTF_K_FORWARD case.
> * tests/data/test-read-ctf/test-forward-undefine-type-decl.c:
> New testcase.
> * tests/data/test-read-ctf/test-forward-undefine-type-decl.abi:
> New expected result.
> * tests/data/test-read-ctf/test-forward-undefine-type-decl.o
> New test input.
> * tests/test-read-ctf.cc: Add new testcase to test harness.
> * tests/data/Makefile.am: Add new test input files to test harness.
>
> Signed-off-by: Guillermo E. Martinez <guillermo.e.martinez@oracle.com>
Applying this to master, thanks!
Cheers,
--
Dodji
next prev parent reply other threads:[~2022-04-29 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 4:14 [PATCH] " Guillermo E. Martinez
2022-03-17 4:49 ` Guillermo Martinez
2022-03-18 1:30 ` [PATCH v2] " Guillermo E. Martinez
2022-03-31 21:12 ` Guillermo Martinez
2022-04-04 22:51 ` Guillermo Martinez
2022-04-25 18:37 ` Guillermo E. Martinez
2022-04-25 19:45 ` Ben Woodard
2022-04-25 20:24 ` Guillermo E. Martinez
2022-04-29 10:57 ` Dodji Seketeli [this message]
2022-04-29 13:50 ` Guillermo E. Martinez
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=87wnf8f97s.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).