From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 12.0.0/musl/
Date: Mon, 25 Apr 2022 01:12:13 +0000 (UTC) [thread overview]
Message-ID: <1650849126.e1b2fe74f2926ecc663804531227937a90315a80.sam@gentoo> (raw)
commit: e1b2fe74f2926ecc663804531227937a90315a80
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 25 01:10:06 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Apr 25 01:12:06 2022 +0000
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=e1b2fe74
12.0.0: update calloc patch (again)
Bug: https://bugs.gentoo.org/828580
Signed-off-by: Sam James <sam <AT> gentoo.org>
12.0.0/musl/50_all_calloc_libgccjit.patch | 12 ++++++------
12.0.0/musl/README.history | 8 ++++++++
2 files changed, 14 insertions(+), 6 deletions(-)
diff --git a/12.0.0/musl/50_all_calloc_libgccjit.patch b/12.0.0/musl/50_all_calloc_libgccjit.patch
index 756f622..f50ef8f 100644
--- a/12.0.0/musl/50_all_calloc_libgccjit.patch
+++ b/12.0.0/musl/50_all_calloc_libgccjit.patch
@@ -8,8 +8,8 @@ Subject: [PATCH] Fix attempt to use poisoned calloc error in libgccjit
This moves usages of pthread.h to above any usage of system.h as it
included #pragma GCC poison calloc
---- a/gcc/jit/jit-playback.c
-+++ b/gcc/jit/jit-playback.c
+--- a/gcc/jit/jit-playback.cc
++++ b/gcc/jit/jit-playback.cc
@@ -18,6 +18,8 @@ You should have received a copy of the GNU General Public License
along with GCC; see the file COPYING3. If not see
<http://www.gnu.org/licenses/>. */
@@ -28,8 +28,8 @@ included #pragma GCC poison calloc
#include "jit-playback.h"
#include "jit-result.h"
#include "jit-builtins.h"
---- a/gcc/jit/jit-recording.c
-+++ b/gcc/jit/jit-recording.c
+--- a/gcc/jit/jit-recording.cc
++++ b/gcc/jit/jit-recording.cc
@@ -18,6 +18,8 @@ You should have received a copy of the GNU General Public License
along with GCC; see the file COPYING3. If not see
<http://www.gnu.org/licenses/>. */
@@ -48,8 +48,8 @@ included #pragma GCC poison calloc
#include "jit-builtins.h"
#include "jit-recording.h"
#include "jit-playback.h"
---- a/gcc/jit/libgccjit.c
-+++ b/gcc/jit/libgccjit.c
+--- a/gcc/jit/libgccjit.cc
++++ b/gcc/jit/libgccjit.cc
@@ -18,13 +18,14 @@ You should have received a copy of the GNU General Public License
along with GCC; see the file COPYING3. If not see
<http://www.gnu.org/licenses/>. */
diff --git a/12.0.0/musl/README.history b/12.0.0/musl/README.history
index bbddd5d..01e2278 100644
--- a/12.0.0/musl/README.history
+++ b/12.0.0/musl/README.history
@@ -1,3 +1,11 @@
+3 25 Apr 2022
+
+ - 25_all_multilib_pure64.patch
+ - 50_all_posix_memalign.patch
+ U 50_all_calloc_libgccjit.patch
+ - 50_all_cpu_indicator.patch
+ - nocross/50_all_libssp_unconditionally.patch
+
2 25 Apr 2022
- 25_all_multilib_pure64.patch
next reply other threads:[~2022-04-25 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 1:12 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-25 2:41 [gentoo-commits] proj/gcc-patches:master commit in: 12.0.0/musl/ Sam James
2022-04-25 1:12 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=1650849126.e1b2fe74f2926ecc663804531227937a90315a80.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