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/111627] modula2: Excess test fails with a case-preserving-case-insensitive source tree. Date: Wed, 31 Jan 2024 15:44:56 +0000 [thread overview] Message-ID: <bug-111627-4-21SJPIdTMu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111627-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111627 --- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Gaius Mulley <gaius@gcc.gnu.org>: https://gcc.gnu.org/g:4fd094835a8997cdcc3d18d7d297debe1527202d commit r14-8663-g4fd094835a8997cdcc3d18d7d297debe1527202d Author: Gaius Mulley <gaiusmod2@gmail.com> Date: Wed Jan 31 15:44:32 2024 +0000 PR modula2/111627 Excess test fails with a case-preserving-case-insensitive source tree This patch renames gm2 testsuite modules whose names conflict with library modules. The conflict is not seen on case preserving case sensitive file systems. gcc/testsuite/ChangeLog: PR modula2/111627 * gm2/pim/pass/stdio.mod: Moved to... * gm2/pim/pass/teststdio.mod: ...here. * gm2/pim/run/pass/builtins.mod: Moved to... * gm2/pim/run/pass/testbuiltins.mod: ...here. * gm2/pim/run/pass/math.mod: Moved to... * gm2/pim/run/pass/testmath.mod: ...here. * gm2/pim/run/pass/math2.mod: Moved to... * gm2/pim/run/pass/testmath2.mod: ...here. Signed-off-by: Gaius Mulley <gaiusmod2@gmail.com>
next prev parent reply other threads:[~2024-01-31 15:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-28 11:52 [Bug modula2/111627] New: " iains at gcc dot gnu.org 2023-09-28 11:54 ` [Bug modula2/111627] " iains at gcc dot gnu.org 2023-11-14 21:37 ` gaius at gcc dot gnu.org 2024-01-31 13:29 ` gaius at gcc dot gnu.org 2024-01-31 15:44 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-31 16:55 ` gaius at gcc dot gnu.org 2024-02-01 10:25 ` cvs-commit at gcc dot gnu.org 2024-02-01 20:40 ` iains 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-111627-4-21SJPIdTMu@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).