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 target/114233] Newly-introduced pr113617.C test fails on Darwin
Date: Thu, 07 Mar 2024 15:45:02 +0000	[thread overview]
Message-ID: <bug-114233-4-hpy7qONdfd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114233-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Francois-Xavier Coudert from comment #3)


> The question is: will this reveal new issues in other tests that weren't
> running before. I'm starting a new regtest and will post the results here.

Well, I do not think that actually matters (perhaps if newly revealed tests
hang, it's a problem - but otherwise it's just telling us something we should
already have known).

So, FAOD absent something drastic like a hanging testsuite, the update to the
darwin-specific code in the target-supports is OK.

  parent reply	other threads:[~2024-03-07 15:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05  7:24 [Bug target/114233] New: " fxcoudert at gcc dot gnu.org
2024-03-05  7:25 ` [Bug target/114233] " fxcoudert at gcc dot gnu.org
2024-03-06 20:32 ` iains at gcc dot gnu.org
2024-03-07 13:31 ` fxcoudert at gcc dot gnu.org
2024-03-07 14:25 ` fxcoudert at gcc dot gnu.org
2024-03-07 15:06 ` iains at gcc dot gnu.org
2024-03-07 15:45 ` iains at gcc dot gnu.org [this message]
2024-03-08 14:19 ` cvs-commit at gcc dot gnu.org
2024-03-29 18:55 ` iains 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-114233-4-hpy7qONdfd@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).