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 modula2/108404] M2RTS_Halt fails with a segv (it should emit a diagnostic and exit).
Date: Thu, 10 Aug 2023 12:21:34 +0000 [thread overview]
Message-ID: <bug-108404-4-5T8ofmUYKG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108404-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108404
--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Gaius Mulley from comment #7)
> I wonder if this bug has now been fixed via the other PR fixes.
> Specifically the rewrite of RTco.cc, the defensive use of select, bugfixes
> to HIGH and FIO.mod (memcpy parameters)? It might be worth a re-run just to
> explore the effect of these fixes.
I guess we can say this bug is fixed, indeed.
...the other hanging tests have been 'fixed' by a more defensive implementation
of the select functionality (although it remains unclear why select is failing
in the first place).
next prev parent reply other threads:[~2023-08-10 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 9:57 [Bug modula2/108404] New: " iains at gcc dot gnu.org
2023-01-15 20:48 ` [Bug modula2/108404] " gaius at gcc dot gnu.org
2023-01-16 8:32 ` gaius at gcc dot gnu.org
2023-01-16 18:25 ` gaius at gcc dot gnu.org
2023-01-16 23:05 ` iains at gcc dot gnu.org
2023-01-17 16:15 ` gaius at gcc dot gnu.org
2023-01-17 19:52 ` iains at gcc dot gnu.org
2023-08-05 17:35 ` gaius at gcc dot gnu.org
2023-08-10 12:21 ` iains at gcc dot gnu.org [this message]
2023-08-10 12:49 ` 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-108404-4-5T8ofmUYKG@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).