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 ada/111909] Filename case sensitivity defaulted wrongly on macOS Date: Tue, 28 Nov 2023 16:48:23 +0000 [thread overview] Message-ID: <bug-111909-4-HoWyXPEhfs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111909-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111909 --- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Marc Poulhi?s <dkm@gcc.gnu.org>: https://gcc.gnu.org/g:396db92d3aa7412dd7133563fecbc6237fa81c02 commit r14-5936-g396db92d3aa7412dd7133563fecbc6237fa81c02 Author: Simon Wright <simon@pushface.org> Date: Tue Nov 28 14:56:36 2023 +0100 Fix PR ada/111909 On Darwin, determine filesystem case sensitivity at runtime In gcc/ada/adaint.c(__gnat_get_file_names_case_sensitive), the current assumption for __APPLE__ is that file names are case-insensitive unless __arm__ or __arm64__ are defined, in which case file names are declared case-sensitive. The associated comment is "By default, we suppose filesystems aren't case sensitive on Windows and Darwin (but they are on arm-darwin)." This means that on aarch64-apple-darwin, file names are treated as case-sensitive, which is not the default case. The true default position is that macOS file systems are case-insensitive, iOS file systems are case-sensitive. Apple provide a header file <TargetConditionals.h> which permits a compile-time check for the compiler target (e.g. OSX vs IOS); if TARGET_OS_IOS is defined as 1, this is a build for iOS. 2023-11-22 Simon Wright <simon@pushface.org> gcc/ada/ PR ada/111909 * adaint.c (__gnat_get_file_names_case_sensitive): Split out the __APPLE__ check and remove the checks for __arm__, __arm64__. For Apple, file names are by default case-insensitive unless TARGET_OS_IOS is set. Signed-off-by: Simon Wright <simon@pushface.org>
next prev parent reply other threads:[~2023-11-28 16:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-21 15:22 [Bug ada/111909] New: " simon at pushface dot org 2023-10-22 1:20 ` [Bug ada/111909] " egallager at gcc dot gnu.org 2023-10-30 14:00 ` egallager at gcc dot gnu.org 2023-11-28 16:48 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-13 14:56 ` simon at pushface dot 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-111909-4-HoWyXPEhfs@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).