public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "simon at pushface dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/112529] New: ACATS test c250002 uses illegal filename on APFS filesystem Date: Tue, 14 Nov 2023 17:07:17 +0000 [thread overview] Message-ID: <bug-112529-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112529 Bug ID: 112529 Summary: ACATS test c250002 uses illegal filename on APFS filesystem Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: simon at pushface dot org Target Milestone: --- This test checks that characters in Latin-1 above ASCII.Del can be used in identifiers, character literals and strings. Some of the identifiers are package names, so when the source is "gnatchopped' they become filenames. In Apple's HFS+, although filesystem naming is UTF-8 (well, Apple's version), attempts to create files with Latin-1 names are allowed by silent name conversion: for example, given the filename c250002_á.ads, what is stored is c250002_%E1.ads. In Apple's current APFS, however, this attempt results in failure: $ gnatchop c250002.aw splitting c250002.aw into: c250002_0.ads cannot create c250002_?.ads cannot create c250002_?.adb c250002.adb It would perhaps be ideal to report this test as 'unsupported' if run on macOS, but this could be challenging given the rather ad-hoc nature of the scripts involved. Just not running the test at all wouldn't be right, since it runs OK on other operating systems.
next reply other threads:[~2023-11-14 17:07 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-14 17:07 simon at pushface dot org [this message] 2023-11-14 17:52 ` [Bug testsuite/112529] " ebotcazou 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-112529-4@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).