From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH master 2/7] include: zero_page: hide possibly NULL pointer variable from optimizer
Date: Mon, 22 May 2023 07:22:17 +0200 [thread overview]
Message-ID: <20230522052222.1037931-2-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20230522052222.1037931-1-a.fatoum@pengutronix.de>
---
include/zero_page.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/zero_page.h b/include/zero_page.h
index 26a12246f155..a71c0e0b8733 100644
--- a/include/zero_page.h
+++ b/include/zero_page.h
@@ -44,6 +44,8 @@ static inline void *zero_page_memcpy(void *dest, const void *src, size_t count)
{
void *ret;
+ OPTIMIZER_HIDE_VAR(dest);
+
zero_page_access();
ret = memcpy(dest, src, count);
zero_page_faulting();
--
2.39.2
next prev parent reply other threads:[~2023-05-22 5:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 5:22 [PATCH master 1/7] test: self: ramfs: fix unintended macro identifier confusion Ahmad Fatoum
2023-05-22 5:22 ` Ahmad Fatoum [this message]
2023-05-23 6:46 ` [PATCH master 2/7] include: zero_page: hide possibly NULL pointer variable from optimizer Ahmad Fatoum
2023-05-22 5:22 ` [PATCH master 3/7] ARM: configs: temporarily revive vexpress_defconfig Ahmad Fatoum
2023-05-22 8:23 ` Sascha Hauer
2023-05-22 8:36 ` Ahmad Fatoum
2023-05-22 5:22 ` [PATCH master 4/7] ARM64: configs: temporarily revive qemu_virt64_defconfig Ahmad Fatoum
2023-05-22 5:22 ` [PATCH master 5/7] pbl: have DEBUG_PBL depend only on PBL_CONSOLE Ahmad Fatoum
2023-05-22 5:22 ` [PATCH master 6/7] meminfo: avoid out-of-bounds compiler warning Ahmad Fatoum
2023-05-22 5:22 ` [PATCH master 7/7] console: don't fixup baud rate into earlycon string Ahmad Fatoum
2023-05-23 7:23 ` [PATCH master 1/7] test: self: ramfs: fix unintended macro identifier confusion Sascha Hauer
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=20230522052222.1037931-2-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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