Github messages for voidlinux
 help / color / mirror / Atom feed
From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: All PHP versions with imagick enabled (`extension=imagick`) segfault
Date: Fri, 02 Feb 2024 22:52:39 +0100	[thread overview]
Message-ID: <20240202215239.6301528876@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48500@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 744 bytes --]

New comment by TinfoilSubmarine on void-packages repository

https://github.com/void-linux/void-packages/issues/48500#issuecomment-1924754633

Comment:
As mentioned in [this thread](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109634#c4), these are some options:

> libgomp can be only dlopened in threaded apps if there is still space in the static TLS surplus, which unfortunately some versions of glibc use even for normal TLS rather than just static TLS.
> So, LD_PRELOAD=libgomp.so.1, or link the program with libgomp.so.1 rather than just its libraries, or dlopen it before spawning threads.
> This is how glibc behaves, and unless we want to slow down libgomp extremely, there is nothing that can be done about it on the GCC side.


  reply	other threads:[~2024-02-02 21:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 21:50 [ISSUE] " TinfoilSubmarine
2024-02-02 21:52 ` TinfoilSubmarine [this message]
2024-02-02 21:53 ` TinfoilSubmarine
2024-02-02 22:07 ` classabbyamp
2024-02-02 22:15 ` TinfoilSubmarine
2024-02-03  2:20 ` sgn
2024-02-03  4:48 ` oreo639
2024-02-03  4:49 ` oreo639
2024-02-03  4:50 ` oreo639
2024-02-03  4:52 ` oreo639
2024-02-03  4:54 ` oreo639
2024-02-03  4:54 ` oreo639
2024-02-03  4:55 ` oreo639
2024-02-03  4:57 ` oreo639
2024-02-03  5:06 ` oreo639
2024-02-03  8:29 ` oreo639
2024-02-04 19:34 ` TinfoilSubmarine
2024-02-04 19:34 ` [ISSUE] [CLOSED] " TinfoilSubmarine

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=20240202215239.6301528876@inbox.vuxu.org \
    --to=tinfoilsubmarine@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).