Displaying 7 results from an estimated 7 matches for "readresponsefil".
Did you mean:
readresponsefiles
2012 Sep 21
2
[LLVMdev] patch to enable response file support in ParseCommandLineOptions
...=========
--- include/llvm/Support/CommandLine.h (revision 164408)
+++ include/llvm/Support/CommandLine.h (working copy)
@@ -42,7 +42,7 @@
//
void ParseCommandLineOptions(int argc, const char * const *argv,
const char *Overview = 0,
- bool ReadResponseFiles = false);
+ bool ReadResponseFiles = true);
//===----------------------------------------------------------------------===//
// ParseEnvironmentOptions - Environment variable option processing alternate
Sam
-------------- next part --------------
An HTML attachment w...
2012 Sep 22
0
[LLVMdev] patch to enable response file support in ParseCommandLineOptions
...64408)
>
> +++ include/llvm/Support/CommandLine.h (working copy)
>
> @@ -42,7 +42,7 @@
>
> //
>
> void ParseCommandLineOptions(int argc, const char * const *argv,
>
> const char *Overview = 0,
>
> - bool ReadResponseFiles = false);
>
> + bool ReadResponseFiles = true);
>
> //===----------------------------------------------------------------------===//
>
> // ParseEnvironmentOptions - Environment variable option processing alternate
>
> Sam
>
>
>
> __...
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]
Sent: Thursday,...
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 "@".
I don't think that is a likely problem. I agree with Nakamura, lets
change the default. Do you have...
2012 Sep 21
0
[LLVMdev] RFC: Adding an option to llvm-link to allow it to get a list of input bitcode file names from a file
Could we enable ReadResponseFiles=true by default?
2012/9/21 Liu, Yaxun (Sam) <Yaxun.Liu at amd.com>:
> Well, although cl::ParseCommandLineOptions contains support for @file. By default it is disabled, which is the case for llvm-link.
>
> To enable @file support in llvm-link, a small change is needed:
>
> --...
2012 Sep 20
2
[LLVMdev] RFC: Adding an option to llvm-link to allow it to get a list of input bitcode file names from a file
Well, although cl::ParseCommandLineOptions contains support for @file. By default it is disabled, which is the case for llvm-link.
To enable @file support in llvm-link, a small change is needed:
--- llvm-link.cpp.orig 2012-09-20 16:10:50.000000000 -0400
+++ llvm-link.cpp 2012-09-20 16:11:24.000000000 -0400
@@ -83,7 +83,7 @@
LLVMContext &Context = getGlobalContext();
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
...VMdev] 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 "@".
I don't think that is a likely problem. I agree with Nakamura, lets change the default. Do you have...