From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D90C33858D28; Sun, 23 Jul 2023 19:55:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D90C33858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1690142147; bh=8i/TCRF/lWXrS09TGCGvgpuA/AgxYq9pyjxrqGBGaHc=; h=From:To:Subject:Date:From; b=UOTQSAIzjLdAokOGQovrgHQeg4ZvyUbH7Yl8PWJwNHDYpYC7biJKDvbtRYo3ZDs59 XnCWTs7Q6byU84hUSIv/9ZWnVV/pzaPxWZnIRYScxUcx1k8DYaQFJttC8w32OCTSjR 4lhZG60lyt+6U5oL/rhKBUzudIlyqOJ5bSCs9Ko8= From: "gaius at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/110779] New: SysClock can not read the clock Date: Sun, 23 Jul 2023 19:55:47 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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: gaius 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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 Bug ID: 110779 Summary: SysClock can not read the clock Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: modula2 Assignee: gaius at gcc dot gnu.org Reporter: gaius at gcc dot gnu.org Target Milestone: --- Relayed from the gm2 mailing list: can you please have a short check - my versions of the compiler now always seem to have a return value of "FALSE" for SysClock.CanGetClock(); Just notices as I had update one test routine and noted that I was always testing against the same set of data - the random number generator uses a seed depended on the system time. ----- Shot check routine: MODULE TstSysClock; IMPORT SysClock; IMPORT STextIO; BEGIN STextIO.WriteLn; STextIO.WriteLn; IF SysClock.CanGetClock() THEN STextIO.WriteString(" clock can be read"); ELSE STextIO.WriteString(" clock can NOT be read"); END; STextIO.WriteLn; STextIO.WriteLn; END TstSysClock.=