public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "Xiaole He" <hexiaole1994@126.com>
To: "Dodji Seketeli" <dodji@seketeli.org>
Cc: "Xiaole He via Libabigail" <libabigail@sourceware.org>,
	 "Xiaole He" <hexiaole@kylinos.cn>
Subject: Re:Re: [PATCH] abg-reader: optimize if construction
Date: Tue, 18 Oct 2022 11:25:12 +0800 (CST)	[thread overview]
Message-ID: <3b841723.1904.183e91fb547.Coremail.hexiaole1994@126.com> (raw)
In-Reply-To: <87leper0z8.fsf@seketeli.org>

[-- Attachment #1: Type: text/plain, Size: 2461 bytes --]

Thank you for reviewing.

















At 2022-10-17 22:14:35, "Dodji Seketeli" <dodji@seketeli.org> wrote:
>Hello Xiaole,
>
>Xiaole He via Libabigail <libabigail@sourceware.org> a écrit:
>
>> In 'build_enum_type_decl' function of 'src/abg-reader.cc', the
>> 'for loop' walk through all the child nodes of the '<enum-decl>' for
>> seeking '<underlying-type>' and '<enumerator>':
>>
>> /* original src/abg-reader.cc begin */
>> static enum_type_decl_sptr
>> build_enum_type_decl(read_context& ctxt,
>>              const xmlNodePtr node,
>>              bool add_to_current_scope)
>> {
>>   ...
>>   for (xmlNodePtr n = xmlFirstElementChild(node);
>>        n;
>>        n = xmlNextElementSibling(n))
>>     {
>>       if (xmlStrEqual(n->name, BAD_CAST("underlying-type")))
>>       {
>>          ...
>>       }
>>
>>       if (xmlStrEqual(n->name, BAD_CAST("enumerator")))
>>       {
>>          ...
>>       }
>>     }
>>   ...
>> }
>> /* original src/abg-reader.cc end */
>>
>> Here uses 2 separate 'if' statements for seeking, that is, for any
>> child node of the '<enum-decl>', there involves 2 'if' comparations.
>> Because the child node of the '<enum-decl>' is either
>> '<underlying-type>' or '<enumerator>', there would be a slight
>> optimization when use 'if-else if' construction instead, like below:
>>
>> /* optimized src/abg-reader.cc begin */
>> for (xmlNodePtr n = xmlFirstElementChild(node);
>>      n;
>>      n = xmlNextElementSibling(n))
>>   {
>>     if (xmlStrEqual(n->name, BAD_CAST("underlying-type")))
>>     {
>>        ...
>>     }
>>     else if (xmlStrEqual(n->name, BAD_CAST("enumerator")))
>>     {
>>        ...
>>     }
>>   }
>> /* optimized src/abg-reader.cc end */
>>
>> Supposing there has the test case:
>>
>> /* test case begin */
>> <abi-instr version='1.0'>
>>   <enum-decl name='E' filepath='../../abitests/test-enum0-v0.cc' line='1' column='6' id='type-id-2'>
>>     <underlying-type type-id='type-id-1'/>
>>     <enumerator name='e0' value='0'/>
>>     <enumerator name='e2' value='1'/>
>>   </enum-decl>
>> </abi-instr>
>> /* test case end */
>>
>> When parsing the '<underlying-type>' xml tag, for the original
>> 'src/abg-reader.cc', there involves 2 'if' comparations. But involves
>> only 1 'if' comparation for the optimized 'src/abg-reader.cc'.
>>
>> Signed-off-by: Xiaole He <hexiaole@kylinos.cn>
>> Tested-by: Xiaole He <hexiaole@kylinos.cn>
>
>Applied to the master branch.
>
>Cheers,
>
>-- 
>		Dodji

      reply	other threads:[~2022-10-18  3:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16  6:47 Xiaole He
2022-10-17 14:14 ` Dodji Seketeli
2022-10-18  3:25   ` Xiaole He [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=3b841723.1904.183e91fb547.Coremail.hexiaole1994@126.com \
    --to=hexiaole1994@126.com \
    --cc=dodji@seketeli.org \
    --cc=hexiaole@kylinos.cn \
    --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).