public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
	Zenith432 <zenith432@users.sourceforge.net>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH] MdePkg: correct and clarify documentation of VA_LIST in Base.h
Date: Tue, 12 Dec 2017 15:01:35 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E191187@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <147f3c39-cfc4-a0ad-44c8-a58487624c7f@redhat.com>

Laszlo:
  Thanks!

Reviewed-by: Liming Gao <liming.gao@intel.com>

> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Laszlo Ersek
> Sent: Tuesday, December 12, 2017 6:39 PM
> To: Zenith432 <zenith432@users.sourceforge.net>; edk2-devel@lists.01.org
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Gao, Liming <liming.gao@intel.com>
> Subject: Re: [edk2] [PATCH] MdePkg: correct and clarify documentation of VA_LIST in Base.h
> 
> On 12/12/17 11:24, Zenith432 wrote:
> > Below is an amended patch.
> >
> > I changed the wording in the notes a little to exclude a non-variadic
> > function using VA_START, and to remind that VA_COPY should also be
> > paired with VA_END.
> >
> > Also, if GCC gets its VA_COPY repaired, documentation may change to
> > allow to using VA_COPY
> > inside non-EFIAPI as well.
> > ---
> >
> > This is to resolve bug 457.
> > https://bugzilla.tianocore.org/show_bug.cgi?id=457
> >
> > Contributed-under: TianoCore Contribution Agreement 1.1
> > Signed-off-by: Zenith432 <zenith432 at users.sourceforge.net>
> > ---
> >  MdePkg/Include/Base.h | 25 +++++++++++++++++--------
> >  1 file changed, 17 insertions(+), 8 deletions(-)
> >
> > diff --git a/MdePkg/Include/Base.h b/MdePkg/Include/Base.h
> > index 02140a5a..4fd5161f 100644
> > --- a/MdePkg/Include/Base.h
> > +++ b/MdePkg/Include/Base.h
> > @@ -552,21 +552,24 @@ struct _LIST_ENTRY {
> >  #define  BASE_8EB    0x8000000000000000ULL
> >
> >  //
> > -//  Support for variable length argument lists using the ANSI standard.
> > +//  Support for variable argument lists in freestanding edk2 modules.
> >  //
> > -//  Since we are using the ANSI standard we used the standard naming and
> > -//  did not follow the coding convention
> > +//  For modules that use the ISO C library interfaces for variable
> > +//  argument lists, refer to "StdLib/Include/stdarg.h".
> >  //
> >  //  VA_LIST  - typedef for argument list.
> >  //  VA_START (VA_LIST Marker, argument before the ...) - Init Marker
> > for use.
> >  //  VA_END (VA_LIST Marker) - Clear Marker
> > -//  VA_ARG (VA_LIST Marker, var arg size) - Use Marker to get an
> > argument from
> > -//    the ... list. You must know the size and pass it in this macro.
> > +//  VA_ARG (VA_LIST Marker, var arg type) - Use Marker to get an
> > argument from
> > +//    the ... list. You must know the type and pass it in this macro.
> > Type
> > +//    must be compatible with the type of the actual next argument (as
> > promoted
> > +//    according to the default argument promotions.)
> >  //  VA_COPY (VA_LIST Dest, VA_LIST Start) - Initialize Dest as a copy
> > of Start.
> >  //
> > -//  example:
> > +//  Example:
> >  //
> >  //  UINTN
> > +//  EFIAPI
> >  //  ExampleVarArg (
> >  //    IN UINTN  NumberOfArgs,
> >  //    ...
> > @@ -582,15 +585,21 @@ struct _LIST_ENTRY {
> >  //    VA_START (Marker, NumberOfArgs);
> >  //    for (Index = 0, Result = 0; Index < NumberOfArgs; Index++) {
> >  //      //
> > -//      // The ... list is a series of UINTN values, so average them up.
> > +//      // The ... list is a series of UINTN values, so sum them up.
> >  //      //
> >  //      Result += VA_ARG (Marker, UINTN);
> >  //    }
> >  //
> >  //    VA_END (Marker);
> > -//    return Result
> > +//    return Result;
> >  //  }
> >  //
> > +//  Notes:
> > +//  - Functions that call VA_START() / VA_END() must have a variable
> > +//    argument list and must be declared EFIAPI.
> > +//  - Functions that call VA_COPY() / VA_END() must be declared EFIAPI.
> > +//  - Functions that only use VA_LIST and VA_ARG() need not be EFIAPI.
> > +//
> >
> >  /**
> >    Return the size of argument that has been aligned to sizeof (UINTN).
> 
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> 
> (Liming, I can help with applying this patch, if you want that.)
> 
> Thanks!
> Laszlo
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel

  reply	other threads:[~2017-12-12 14:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1667068483.2112668.1512898346914.ref@mail.yahoo.com>
2017-12-10  9:32 ` [PATCH] MdePkg: correct and clarify documentation of VA_LIST in Base.h Zenith432
2017-12-10 13:53   ` Gao, Liming
2017-12-10 15:43     ` Zenith432
2017-12-11 14:35       ` Gao, Liming
2017-12-11 14:57         ` Zenith432
2017-12-12  1:32           ` Gao, Liming
2017-12-12  8:36             ` Laszlo Ersek
2017-12-12  9:16   ` Laszlo Ersek
2017-12-12 10:24     ` Zenith432
2017-12-12 10:39       ` Laszlo Ersek
2017-12-12 15:01         ` Gao, Liming [this message]
2017-12-12 17:42           ` Laszlo Ersek

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-list 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=4A89E2EF3DFEDB4C8BFDE51014F606A14E191187@SHSMSX104.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /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