public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/110779] SysClock can not read the clock
Date: Mon, 07 Aug 2023 14:10:04 +0000 [thread overview]
Message-ID: <bug-110779-4-cZMUlFQ8Q9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110779-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110779
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Gaius Mulley
<gaius@gcc.gnu.org>:
https://gcc.gnu.org/g:4f8d84955dd5c9d2882d09e9c249240efe3a02aa
commit r13-7691-g4f8d84955dd5c9d2882d09e9c249240efe3a02aa
Author: Gaius Mulley <gaiusmod2@gmail.com>
Date: Mon Aug 7 15:08:49 2023 +0100
PR modula2/110779 SysClock can not read the clock
This patch completes the implementation of the ISO module
SysClock.mod. Three new testcases are provided. wrapclock.{cc,def}
are new support files providing access to clock_settime, clock_gettime
and glibc timezone variables.
gcc/m2/ChangeLog:
PR modula2/110779
* gm2-libs-iso/SysClock.mod: Re-implement using wrapclock.
* gm2-libs-iso/wrapclock.def: New file.
libgm2/ChangeLog:
PR modula2/110779
* config.h.in: Regenerate.
* configure: Regenerate.
* configure.ac (GM2_CHECK_LIB): Check for clock_gettime
and clock_settime.
* libm2iso/Makefile.am (M2DEFS): Add wrapclock.def.
* libm2iso/Makefile.in: Regenerate.
* libm2iso/wraptime.cc: Replace HAVE_TIMEVAL with
HAVE_STRUCT_TIMEVAL.
* libm2iso/wrapclock.cc: New file.
gcc/testsuite/ChangeLog:
PR modula2/110779
* gm2/iso/run/pass/m2date.mod: New test.
* gm2/iso/run/pass/testclock.mod: New test.
* gm2/iso/run/pass/testclock2.mod: New test.
Signed-off-by: Gaius Mulley <gaiusmod2@gmail.com>
next prev parent reply other threads:[~2023-08-07 14:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 19:55 [Bug modula2/110779] New: " gaius at gcc dot gnu.org
2023-07-23 19:56 ` [Bug modula2/110779] " gaius at gcc dot gnu.org
2023-08-04 4:04 ` gaius at gcc dot gnu.org
2023-08-04 12:17 ` gaius at gcc dot gnu.org
2023-08-05 16:39 ` cvs-commit at gcc dot gnu.org
2023-08-05 16:43 ` gaius at gcc dot gnu.org
2023-08-07 14:10 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-07 17:07 ` ro at gcc dot gnu.org
2023-08-07 23:51 ` gaius at gcc dot gnu.org
2023-08-08 11:40 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-08-09 8:36 ` cvs-commit at gcc dot gnu.org
2023-08-09 10:20 ` cvs-commit at gcc dot gnu.org
2023-08-10 14:29 ` gaius at gcc dot gnu.org
2023-08-12 15:27 ` iains at gcc dot gnu.org
2023-08-12 17:19 ` cvs-commit at gcc dot gnu.org
2023-08-12 19:21 ` cvs-commit at gcc dot gnu.org
2023-08-12 19:24 ` gaius at gcc dot gnu.org
2023-08-13 17:47 ` egallager at gcc dot gnu.org
2023-11-09 7:45 ` tschwinge at gcc dot gnu.org
2023-11-09 18:10 ` gaius at gcc dot gnu.org
2023-11-10 20:04 ` gaius at gcc dot gnu.org
2023-11-10 20:47 ` gaius at gcc dot gnu.org
2023-11-13 15:12 ` cvs-commit at gcc dot gnu.org
2024-01-24 13:45 ` 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-110779-4-cZMUlFQ8Q9@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).