[LLVMdev] [llvm-commits] patch to enable response file support in ParseCommandLineOptions

[Matt Beaumont-Gay]

Can we call this a "parameters file"? I find "response file" to be non-obvious.

On Tue, Oct 2, 2012 at 8:18 AM, Liu, Yaxun (Sam) <Yaxun.Liu at amd.com> wrote:
> Thanks Chris for the comment.
>
>
>
> Since there is no objection, I attached a new patch which enables response
> file support and removes the argument for controlling/disabling response
> file support. The patch also contains a simple test. I did regression check
> and there are no regressions.
>
>
>
> + llvmdev
>
>
>
> Sam
>
>
>
> From: Chris Lattner [mailto:clattner at apple.com]
> Sent: Sunday, September 30, 2012 2:20 PM
> To: Liu, Yaxun (Sam)
> Cc: llvm-commits at cs.uiuc.edu
> Subject: Re: [llvm-commits] patch to enable response file support in
> ParseCommandLineOptions
>
>
>
>
>
> On Sep 21, 2012, at 2:07 PM, "Liu, Yaxun (Sam)" <Yaxun.Liu at amd.com> wrote:
>
>
>
> Hi,
>
>
>
> I am sending a patch to enable response file support in
> ParseCommandLineOptions. With this change, all llvm tools will support
> response file. This helps overcome the command line length limit which we
> encountered recently.
>
>
>
>
>
> This seems fine to me.  Is there any reason we *wouldn't* want a tool to
> read response files?  If all tools should handle it, the argument should
> just go away.
>
>
>
> -Chris
>
>
>
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>