From: Mike Frysinger <vapier@gentoo.org>
To: Matt Rice <ratmice@gmail.com>
Cc: gdb-patches@sourceware.org, Jie Zhang <jie@codesourcery.com>
Subject: Re: [PATCH] sim: tests: support .S files
Date: Mon, 15 Mar 2010 07:09:00 -0000 [thread overview]
Message-ID: <201003150308.58613.vapier@gentoo.org> (raw)
In-Reply-To: <8ba6bed41003141743n79e501b7n11d3d20cdb45f356@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 958 bytes --]
On Sunday 14 March 2010 20:43:45 Matt Rice wrote:
> On Sun, Mar 14, 2010 at 2:03 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> > Rather than requiring all sim tests to be preprocessed .s files, add
> > support for .S files so we can easily write code using normal CPP
> > defines/macros.
>
> not that I actually care about any such targets, but wouldn't this
> just fall over on a case insentive filesystem?
case insensitive is not the same thing as case preserving. assuming you're
referring to the main ones (windows or OS X default), they're both case
preserving. so files checked out as foo.s will stay as foo.s. the source
code changes do string matches which have on relation at all to the file
system the files reside upon.
so no, i dont think this change will make any difference at all to such
systems. otherwise you'd already see problems with the packages that utilize
source files based on extension case.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-03-15 7:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 22:02 Mike Frysinger
2010-03-15 0:43 ` Matt Rice
2010-03-15 1:46 ` Jie Zhang
2010-03-15 7:09 ` Mike Frysinger [this message]
2010-03-15 10:54 ` Matt Rice
2010-03-19 20:12 ` Mike Frysinger
2010-03-15 20:17 ` DJ Delorie
2011-03-14 8:20 Mike Frysinger
2011-03-14 12:32 ` Pedro Alves
2011-03-14 21:06 ` Mike Frysinger
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=201003150308.58613.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=jie@codesourcery.com \
--cc=ratmice@gmail.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