From: "Gao, Liming" <liming.gao@intel.com>
To: M1cha <sigmaepsilon92@gmail.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH v2 0/3] fix GCC optimizations and warnings for SetJump/LongJump
Date: Fri, 29 Dec 2017 15:21:01 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E19B34D@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20171222191640.5313-1-sigmaepsilon92@gmail.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
> -----Original Message-----
> From: M1cha [mailto:sigmaepsilon92@gmail.com]
> Sent: Saturday, December 23, 2017 3:17 AM
> To: edk2-devel@lists.01.org
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>; Kinney, Michael D <michael.d.kinney@intel.com>; Gao, Liming
> <liming.gao@intel.com>
> Subject: [edk2] [PATCH v2 0/3] fix GCC optimizations and warnings for SetJump/LongJump
>
> I've already discussed this in past but never actually sent proper
> patches for some reason.
>
> This patch series is about fixing problems with these functions when
> using GCC.
>
> V2:
> * add attributes to C-files too
> * remove useless condition in RETURNS_TWICE macro
>
> M1cha (3):
> MdePkg: add RETURNS_TWICE attribute
> MdePkg/BaseLib: add attribute 'RETURNS_TWICE' to SetJump
> MdePkg: add NORETURN attribute to LongJump and InternalLongJump
>
> MdePkg/Include/Base.h | 8 ++++++++
> MdePkg/Include/Library/BaseLib.h | 2 ++
> MdePkg/Library/BaseLib/BaseLibInternals.h | 1 +
> MdePkg/Library/BaseLib/Ebc/SetJumpLongJump.c | 2 ++
> MdePkg/Library/BaseLib/Ia32/LongJump.c | 1 +
> MdePkg/Library/BaseLib/Ia32/SetJump.c | 1 +
> MdePkg/Library/BaseLib/LongJump.c | 1 +
> 7 files changed, 16 insertions(+)
>
> --
> 2.15.1
prev parent reply other threads:[~2017-12-29 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 19:16 [PATCH v2 0/3] fix GCC optimizations and warnings for SetJump/LongJump M1cha
2017-12-29 15:21 ` Gao, Liming [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-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=4A89E2EF3DFEDB4C8BFDE51014F606A14E19B34D@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