public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sarah.kriesch at opensuse dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/103364] s390x: TLS reference in /usr/lib64/libLLVM.so mismatches non-TLS reference in /usr/lib64/libLLVM.so
Date: Sat, 11 Dec 2021 18:26:33 +0000	[thread overview]
Message-ID: <bug-103364-4-WMtJnUmMz4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103364-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103364

--- Comment #25 from Sarah Julia Kriesch <sarah.kriesch at opensuse dot org> ---
The kernel bug fix in combination with higher constraints (12GB of memory) has
helped. It is strange, that we had this error message instead of an oom.
BUT that should be only a workaround.
12GB for s390x in comparison to 4GB for x86 for PostgreSQL?
I suggest a new bug report for the memory requirements of GCC. Where is the
power of the mainframe?

Thank you for the support! It should be possible to reproduce it again on
Fedora in the future. The problem was a dependency of the kernel and
cross-epiphany-gcc11-bootstrap.

  parent reply	other threads:[~2021-12-11 18:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 19:08 [Bug c/103364] New: " sarah.kriesch at opensuse dot org
2021-11-22 19:30 ` [Bug c/103364] " sarah.kriesch at opensuse dot org
2021-11-23  6:34 ` [Bug middle-end/103364] " pinskia at gcc dot gnu.org
2021-11-23  6:45 ` pinskia at gcc dot gnu.org
2021-11-23  6:46 ` pinskia at gcc dot gnu.org
2021-11-23  6:47 ` pinskia at gcc dot gnu.org
2021-11-23  8:10 ` sarah.kriesch at opensuse dot org
2021-11-23  8:13 ` sarah.kriesch at opensuse dot org
2021-11-23 13:04 ` hjl.tools at gmail dot com
2021-11-23 15:26 ` sarah.kriesch at opensuse dot org
2021-11-23 15:28 ` sarah.kriesch at opensuse dot org
2021-12-02 11:03 ` krebbel at gcc dot gnu.org
2021-12-02 14:17 ` sarah.kriesch at opensuse dot org
2021-12-02 14:18 ` sarah.kriesch at opensuse dot org
2021-12-02 14:22 ` sarah.kriesch at opensuse dot org
2021-12-02 15:57 ` krebbel at gcc dot gnu.org
2021-12-02 17:04 ` sarah.kriesch at opensuse dot org
2021-12-03 14:50 ` krebbel at gcc dot gnu.org
2021-12-05 22:07 ` sarah.kriesch at opensuse dot org
2021-12-06  8:34 ` sarah.kriesch at opensuse dot org
2021-12-06  9:54 ` krebbel at gcc dot gnu.org
2021-12-06 12:17 ` sarah.kriesch at opensuse dot org
2021-12-06 19:59 ` krebbel at gcc dot gnu.org
2021-12-07 12:46 ` sarah.kriesch at opensuse dot org
2021-12-07 20:35 ` sarah.kriesch at opensuse dot org
2021-12-11 18:26 ` sarah.kriesch at opensuse dot org [this message]
2022-01-17  8:48 ` krebbel at gcc dot gnu.org

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=bug-103364-4-WMtJnUmMz4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).