public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/110779] SysClock can not read the clock
Date: Tue, 08 Aug 2023 11:40:48 +0000	[thread overview]
Message-ID: <bug-110779-4-HDbWE6ml1I@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 #9 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #8 from Gaius Mulley <gaius at gcc dot gnu.org> ---
> Created attachment 55703
>   --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55703&action=edit
> Proposed fix (addendum)
>
> Here is a patch which tests for all the functions and structs in wrapclock.cc.

That patch does restore i386-pc-solaris2.11 bootstrap, thanks.

Testsuite results are good, with two exceptions: for 32-bit compilation
(only, 64-bit is fine), two tests reliably time out at all optimization
levels:

WARNING: gm2/iso/run/pass/m2date.mod execution,  -O  program timed out.

WARNING: gm2/iso/run/pass/testclock2.mod execution,  -O  program timed out.

Running them under truss shows that the last system call each is

5032:   clock_settime(3, 0x080975F0)                    Err#1 EPERM [sys_time]

Running testclock2.mod under gdb shows

Thread 2 received signal SIGINT, Interrupt.
[Switching to Thread 1 (LWP 1)]
0x08064ad4 in daysInMonth (year=42582828, month=7)
    at
/vol/gcc/src/hg/master/local/libgm2/libm2iso/../../gcc/m2/gm2-libs-iso/SysClock.mod:225
225     BEGIN
(gdb) bt
#0  0x08064ad4 in daysInMonth (year=42582828, month=7)
    at
/vol/gcc/src/hg/master/local/libgm2/libm2iso/../../gcc/m2/gm2-libs-iso/SysClock.mod:225
#1  0x08065152 in daysInYear (year=42582828, month=<optimized out>, 
    day=<optimized out>)
    at
/vol/gcc/src/hg/master/local/libgm2/libm2iso/../../gcc/m2/gm2-libs-iso/SysClock.mod:132
#2  ExtractDate (day=@0x808748c: 0, month=@0x8087484: 0, year=@0x8087480: 0, 
    days=53508608997914)
    at
/vol/gcc/src/hg/master/local/libgm2/libm2iso/../../gcc/m2/gm2-libs-iso/SysClock.mod:152
#3  m2iso_SysClock_GetClock (userData=...)
    at
/vol/gcc/src/hg/master/local/libgm2/libm2iso/../../gcc/m2/gm2-libs-iso/SysClock.mod:204
#4  0x0805f652 in _M2_testclock2_init ()
#5  0x08068d7a in m2pim_M2Dependent_ConstructModules (
    applicationmodule=0x805c2b4, libname=0x805c2bf, 
    overrideliborder=0x805c2d8, argc=1, argv=0xfeffdafc, envp=0xfeffdb04)
    at
/vol/gcc/src/hg/master/local/libgm2/libm2pim/../../gcc/m2/gm2-libs/M2Dependent.mod:809
#6  0x0805fca9 in _M2_init ()
#7  0x0805fcee in main ()

That year value seems very strange.

  parent reply	other threads:[~2023-08-08 11:40 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 [this message]
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-HDbWE6ml1I@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).