From: M1cha <sigmaepsilon92@gmail.com>
To: edk2-devel@lists.01.org
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <liming.gao@intel.com>
Subject: [PATCH v2 0/3] fix GCC optimizations and warnings for SetJump/LongJump
Date: Fri, 22 Dec 2017 20:16:40 +0100 [thread overview]
Message-ID: <20171222191640.5313-1-sigmaepsilon92@gmail.com> (raw)
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
next reply other threads:[~2017-12-22 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 19:16 M1cha [this message]
2017-12-29 15:21 ` [PATCH v2 0/3] fix GCC optimizations and warnings for SetJump/LongJump Gao, Liming
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=20171222191640.5313-1-sigmaepsilon92@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