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/108835] gm2 tests at large -jNN numbers do not return
Date: Thu, 10 Aug 2023 12:55:39 +0000	[thread overview]
Message-ID: <bug-108835-4-kyFyT3vv8C@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108835-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Gaius Mulley from comment #9)
> This looks fixed from the commit trail - can this PR be closed now?

It's "fixed" - in that the more defensive coding around the select calls no
longer triggers the hanging case.

Unfortunately, I was not able to find any conclusive reason why the select
calls are getting incorrect input in the first place.  So, we can close this
bug but perhaps remember in the back of the mind that something (unknown) is
still not quite right with the select usage.

  parent reply	other threads:[~2023-08-10 12:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 12:28 [Bug testsuite/108835] New: " aldyh at gcc dot gnu.org
2023-02-19 20:29 ` [Bug testsuite/108835] " gaius at gcc dot gnu.org
2023-02-19 20:34 ` gaius at gcc dot gnu.org
2023-02-19 22:10 ` cvs-commit at gcc dot gnu.org
2023-02-20  7:12 ` aldyh at gcc dot gnu.org
2023-02-20 13:28 ` gaius at gcc dot gnu.org
2023-02-22 11:10 ` iains at gcc dot gnu.org
2023-06-30 14:15 ` cvs-commit at gcc dot gnu.org
2023-07-03 14:24 ` cvs-commit at gcc dot gnu.org
2023-07-27 21:43 ` gaius at gcc dot gnu.org
2023-08-10 12:55 ` iains at gcc dot gnu.org [this message]
2023-08-10 14:10 ` gaius 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-108835-4-kyFyT3vv8C@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).