public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/109951] [14 Regression] libgomp, testsuite: non-native multilib c++ tests fail on Darwin.
Date: Thu, 25 May 2023 23:34:21 +0000	[thread overview]
Message-ID: <bug-109951-4-Ir2ZsHypGq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109951-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> ---
Since AFAICT, there is only one piece of Darwin-specific code in the libgomp
TCL (which adds -shared-libgcc), I would expect the base phenomenon to be the
same on Linux.  What is not obvious there is why it seems to work in that case
(unless it's just Darwin's linker being 'picky').

  parent reply	other threads:[~2023-05-25 23:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  7:23 [Bug testsuite/109951] New: " iains at gcc dot gnu.org
2023-05-24  7:25 ` [Bug testsuite/109951] " iains at gcc dot gnu.org
2023-05-24 10:39 ` iains at gcc dot gnu.org
2023-05-25  7:38 ` rguenth at gcc dot gnu.org
2023-05-25 22:04 ` tschwinge at gcc dot gnu.org
2023-05-25 23:12 ` iains at gcc dot gnu.org
2023-05-25 23:34 ` iains at gcc dot gnu.org [this message]
2023-06-01 16:02 ` tschwinge at gcc dot gnu.org
2023-06-02 10:00 ` tschwinge at gcc dot gnu.org
2023-06-02 10:08 ` tschwinge at gcc dot gnu.org
2023-06-02 14:31 ` iains at gcc dot gnu.org
2023-09-12  9:32 ` cvs-commit at gcc dot gnu.org
2023-09-12  9:32 ` cvs-commit at gcc dot gnu.org
2023-09-12 11:32 ` tschwinge at gcc dot gnu.org
2023-09-12 20:20 ` cvs-commit at gcc dot gnu.org
2023-10-26 16:05 ` cvs-commit at gcc dot gnu.org
2023-10-26 16:05 ` 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-109951-4-Ir2ZsHypGq@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).