public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 11.4.0/musl/
Date: Mon,  2 Jan 2023 01:41:01 +0000 (UTC)	[thread overview]
Message-ID: <1672621384.c6e054b9a653edf7d5f6e94ded6c3887c2f1ec60.sam@gentoo> (raw)

commit:     c6e054b9a653edf7d5f6e94ded6c3887c2f1ec60
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Jan  2 01:03:04 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jan  2 01:03:04 2023 +0000
URL:        https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=c6e054b9

11.4.0: update calloc/musl patch

Signed-off-by: Sam James <sam <AT> gentoo.org>

 11.4.0/musl/50_all_calloc_libgccjit.patch | 50 +++++++++++++++++++++++++++++++
 1 file changed, 50 insertions(+)

diff --git a/11.4.0/musl/50_all_calloc_libgccjit.patch b/11.4.0/musl/50_all_calloc_libgccjit.patch
index 5dec538..bbb6787 100644
--- a/11.4.0/musl/50_all_calloc_libgccjit.patch
+++ b/11.4.0/musl/50_all_calloc_libgccjit.patch
@@ -12,6 +12,36 @@ 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/cp/mapper-client.cc
++++ b/gcc/cp/mapper-client.cc
+@@ -27,6 +27,7 @@ along with GCC; see the file COPYING3.  If not see
+ #define INCLUDE_STRING
+ #define INCLUDE_VECTOR
+ #define INCLUDE_MAP
++#include <pthread.h>
+ #include "system.h"
+ 
+ #include "line-map.h"
+--- a/gcc/cp/mapper-resolver.cc
++++ b/gcc/cp/mapper-resolver.cc
+@@ -25,6 +25,7 @@ along with GCC; see the file COPYING3.  If not see
+ #define INCLUDE_VECTOR
+ #define INCLUDE_ALGORITHM
+ #define INCLUDE_MAP
++#include <pthread.h>
+ #include "system.h"
+ 
+ // We don't want or need to be aware of networking
+--- a/gcc/cp/module.cc
++++ b/gcc/cp/module.cc
+@@ -204,6 +204,7 @@ Classes used:
+ #include "config.h"
+ #define INCLUDE_STRING
+ #define INCLUDE_VECTOR
++#include <pthread.h>
+ #include "system.h"
+ #include "coretypes.h"
+ #include "cp-tree.h"
 --- a/gcc/jit/jit-playback.c
 +++ b/gcc/jit/jit-playback.c
 @@ -18,6 +18,8 @@ You should have received a copy of the GNU General Public License
@@ -70,3 +100,23 @@ included #pragma GCC poison calloc
  
  #include "libgccjit.h"
  #include "jit-recording.h"
+--- a/libcc1/libcc1plugin.cc
++++ b/libcc1/libcc1plugin.cc
+@@ -17,6 +17,7 @@
+    along with GCC; see the file COPYING3.  If not see
+    <http://www.gnu.org/licenses/>.  */
+ 
++#include <pthread.h>
+ #include <cc1plugin-config.h>
+ 
+ #undef PACKAGE_NAME
+--- a/libcc1/libcp1plugin.cc
++++ b/libcc1/libcp1plugin.cc
+@@ -18,6 +18,7 @@
+    along with GCC; see the file COPYING3.  If not see
+    <http://www.gnu.org/licenses/>.  */
+ 
++#include <pthread.h>
+ #include <cc1plugin-config.h>
+ 
+ #undef PACKAGE_NAME


             reply	other threads:[~2023-01-02  1:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-02  1:41 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-11  9:00 [gentoo-commits] proj/gcc-patches:master commit in: 11.4.0/musl/ 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=1672621384.c6e054b9a653edf7d5f6e94ded6c3887c2f1ec60.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