public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>,
	Brijesh Singh <brijesh.singh@amd.com>,
	 Jordan Justen <jordan.l.justen@intel.com>
Subject: Re: [PATCH 2/2] OvmfPkg/PlatformPei: sync AmdSevInitialize() definition with declaration
Date: Wed, 7 Feb 2018 10:47:14 +0100	[thread overview]
Message-ID: <CAKv+Gu_dV5p+G0mE34bFUOzdfma2m8VwH+knJa3BcHqN5zyK1g@mail.gmail.com> (raw)
In-Reply-To: <20180206220115.29193-3-lersek@redhat.com>

On 6 February 2018 at 23:01, Laszlo Ersek <lersek@redhat.com> wrote:
> "Platform.h" declares the AmdSevInitialize() function without EFIAPI, but
> the definition in "AmdSev.c" includes EFIAPI.
>
> GCC toolchains without LTO do not catch this error because "AmdSev.c" does
> not include "Platform.h"; i.e. the declaration used by callers such as
> "Platform.c" is not actually matched against the function definition at
> build time.
>
> With LTO enabled, the mismatch is found -- however, as a warning only, due
> to commit f8d0b9662993 ("BaseTools GCC5: disable warnings-as-errors for
> now", 2016-08-03).
>
> Include the header in the C file (which turns the issue into a hard build
> error on all GCC toolchains), plus sync the declaration from the header
> file to the C file.
>
> There's been no functional breakage because AmdSevInitialize() takes no
> parameters.
>
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Cc: Brijesh Singh <brijesh.singh@amd.com>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>

Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>

> ---
>  OvmfPkg/PlatformPei/AmdSev.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/OvmfPkg/PlatformPei/AmdSev.c b/OvmfPkg/PlatformPei/AmdSev.c
> index 1539e5b5cdce..ad31b69fb032 100644
> --- a/OvmfPkg/PlatformPei/AmdSev.c
> +++ b/OvmfPkg/PlatformPei/AmdSev.c
> @@ -23,6 +23,8 @@
>  #include <Register/Amd/Cpuid.h>
>  #include <Library/MemEncryptSevLib.h>
>
> +#include "Platform.h"
> +
>  /**
>
>    Function checks if SEV support is available, if present then it sets
> @@ -30,7 +32,6 @@
>
>    **/
>  VOID
> -EFIAPI
>  AmdSevInitialize (
>    VOID
>    )
> --
> 2.14.1.3.gb7cf6e02401b
>


  parent reply	other threads:[~2018-02-07  9:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180206220115.29193-1-lersek@redhat.com>
     [not found] ` <20180206220115.29193-3-lersek@redhat.com>
2018-02-06 22:11   ` [PATCH 2/2] OvmfPkg/PlatformPei: sync AmdSevInitialize() definition with declaration Brijesh Singh
2018-02-07  9:47   ` Ard Biesheuvel [this message]
2018-02-06 22:56 ` [PATCH 0/2] sync some function definitions with their declarations Carsey, Jaben

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=CAKv+Gu_dV5p+G0mE34bFUOzdfma2m8VwH+knJa3BcHqN5zyK1g@mail.gmail.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