This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Fix -save-temps from clobbering input file@apple.com
- To: Ira Ruben <ira at apple dot com>
- Subject: Re: [PATCH] Fix -save-temps from clobbering input file@apple.com
- From: Dale Johannesen <dalej at apple dot com>
- Date: Tue, 30 Oct 2001 11:40:57 -0800
- Cc: Dale Johannesen <dalej at apple dot com>, degger at fhm dot edu, gcc-patches at gcc dot gnu dot org
On Tuesday, October 30, 2001, at 11:18 AM, Ira Ruben wrote:
> At 4:34 PM +0100 10/30/01, degger@fhm.edu wrote:
>
>> On 30 Oct, Stan Shebs wrote:
>>
>>> Won't help you on a Mac, where foo.s and foo.S refer to the same
>>> file usually.
>>
>> Please define "Mac", I assume that MacOS X with UFS filesystem
>> is casesensitive.
> Mac OSX supports both HFS+ and UFS. I think most of our
> users generally use HFS+.
Yes. Legacy OS9 ("Classic") software will not handle UFS[*], so
HFS+ is the recommended and usual filesystem. It's not
case sensitive. As more apps become available on native OSX,
this may change, but the OS9 legacy is going to be with Apple
for a while yet.
[*] I have not tried this personally, but that's what the
installer says.
<ira> But that isn't the issue. IMO, the compiler never has a
<ira> "right" to implicitly clobber user files.
OTOH, I frequently run the compiler more than once with -S,
and the behavior I expect, and get, is that the new .s file
overwrites the previous one. The compiler cannot readily
tell whether an existing .s file is a user file or left
around from a previous run of the compiler.