public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/112506] gm2 test failures on x86_64-apple-darwin21 Date: Sat, 27 Jan 2024 11:36:49 +0000 [thread overview] Message-ID: <bug-112506-4-UVfVJeEXqE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112506-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112506 Iain Sandoe <iains at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2023-11-13 00:00:00 |2024-1-27 --- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> --- however, as of r14-8436-gf03b8f595b6350 on a case sensitive source partition the clock-related tests still fail. === gm2 tests === Running target unix FAIL: gm2/iso/run/pass/m2date.mod execution, -g FAIL: gm2/iso/run/pass/m2date.mod execution, -O FAIL: gm2/iso/run/pass/m2date.mod execution, -O -g FAIL: gm2/iso/run/pass/m2date.mod execution, -Os FAIL: gm2/iso/run/pass/m2date.mod execution, -O3 -fomit-frame-pointer FAIL: gm2/iso/run/pass/m2date.mod execution, -O3 -fomit-frame-pointer -finline-functions FAIL: gm2/iso/run/pass/testclock.mod execution, -g FAIL: gm2/iso/run/pass/testclock.mod execution, -O FAIL: gm2/iso/run/pass/testclock.mod execution, -O -g FAIL: gm2/iso/run/pass/testclock.mod execution, -Os FAIL: gm2/iso/run/pass/testclock.mod execution, -O3 -fomit-frame-pointer FAIL: gm2/iso/run/pass/testclock.mod execution, -O3 -fomit-frame-pointer -finline-functions === gm2 Summary === # of expected passes 13016 # of unexpected failures 12
next prev parent reply other threads:[~2024-01-27 11:36 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-13 7:12 [Bug modula2/112506] New: " fxcoudert at gcc dot gnu.org 2023-11-13 7:13 ` [Bug modula2/112506] " fxcoudert at gcc dot gnu.org 2023-11-13 7:25 ` fxcoudert at gcc dot gnu.org 2023-11-20 16:19 ` iains at gcc dot gnu.org 2023-11-20 16:22 ` iains at gcc dot gnu.org 2023-11-22 22:32 ` gaius at gcc dot gnu.org 2024-01-27 11:36 ` iains at gcc dot gnu.org [this message] 2024-02-01 10:25 ` cvs-commit at gcc dot gnu.org 2024-02-01 10:55 ` gaius at gcc dot gnu.org 2024-02-01 10:57 ` iains at gcc dot gnu.org 2024-02-01 20:42 ` iains at gcc dot gnu.org 2024-02-02 9:46 ` 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-112506-4-UVfVJeEXqE@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).