Displaying 3 results from an estimated 3 matches for "test_args".
2019 Jun 07
7
Bugpoint Redesign
...nd a nonzero value when otherwise. Leaving the user the freedom to
determine what is and isn’t interesting to the tool, and thus, streamlining
the process of reducing a test-case.
If the test accepts any arguments (excluding the input ll/bc file), they
are given via the following flag:
`--test_args=<test_arguments>`
If unspecified, the test is run as given. It’s worth noting that the input
file would be passed as a parameter to the test, similar how
`-compile-custom` currently operates.
### Implementation
The tool would behave similar to CReduce’s functionality in that it would
have a...
2019 Jun 11
2
Bugpoint Redesign
...nd a nonzero value when otherwise. Leaving the user the freedom to determine what is and isn’t interesting to the tool, and thus, streamlining the process of reducing a test-case.
If the test accepts any arguments (excluding the input ll/bc file), they are given via the following flag:
`--test_args=<test_arguments>`
If unspecified, the test is run as given. It’s worth noting that the input file would be passed as a parameter to the test, similar how `-compile-custom` currently operates.
### Implementation
The tool would behave similar to CReduce’s functionality in that it would have a...
2016 Aug 18
5
[PATCH v2 0/4] New getprogname module
Hi,
as discussed in [1], this series adds a new getprogname module.
All it does is providing a getprogname function, much like what is
found on e.g. *BSD systems, and using it in gnulib instead of progname.
Also, using it explicitly by modules avoids gnulib users the need of
either use the progname module (GPL), or to provide program_name (and
call set_program_name manually, which is not always