From: Jan Beulich <jbeulich@suse.com>
To: "Clément Chigot" <chigot@adacore.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH 1/4] gas/testsuite: adjust a test for case insensitive file systems
Date: Tue, 21 Feb 2023 10:28:38 +0100 [thread overview]
Message-ID: <28629025-45c2-df6f-b3fa-beb3a6c6ca63@suse.com> (raw)
In-Reply-To: <CAJ307EgWKBO5Sys+Y_F6YYbEMSBO31w+VHDgtn1NLsfc9J6=7w@mail.gmail.com>
On 21.02.2023 10:02, Clément Chigot wrote:
> On Tue, Feb 21, 2023 at 9:40 AM Jan Beulich <jbeulich@suse.com> wrote:
>> Other than that I'm okay with the change, albeit I'd like to
>> point out that libiberty's filename_cmp() isn't really international-
>> ready (works reliably only for ASCII), and hence there are apparently
>> bigger issues here.
>
> It's not linked with internationalization, here. The issue is because
> mingw file system is case insensitive, thus line.s and Line.s are
> supposed to be the same file.
> Looking at filename_cmp, it's already handling that.
Sure, and I was pointing this out as a related issue, yet unrelated
to your concern. Clearly in the testsuite we can limit ourselves to
all-ASCII names. But that may not hold for people actually using
binutils on case-insensitive file systems.
Jan
prev parent reply other threads:[~2023-02-21 9:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 8:22 Clément Chigot
2023-02-20 8:22 ` [PATCH 2/4] ld/testsuite: don't output to /dev/null on mingw hosts Clément Chigot
2023-02-20 10:59 ` Alan Modra
2023-02-20 8:22 ` [PATCH 3/4] ld/testsuite: adjust to Windows path separator Clément Chigot
2023-02-20 11:00 ` Alan Modra
2023-02-20 8:22 ` [PATCH 4/4] ld/testsuite: handle Windows drive letter in a noinit test Clément Chigot
2023-02-20 11:02 ` Alan Modra
2023-02-20 10:52 ` [PATCH 1/4] gas/testsuite: adjust a test for case insensitive file systems Alan Modra
2023-02-21 8:30 ` Jan Beulich
2023-02-21 8:40 ` Jan Beulich
2023-02-21 9:02 ` Clément Chigot
2023-02-21 9:28 ` Jan Beulich [this message]
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=28629025-45c2-df6f-b3fa-beb3a6c6ca63@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=chigot@adacore.com \
/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).