Displaying 8 results from an estimated 8 matches for "positionaleatsargs".
2018 Jul 31
4
bugpoint --tool-args and --safe-tool-args
...above but it's a bit painful.
>>
>> Has anyone tried to use bugpoint like this before? Any tips?
>
> I've occasionally used shell script wrappers when I couldn't get bugpoint command-line parsing to work the way I wanted it to.
>
> Looking at CommandLine.rst, PositionalEatsArgs is supposed to allow specifying something like the command you wrote, but I'm not sure it ever worked correctly; nothing other than bugpoint uses it, as far as I can tell.
>
> -Eli
>
> --
> Employee of Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a...
2018 Jul 31
2
bugpoint --tool-args and --safe-tool-args
I have a failing test and bugpoint would be the perfect tool to help
narrow it down.
llc is the failing tool. It fails with one set of options and passes
with another. I was hoping to use bugpoint like this:
bugpoint -safe-llc -run-llc <testcase> -tool-args <failing args> -safe-tool-args <passing args>
Unfortunately, this doesn't seem to be possible. According to the
2013 May 07
1
[LLVMdev] CommandLine: using cl::Positional with enum
...odify "OptionsLevelOptionsLevel" including the cl::Required flagThe error is now:"option: does not allow a value! option1 specified.option: must be specified at least once!option: must be specified at least once!option: must be specified at least once!"Then, I decided to use cl::PositionalEatsArgs instead of cl::ConsumeAfter. Then, this is the result:"option: does not allow a value! option1 specified."But, this time, the program continues. However, if I run "myTool option3 arg1 file.cpp --" it gives me a different problem:"warning: ../build/arg1: 'linker' inp...
2013 May 08
0
[LLVMdev] CommandLine: using cl::Positional with enum
...quot;OptionsLevelOptionsLevel" including the cl::Required flagThe error is now:
"option: does not allow a value! option1 specified.
option: must be specified at least once!
option: must be specified at least once!
option: must be specified at least once!"
Then, I decided to use cl::PositionalEatsArgs instead of cl::ConsumeAfter. Then, this is the result:
"option: does not allow a value! option1 specified."
But, this time, the program continues. However, if I run "myTool option3 arg1 file.cpp --" it
gives me a different problem:
"warning: ../build/arg1: 'linker...
2013 May 08
0
[LLVMdev] CommandLine: using cl::Positional with enum
...onsLeve
>>
> lOptionsLevel" including the cl::Required flagThe error is now:"option: does not allow a value! option1 specified.option: must be specified at least once!option: must be specified at least once!option: must be specified at least once!"Then, I decided to use cl::PositionalEatsArgs instead of cl::ConsumeAfter. Then, this is the result:"option: does not allow a value! option1 specified."But, this time, the program continues. However, if I run "myTool option3 arg1 file.cpp --" it gives me a different problem:"warning: ../build/arg1: 'linker' inp...
2013 May 10
0
[LLVMdev] CommandLine: using cl::Positional with enum
...onsLeve
>>
> lOptionsLevel" including the cl::Required flagThe error is now:"option: does not allow a value! option1 specified.option: must be specified at least once!option: must be specified at least once!option: must be specified at least once!"Then, I decided to use cl::PositionalEatsArgs instead of cl::ConsumeAfter. Then, this is the result:"option: does not allow a value! option1 specified."But, this time, the program continues. However, if I run "myTool option3 arg1 file.cpp --" it gives me a different problem:"warning: ../build/arg1: 'linker' inp...
2013 May 12
0
[LLVMdev] CommandLine: using cl::Positional with enum
...t;
> lOptionsLevel" including the cl::Required flagThe error is now:"option: does
> not allow a value! option1 specified.option: must be specified at least
> once!option: must be specified at least once!option: must be specified at
> least once!"Then, I decided to use cl::PositionalEatsArgs instead of
> cl::ConsumeAfter. Then, this is the result:"option: does not allow a value!
> option1 specified."But, this time, the program continues. However, if I run
> "myTool option3 arg1 file.cpp --" it gives me a different problem:"warning:
> ../build/arg1:...
2013 May 14
0
[LLVMdev] CommandLine: using cl::Positional with enum
...ionsLevel" including the cl::Required flagThe error is now:"option: does
>> not allow a value! option1 specified.option: must be specified at least
>> once!option: must be specified at least once!option: must be specified at
>> least once!"Then, I decided to use cl::PositionalEatsArgs instead of
>> cl::ConsumeAfter. Then, this is the result:"option: does not allow a value!
>> option1 specified."But, this time, the program continues. However, if I run
>> "myTool option3 arg1 file.cpp --" it gives me a different problem:"warning:
>>...