From: Lucas Stach <l.stach@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 1/4] dtc: fix build with GCC11
Date: Sat, 1 May 2021 00:31:03 +0200 [thread overview]
Message-ID: <20210430223106.2472-1-l.stach@pengutronix.de> (raw)
Pick patch from upstream to fix warning with GCC11.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
.../0001-fdtdump-Fix-gcc11-warning.patch | 30 +++++++++++++++++++
patches/dtc-v1.6.0/series | 4 +++
2 files changed, 34 insertions(+)
create mode 100644 patches/dtc-v1.6.0/0001-fdtdump-Fix-gcc11-warning.patch
create mode 100644 patches/dtc-v1.6.0/series
diff --git a/patches/dtc-v1.6.0/0001-fdtdump-Fix-gcc11-warning.patch b/patches/dtc-v1.6.0/0001-fdtdump-Fix-gcc11-warning.patch
new file mode 100644
index 000000000000..052419940a15
--- /dev/null
+++ b/patches/dtc-v1.6.0/0001-fdtdump-Fix-gcc11-warning.patch
@@ -0,0 +1,30 @@
+From: David Gibson <david@gibson.dropbear.id.au>
+Date: Wed, 6 Jan 2021 14:52:26 +1100
+Subject: [PATCH] fdtdump: Fix gcc11 warning
+
+In one place, fdtdump abuses fdt_set_magic(), passing it just a small char
+array instead of the full fdt header it expects. That's relying on the
+fact that in fact fdt_set_magic() will only actually access the first 4
+bytes of the buffer.
+
+This trips a new warning in GCC 11 - and it's entirely possible it was
+always UB. So, don't do that.
+
+Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
+---
+ fdtdump.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/fdtdump.c b/fdtdump.c
+index 9613befede71..d9fb374a59be 100644
+--- a/fdtdump.c
++++ b/fdtdump.c
+@@ -217,7 +217,7 @@ int main(int argc, char *argv[])
+ char *p = buf;
+ char *endp = buf + len;
+
+- fdt_set_magic(smagic, FDT_MAGIC);
++ fdt32_st(smagic, FDT_MAGIC);
+
+ /* poor man's memmem */
+ while ((endp - p) >= FDT_MAGIC_SIZE) {
diff --git a/patches/dtc-v1.6.0/series b/patches/dtc-v1.6.0/series
new file mode 100644
index 000000000000..a7e9d0319ba0
--- /dev/null
+++ b/patches/dtc-v1.6.0/series
@@ -0,0 +1,4 @@
+# generated by git-ptx-patches
+#tag:base --start-number 1
+0001-fdtdump-Fix-gcc11-warning.patch
+# cb5c26c7ab3ae2082ecff7af4de4e8c5 - git-ptx-patches magic
--
2.29.2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2021-04-30 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 22:31 Lucas Stach [this message]
2021-04-30 22:31 ` [ptxdist] [PATCH 2/4] nspr: version bump 4.26 -> 4.30 Lucas Stach
2021-04-30 22:31 ` [ptxdist] [PATCH 3/4] host-nss: disable array-parameter warning Lucas Stach
2021-05-02 13:14 ` Roland Hieber
2021-04-30 22:31 ` [ptxdist] [PATCH 4/4] host-fakeroot: version bump 1.25.1 -> 1.25.3 Lucas Stach
2021-05-02 13:18 ` Roland Hieber
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=20210430223106.2472-1-l.stach@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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