From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 11.4.0/gentoo/
Date: Sat, 2 Dec 2023 05:28:11 +0000 (UTC) [thread overview]
Message-ID: <1701494309.a0a1379a3be2a614058045a6bf24eb67d6007044.sam@gentoo> (raw)
commit: a0a1379a3be2a614058045a6bf24eb67d6007044
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 2 05:18:29 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Dec 2 05:18:29 2023 +0000
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=a0a1379a
11.4.0: add 77_all_all_PR112823_13_libiberty-warning.patch
Bug: https://gcc.gnu.org/PR112823
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../77_all_all_PR112823_13_libiberty-warning.patch | 36 ++++++++++++++++++++++
11.4.0/gentoo/README.history | 3 ++
2 files changed, 39 insertions(+)
diff --git a/11.4.0/gentoo/77_all_all_PR112823_13_libiberty-warning.patch b/11.4.0/gentoo/77_all_all_PR112823_13_libiberty-warning.patch
new file mode 100644
index 0000000..26d38af
--- /dev/null
+++ b/11.4.0/gentoo/77_all_all_PR112823_13_libiberty-warning.patch
@@ -0,0 +1,36 @@
+https://gcc.gnu.org/PR112823
+https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=38757aa88735ab
+
+From 38757aa88735ab2e511bc428e2407a5a5e9fa0be Mon Sep 17 00:00:00 2001
+From: Iain Sandoe <iain@sandoe.co.uk>
+Date: Mon, 23 Aug 2021 17:34:43 +0100
+Subject: [PATCH] libiberty, Darwin: Fix a build warning.
+
+r12-3005-g220c410162ebece4f missed a cast for the set_32 call.
+Fixed thus.
+
+Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
+
+libiberty/ChangeLog:
+
+ * simple-object-mach-o.c (simple_object_mach_o_write_segment):
+ Cast the first argument to set_32 as needed.
+---
+ libiberty/simple-object-mach-o.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/libiberty/simple-object-mach-o.c b/libiberty/simple-object-mach-o.c
+index 72b69d19c21..a8869e7c639 100644
+--- a/libiberty/simple-object-mach-o.c
++++ b/libiberty/simple-object-mach-o.c
+@@ -1228,7 +1228,7 @@ simple_object_mach_o_write_segment (simple_object_write *sobj, int descriptor,
+ /* Swap the indices, if required. */
+
+ for (i = 0; i < (nsects_in * 4); ++i)
+- set_32 (&index[i], index[i]);
++ set_32 ((unsigned char *) &index[i], index[i]);
+
+ sechdr_offset += sechdrsize;
+
+--
+2.39.3
diff --git a/11.4.0/gentoo/README.history b/11.4.0/gentoo/README.history
index b578306..436fcb5 100644
--- a/11.4.0/gentoo/README.history
+++ b/11.4.0/gentoo/README.history
@@ -1,3 +1,6 @@
+11 2 Dec 2023
+ + 77_all_all_PR112823_13_libiberty-warning.patch
+
10 5 May 2023
- 77_all_all_PR109585_13_rtl-alias-analysis-typo.patch
next reply other threads:[~2023-12-02 5:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 5:28 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-09 13:49 [gentoo-commits] proj/gcc-patches:master commit in: 11.4.0/gentoo/ Sam James
2023-12-06 10:52 Sam James
2023-05-05 2:37 Sam James
2023-04-27 23:56 Sam James
2023-01-28 5:13 Sam James
2023-01-23 0:35 Sam James
2023-01-23 0:35 Sam James
2023-01-07 7:47 Sam James
2022-12-17 4:54 Sam James
2022-12-17 4:54 Sam James
2022-12-17 4:54 Sam James
2022-11-20 0:25 Sam James
2022-08-22 2:14 Sam James
2022-05-22 23:16 Sam James
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=1701494309.a0a1379a3be2a614058045a6bf24eb67d6007044.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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