From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 6C8B3385800C; Thu, 10 Aug 2023 12:21:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6C8B3385800C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1691670096;
	bh=6pdF4m+6F7rwlRnfMgX7wN9BsTqAFHyk6yKo0CE27Xc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=yN9YVGoWYgrT/I2LaME4Iz9IuCJ72hXw93CXPrJML2gisH00+G4NLGK7veuKAKdBk
	 dYvxtITxGf321KvDyYHtqZzv7zL/W/0uSeRS+NEQANuDnFYXY1HWDxy59MLbn9jjKZ
	 H1wlhvJhhb6EwVPNKmaFLY5HXgBdjs/TPNVwp0Kw=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: modula2
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: gaius at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108404-4-5T8ofmUYKG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108404-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108404-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

--- 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.=20
> 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 implementa=
tion
of the select functionality (although it remains unclear why select is fail=
ing
in the first place).=