search for: responsefile_patch

Displaying 3 results from an estimated 3 matches for "responsefile_patch".

[LLVMdev] RFC: Adding an option to llvm-link to allow it to get a list of input bitcode file names from a file
2012 Oct 04
0
[LLVMdev] RFC: Adding an option to llvm-link to allow it to get a list of input bitcode file names from a file
On 21 September 2012 10:44, Liu, Yaxun (Sam) <Yaxun.Liu at amd.com> wrote: > I have no objection to that. Actually I am curious why it is disabled by default. > > If we enable ReadResponseFiles=true by default, we will automatically get support of response file (@file) in all llvm tools. The only issue I can think of is that some users may have file names starting with
[LLVMdev] RFC: Adding an option to llvm-link to allow it to get a list of input bitcode file names from a file
2012 Oct 04
1
[LLVMdev] RFC: Adding an option to llvm-link to allow it to get a list of input bitcode file names from a file
..."@". I don't think that is a likely problem. I agree with Nakamura, lets change the default. Do you have write access or do you need me to commit a patch? > Sam Cheers, Rafael -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ResponseFile_patch.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121004/2ef9c7d4/attachment.txt>
[LLVMdev] RFC: Adding an option to llvm-link to allow it to get a list of input bitcode file names from a file
2012 Sep 21
2
[LLVMdev] RFC: Adding an option to llvm-link to allow it to get a list of input bitcode file names from a file
I have no objection to that. Actually I am curious why it is disabled by default. If we enable ReadResponseFiles=true by default, we will automatically get support of response file (@file) in all llvm tools. The only issue I can think of is that some users may have file names starting with "@". Sam -----Original Message----- From: NAKAMURA Takumi [mailto:geek4civic at gmail.com]