public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/103944] [12 Regression] Testsuite hang due to libphobos/testsuite/libphobos.gc/forkgc2.d
Date: Mon, 10 Jan 2022 14:10:08 +0000	[thread overview]
Message-ID: <bug-103944-4-MWgMky89a0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103944-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Note, it isn't just i686-linux, I was getting the hangs on x86_64-linux,
s390x-linux or armv7hl-linux-gnueabi too.
Wonder whether it is
-fstack-clash-protection -fcf-protection -fcf-protection
related or perhaps glibc version dependent (in the builds where it reproduces
we are using a very recent glibc snapshot (e.g. one with _dl_find_object in
there in case the test uses unwind info in some way)).

  parent reply	other threads:[~2022-01-10 14:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 17:07 [Bug d/103944] New: " jakub at gcc dot gnu.org
2022-01-07 17:09 ` [Bug d/103944] " jakub at gcc dot gnu.org
2022-01-08  3:42 ` pinskia at gcc dot gnu.org
2022-01-10  8:49 ` jakub at gcc dot gnu.org
2022-01-10 13:55 ` ibuclaw at gdcproject dot org
2022-01-10 14:10 ` jakub at gcc dot gnu.org [this message]
2022-01-10 14:30 ` jakub at gcc dot gnu.org
2022-01-10 14:52 ` ibuclaw at gdcproject dot org
2022-01-10 17:51 ` ibuclaw at gdcproject dot org
2022-05-06  8:32 ` [Bug d/103944] [12/13 " jakub at gcc dot gnu.org
2022-07-18 14:34 ` doko at gcc dot gnu.org
2023-02-26 17:26 ` iains at gcc dot gnu.org
2023-05-08 12:23 ` [Bug d/103944] [12/13/14 " rguenth at gcc dot gnu.org
2023-07-01 16:15 ` cvs-commit at gcc dot gnu.org
2023-07-03 14:24 ` cvs-commit at gcc dot gnu.org
2024-03-09 17:18 ` law at gcc dot gnu.org
2024-04-04 18:50 ` cvs-commit 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-103944-4-MWgMky89a0@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).