From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CE5343858D32; Sun, 13 Aug 2023 17:47:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CE5343858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1691948854; bh=vgHUVYJKAd5sS+dyOXt7iNdbEtFPrHWHeSHC9SaQUiY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=oK0UwaVgxArvscaPHgwhUv1JeZgjw7sV/OxQ704j6HX5GMd5W7BeGPDR7L2lk9XgH y1KAX05HRN2ygdTl+M3cyLg6OXAhOBbCDRi309uTwqvEon/iftEx9l5a4XYP3nNm/k K/OZzT0M0RhsPOU/dkEz/3FuU8yZQA4t8MgT/cnM= From: "egallager at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/110779] SysClock can not read the clock Date: Sun, 13 Aug 2023 17:47:33 +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: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: egallager at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED 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: cc Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110779 Eric Gallager changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |egallager at gcc dot gnu.o= rg --- Comment #17 from Eric Gallager --- (In reply to Iain Sandoe from comment #13) > (In reply to Gaius Mulley from comment #12) > > Created attachment 55717 [details] > > Another patch for Darwin > >=20 > > More portability configure checks and fixes to wrapclock.cc. >=20 > This patch fixes bootstrap on the affected versions - I've tried it on old > and new Darwin + a cross. There are some time-related test fails, but th= at > can be handled separately. So is this why I was getting all the timeouts in my most recent test result= s? https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/793205.html=