public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: Guillermo Martinez <guillermo.e.martinez@oracle.com>
To: "libabigail@sourceware.org" <libabigail@sourceware.org>,
	Guillermo Martinez <guillermo.e.martinez@oracle.com>
Subject: Re: [PATCH v2] ctf-reader: Add support to undefined forward declaration types
Date: Mon, 4 Apr 2022 22:51:59 +0000	[thread overview]
Message-ID: <5819626.lOV4Wx5bFT@sali> (raw)
In-Reply-To: <4613524.tdWV9SEqCh@sali>

Hello libabigail team,

Any comment about this patch?

Thanks,
Guillermo

On Thursday, March 31, 2022 3:12:38 PM CDT Guillermo Martinez via Libabigail 
wrote:
> Hello,
> 
> Any comment about this patch?
> 
> Thanks,
> Guillermo
> 
> On Thursday, March 17, 2022 7:30:36 PM CST Guillermo E. Martinez wrote:
> > This is the patch v2 intended to fix undefined forward declarations
> > in ctf reader back-end.
> > 
> > Changes from v1 is update tests/data/Makefile.am to include test
> > input/expected files.
> > 
> > Comments will be appreciated.
> > 
> > Kind Regards,
> > Guillermo
> > 
> > Undefined struct/union forward declaration types are not serialized in
> > abixml representation using `class-decl' node.
> > 
> > For instance, consider:
> >     struct key_type;
> >     typedef void (*key_restrict_link_func_t)(struct key_type *type);
> >  
> >  [...]


  reply	other threads:[~2022-04-04 22:52 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 [this message]
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
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=5819626.lOV4Wx5bFT@sali \
    --to=guillermo.e.martinez@oracle.com \
    --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).