search for: run_opt

...ers can be more powerful (e.g. verify-uselistorder or `clang -verify`). #ifdef IR define void @func() { entry: ret } #else /* IR */ #include "compiledtestboilerplate.h" TEST(TestSuiteName, TestName) { unique_ptr<Module> Output = run_opt(__FILE__, "IR", "-passes=loop-vectorize"); /* Check Output */ } #endif /* IR */ That is, input IR and check code are in the same file. The run_opt command is a replica of main() from the opt tool, so any command line arguments (passes with legacy or new passma...

...t part -------------- Index: External/SPEC/CFP2000/177.mesa/Makefile =================================================================== --- External/SPEC/CFP2000/177.mesa/Makefile (revision 92115) +++ External/SPEC/CFP2000/177.mesa/Makefile (working copy) @@ -4,7 +4,7 @@ ifdef LARGE_PROBLEM_SIZE RUN_OPTIONS := -frames 500 else -RUN_OPTIONS := -frames 100 +RUN_OPTIONS := -frames 10 endif RUN_OPTIONS += -meshfile mesa.in -ppmfile mesa.ppm

...tion. Note that different problem inputs (test/ref/train) are not different compile-time options, they are different input files and command line arguments. If you look at the LLVM llvm-test makefiles, this information is also encoded. From the 126.gcc makefile, for example, you'll see: RUN_OPTIONS := -quiet -funroll-loops -fforce-mem -fcse-follow-jumps -fcse-skip-blocks -fexpensive-optimizati ons -fstrength-reduce -fpeephole -fschedule-insns -finline-functions -fschedule-insns2 -O -o - ifeq ($(RUN_TYPE),test) STDIN_FILENAME = cccp.i STDOUT_FILENAME = cccp.s else STDIN_FILENAME = amptj...

Does anyone know the "standard" commandline to compile and run spec95 benchmarks ? I found some scripts in llvm test suite (External/SPEC/CINT95), but I am not sure if they are the *default ref* configurations. <Some of them seem to use smaller problem sizes.> SPEC95 was retired many years ago, so few people around me know how to compile and run them. I am building from

Some of the run commandlines don't seem to be the *default ref* configuration. For instance, in 099.go, what's in the script is: LEVEL = ../../../.. BM=099.go ifeq ($(RUN_TYPE),test) STDIN_FILENAME = /dev/null STDOUT_FILENAME = null.out RUN_OPTIONS = 40 19 else STDIN_FILENAME = 2stone9.in STDOUT_FILENAME = 2stone9.out RUN_OPTIONS = 50 9 endif include ../../Makefile.spec95 Makefile (END) which suggests the compiling command: gcc -DSPEC_CPU95 -O2 -o spec_go g2.c g22.c g23.c g25.c g26.c g27a.c g27b.c g28.c g29.c g2eye.c g2jlib2.c...

...without @@ -109,44 +109,55 @@ struct backend *backend; static char *random_fifo_dir = NULL; static char *random_fifo = NULL; -enum { HELP_OPTION = CHAR_MAX + 1 }; +enum { + HELP_OPTION = CHAR_MAX + 1, + DUMP_CONFIG_OPTION, + DUMP_PLUGIN_OPTION, + EXIT_WITH_PARENT_OPTION, + FILTER_OPTION, + RUN_OPTION, + SELINUX_LABEL_OPTION, + TLS_OPTION, + TLS_CERTIFICATES_OPTION, + TLS_VERIFY_PEER_OPTION, +}; static const char *short_options = "e:fg:i:nop:P:rst:u:U:vV"; static const struct option long_options[] = { - { "help", 0, NULL, HELP_OPTION }, - { "dump-config...

...see that they're identical. I'm not sure if there is an option to run the program in sequential mode (if there is, the test will pass), but if not, the simplest way to fix the diff is to sort the reference_output and the program's output on execution. Adding "| sort" to the RUN_OPTIONS didn't have the desired effect (that was a long shot, anyway), does anyone know of a way to sort the output of a program on those Makefiles? Maybe a rule that can be intermediary of the final rule (I'm guessing $PROGRAM) that I can add a few steps before the diff? cheers, --renato ----...

...ain) are not >> different compile-time options, they are different input files and command >> line arguments. If you look at the LLVM llvm-test makefiles, this >> information is also encoded. From the 126.gcc makefile, for example, >> you'll see: >> >> RUN_OPTIONS := -quiet -funroll-loops -fforce-mem -fcse-follow-jumps >> -fcse-skip-blocks -fexpensive-optimizati >> ons -fstrength-reduce -fpeephole -fschedule-insns -finline-functions >> -fschedule-insns2 -O -o - >> >> ifeq ($(RUN_TYPE),test) >> STDIN_FILENAME = cccp....

v1 was here: https://www.redhat.com/archives/libguestfs/2018-November/msg00147.html v2: - Use stdbool for booleans. - Use __attribute__((format(printf))). - Don't abort on invalid options, exit with failure instead. - Preserve long/short option choices in the output. - Add '=' in long option output, ie. always use --longopt=arg. - Add "--" parameter

v1 was here: https://www.redhat.com/archives/libguestfs/2018-November/msg00147.html v2 was here: https://www.redhat.com/archives/libguestfs/2018-November/msg00152.html v3: - Use optarg != NULL as a sentinel for has_arg. - Moved some variable decls into the inner loop. - Make nbdkit wrapper depend on config.status, so if srcdir or builddir changes then we rebuild the wrapper. It

...cal. > > I'm not sure if there is an option to run the program in sequential mode > (if there is, the test will pass), but if not, the simplest way to fix the > diff is to sort the reference_output and the program's output on execution. > > Adding "| sort" to the RUN_OPTIONS didn't have the desired effect (that > was a long shot, anyway), does anyone know of a way to sort the output of a > program on those Makefiles? Maybe a rule that can be intermediary of the > final rule (I'm guessing $PROGRAM) that I can add a few steps before the > diff? &g...

...revision/protXML/protXML_v6.xsd " summary_xml="interact-LFA1_C18_PME5R1.prot.xml"> <protein_summary_header reference_database="EColi_decoy_v3.0.fasta"> <program_details analysis="proteinprophet"> <proteinprophet_details occam_flag="Y" run_options="XML"> <protein_group group_number="1" probability="1.0000"> <protein protein_name="sp|P00004|CYC_HORSE" n_indistinguishable_proteins="1" probability="1.0000" percent_coverage="46.7" unique_stripped_pep...

This patch series solves the FreeBSD shebang problem in a completely different way, and a few other things besides. I propose that we replace ./nbdkit with a C program. The C program is a straightforward translation of the shell script. Some advantages of this approach are: - We can parse options in exactly the same way as the real program. - Use the more accurate ‘is_short_name’ test for

On 2 April 2013 21:20, Török Edwin <edwin+ml-debian at etorok.net> wrote: > You can pass all the filenames from the inputs/ directory directly on the > command-line, instead of specifying -r inputs/. > That way the order of scanning will be exactly the one specified on the > command-line. > Hum, I think I can fix that with Make... --renato -------------- next part

On Sun, 4 Sep 2005, Tanu Sharma wrote: > > I have a doubt. > > This is an excerpt of the raw report I get after running Spec benchmarks > through llvm-test.I am trying to calculate the program execution > time.Does the output result in bold corresponds to "lli time" in > Makefile.spec ? I am not interested in llc, jit or cbe.I simply need the > normal

On 04/02/2013 11:06 PM, Daniel Dunbar wrote: > On Tue, Apr 2, 2013 at 11:46 AM, Renato Golin <renato.golin at linaro.org <mailto:renato.golin at linaro.org>> wrote: > > On 2 April 2013 19:20, Daniel Dunbar <daniel at zuster.org <mailto:daniel at zuster.org>> wrote: > > What is it that makes the output of the program asynchronous? The output is

I have a doubt. This is an excerpt of the raw report I get after running Spec benchmarks through llvm-test.I am trying to calculate the program execution time.Does the output result in bold corresponds to "lli time" in Makefile.spec ? I am not interested in llc, jit or cbe.I simply need the normal bytecode and native code execution times after running my pass over them.I have modified

...DIR)/inputs/rtf-test/Doc22.rtf \ $(PROJ_SRC_DIR)/inputs/rtf-test/Doc2.rtf \ $(PROJ_SRC_DIR)/inputs/rtf-test/doc3.rtf \ $(PROJ_SRC_DIR)/inputs/rtf-test/docCLAMexe.rtf \ $(PROJ_SRC_DIR)/inputs/rtf-test/rtf1.rtf \ $(PROJ_SRC_DIR)/inputs/rtf-test/rtf-novirus.rtf RUN_OPTIONS = --debug --exclude-dir .svn --verbose -d$(PROJ_SRC_DIR)/dbdir -r $(INPUT) This is what Make generated for me on both machines: Output/clamscan.simple --debug --exclude-dir .svn --verbose \ -d/home/user/devel/llvm/test/test-suite/MultiSource/Applications/ClamAV/dbdir \ -r \ /h...

...extern bool no_sr; extern const char *port; diff --git a/server/options.h b/server/options.h index a69f413a..c74e0b8b 100644 --- a/server/options.h +++ b/server/options.h @@ -46,6 +46,7 @@ enum { FILTER_OPTION, LOG_OPTION, LONG_OPTIONS_OPTION, + MASK_HANDSHAKE_OPTION, NO_SR_OPTION, RUN_OPTION, SELINUX_LABEL_OPTION, @@ -74,6 +75,7 @@ static const struct option long_options[] = { { "ipaddr", required_argument, NULL, 'i' }, { "log", required_argument, NULL, LOG_OPTION }, { "long-options", no_argument, NUL...

This is similar to the recent --no-sr option - it's a change that is unlikely to ever be used except by someone testing whether a client is compliant to the protocol, but in that niche case, it can be quite handy (it's a lot nicer to be able to purposefully cripple a server from the command line than from a one-off compile, when testing if a client's fallback for a spec-compliant but