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: Wed, 09 Aug 2023 10:20:44 +0000 [thread overview] Message-ID: <bug-110779-4-IXT9dSLfXI@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 #11 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:9043e8a8d82ac2afaf8b5fcdfcbbd12f759b14d4 commit r13-7702-g9043e8a8d82ac2afaf8b5fcdfcbbd12f759b14d4 Author: Gaius Mulley <gaiusmod2@gmail.com> Date: Wed Aug 9 11:19:50 2023 +0100 PR modula2/110779: libgm2 fix solaris bootstrap check for tm_gmtoff This patch defensively checks for every C function and every struct used in wrapclock.cc. It adds return values to GetTimespec and SetTimespec to allow the module to return a code representing unavailable. gcc/m2/ChangeLog: PR modula2/110779 * gm2-libs-iso/SysClock.mod (GetClock): Test GetTimespec return value. (SetClock): Test SetTimespec return value. * gm2-libs-iso/wrapclock.def (GetTimespec): Add integer return type. (SetTimespec): Add integer return type. libgm2/ChangeLog: PR modula2/110779 * config.h.in: Regenerate. * configure: Regenerate. * configure.ac (AC_CACHE_CHECK): Check for tm_gmtoff field in struct tm. (GM2_CHECK_LIB): Check for daylight, timezone and tzname. * libm2iso/wrapclock.cc (timezone): Guard against absence of struct tm and tm_gmtoff. (daylight): Check for daylight. (timezone): Check for timezone. (isdst): Check for isdst. (tzname): Check for tzname. (GetTimeRealtime): Check for struct timespec. (SetTimeRealtime): Check for struct timespec. (InitTimespec): Check for struct timespec. (KillTimespec): Check for struct timespec. (SetTimespec): Check for struct timespec. (GetTimespec): Check for struct timespec. Signed-off-by: Gaius Mulley <gaiusmod2@gmail.com>
next prev parent reply other threads:[~2023-08-09 10:20 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 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 [this message] 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-IXT9dSLfXI@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: linkBe 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).