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: Thu, 01 Feb 2024 10:57:38 +0000 [thread overview]
Message-ID: <bug-112506-4-7BYaLyy1vm@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
--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Gaius Mulley from comment #7)
> I doubt the m2date and testclock are related to filesystem case (but I could
> be wrong) as I've built gcc on a gnu-linux jfs filesystem (case preserving
> case insensitive) and see:
I agree that are not related to the FS - they occur on all Darwin versions and
on three different FS kinds.
- the main point here was to note that we do not expect them to be fixed by the
FS CS fix.
next prev parent reply other threads:[~2024-02-01 10:57 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
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 [this message]
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-7BYaLyy1vm@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).