This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: About behavior of -save-temps=obj option on GCC 4.5
- From: Tadashi Koike <tadashiee at gmail dot com>
- To: Michael Meissner <meissner at linux dot vnet dot ibm dot com>, Richard Guenther <richard dot guenther at gmail dot com>, gcc at gcc dot gnu dot org
- Date: Sat, 3 Apr 2010 10:56:10 +0900
- Subject: Re: About behavior of -save-temps=obj option on GCC 4.5
- References: <1b0a845b1003200940r5e1d5245se19302e8b641f099@mail.gmail.com> <84fc9c001003200959n64e5c3d6w6755b06046196281@mail.gmail.com> <1b0a845b1003250733hdbcf822l8077892f9e3a5417@mail.gmail.com> <20100325152924.GA6569@hungry-tiger.westford.ibm.com> <s2m1b0a845b1004021848yc007b162v5dca8f6f5ff76e38@mail.gmail.com>
Sorry, I miss. follow it:
2010/4/3 Tadashi Koike <tadashiee@gmail.com>:
> Hi Mike,
>
> I'm sorry to spend a week to response your replay, and thank you
> for explanation of -save-temps=obj specifications.
>
>> I tend to agree with Richard, that if there are multiple source inputs, it
>> should be an error to use -save-temps=obj without the -c/-S option.
>
> I reached a true understanding, and this explanation should help
> my project.
>
This quotation is forgotten
>> Though it might be friendlier to allow:
>>
>> gcc -o dir/exe a.c b.c c.c
>>
>> and put the temp files in:
>>
>> dir/a.{s,i}
>> dir/b.{s,i}
>> dir/c.{s,i}
>>
>> But it would fail for doing:
>>
>> gcc -o exe dir1/a.c dir2/a.c
>>
>> where the names overlap. Let me look at it.
> Certainly this case is not god. In this case(= multiple input
> files that have same filename), compiling should became failure
> neither by -save-temps=cwd nor by -save-temps=obj. It is difficult ...
ãã:
Best regards,
Tadashi Koike