Displaying 15 results from an estimated 15 matches for "run_typ".
Did you mean:
run_type
2009 Dec 24
0
[LLVMdev] Problem in External/SPEC/CFP2000/177.mesa/Makefile ?
...ng unchecked fscanf on that "numbers" file.
>
> Is my version of spec wrong ?
What you say is true in the version I have.
> If not, can we apply the attached patch ?
I don't think it's ideal. There are 3 input sets, not 2, that's the
root of the problem:
ifndef RUN_TYPE
ifdef SMALL_PROBLEM_SIZE
RUN_TYPE := test
else
ifdef LARGE_PROBLEM_SIZE
RUN_TYPE := ref
else
RUN_TYPE := train
endif
endif
endif
100 is a fine value for "train". I think it's better to test both
variables in the mesa Makefile.
(IMO controlling a ternary variable with 2 booleans...
2009 Dec 24
2
[LLVMdev] Problem in External/SPEC/CFP2000/177.mesa/Makefile ?
Hello folks,
The makefile for 177.mesa says that for a small problem size, it will
get 100 frames. But in the spec sources I have, the test folder only
contains numbers for 10 frames:
$ speccpu2000/benchspec/CFP2000/177.mesa/data $ wc -l test/input/numbers
10 test/input/numbers
Generating 100 frames causes undefined behaviour because the program is
doing unchecked fscanf on that
2005 Sep 05
0
[LLVMdev] Doubt
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
2005 Sep 04
2
[LLVMdev] Doubt
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
2005 Jul 22
0
[LLVMdev] Need help on SPEC 95 "standard" commandlines
...ormation 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 = amptjp.i
STDOUT_FILENAME = amptjp.s
endif
Note that llvm-test compiles the benchmarks a file at a time (with -c),
not all at once.
-Chris
--
http://nondot.org/sabre/
http://llvm.org/
2005 Jul 22
2
[LLVMdev] Need help on SPEC 95 "standard" commandlines
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....
2005 Jul 22
2
[LLVMdev] Need help on SPEC 95 "standard" commandlines
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
2009 Sep 01
0
[LLVMdev] spec tests + PWD=
...env_pwd = getenv("PWD");
std::string Exec = "cd ";
Exec += env_pwd;
Perhaps I shouldn't have added it to Makefile.spec? At the least it
seems like it should probably move to the beginning of the command,
like this:
PWD=$(CURDIR) $(SPEC_SANDBOX) bugpoint-$(RUN_TYPE) $@ $(REF_IN_DIR) \
$(LBUGPOINT) -llc-safe ../$*.noopt-llvm.bc -std-compile-opts $
(OPTPASSES) \
David
On Aug 30, 2009, at 8:25 PM, Chris Lattner wrote:
> Hi David,
>
> It looks like you added the PWD= magic to Makefile.spec. It is
> preventing me from running bugpoint on...
2009 Aug 31
2
[LLVMdev] spec tests + PWD=
Hi David,
It looks like you added the PWD= magic to Makefile.spec. It is
preventing me from running bugpoint on the desktop, with errors like
this:
/Users/sabre/llvm/projects/llvm-test/External/SPEC/Sandbox.sh bugpoint-
train Output/176.gcc.bugpoint-opt /Users/sabre/cvs/benchmarks/
speccpu2000/benchspec/CINT2000/176.gcc/data/train/input/ \
2005 Jul 22
0
[LLVMdev] Need help on SPEC 95 "standard" commandlines
...> 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 = amptjp.i
>> STDOUT_FILENAME = amptjp.s
>> endif
>>
>> Note that llvm-test compiles the benchmarks a file at a time (with -c), not
>> all at once.
>&g...
2015 Mar 16
1
Problem with replication ("Fatal: -N parameter requires syncing with remote host")
...o work ok. However, I can't figure out the cause for
the error that I am seeing. I have looked into source code and found
where this error is triggered (line 834 in
doveadm/dsync/doveadm-dsync.c, inside Dovecot 2.2.9 source code), but I
am afraid that I don't understand the context (ctx->run_type ==
DSYNC_RUN_TYPE_LOCAL) and it would take me a lot of time to debug the
whole thing from the scratch. I've never looked into Dovecot internals
before, so it's all a mystery to me at this point.
I've tried stracing the process but the flow does not make sense to me,
I can't unders...
2016 Mar 24
2
[test-suite] r261857 - [cmake] Add support for arbitrary metrics
...IPT "${TESTSCRIPT}VERIFY: ${JOINED_ARGUMENTS}\n")
>>>>>>> endif()
>>>>>>> endmacro()
>>>>>>> +
>>>>>>> +macro(llvm_test_metric)
>>>>>>> + CMAKE_PARSE_ARGUMENTS(ARGS "" "RUN_TYPE;METRIC" "" ${ARGN})
>>>>>>> + if(NOT DEFINED TESTSCRIPT)
>>>>>>> + set(TESTSCRIPT "" PARENT_SCOPE)
>>>>>>> + endif()
>>>>>>> + # ARGS_UNPARSED_ARGUMENTS is a semicolon-separated list....
2007 Dec 02
2
[Bug 13491] New: 5min.com player causes assertion
...n_return=0x0,
instance_and_params=0x7fffbf5d9ac0) at gsignal.c:2478
tmp = <value optimized out>
handler = (Handler *) 0x3a2aef0
accumulator = (SignalAccumulator *) 0x0
emission = {next = 0x0, instance = 0x1bfa750, ihint = {
signal_id = 362, detail = 0, run_type = G_SIGNAL_RUN_LAST},
state = EMISSION_RUN, chain_type = 29300208}
class_closure = (GClosure *) 0x2976be0
handler_list = (Handler *) 0x3a2aef0
return_accu = (GValue *) 0x0
accu = {g_type = 0, data = {{v_int = 0, v_uint = 0, v_long = 0,
v_ulong = 0, v_int64...
2016 Mar 24
0
[test-suite] r261857 - [cmake] Add support for arbitrary metrics
...PT}VERIFY: ${JOINED_ARGUMENTS}\n")
>>>>>>>> endif()
>>>>>>>> endmacro()
>>>>>>>> +
>>>>>>>> +macro(llvm_test_metric)
>>>>>>>> + CMAKE_PARSE_ARGUMENTS(ARGS "" "RUN_TYPE;METRIC" "" ${ARGN})
>>>>>>>> + if(NOT DEFINED TESTSCRIPT)
>>>>>>>> + set(TESTSCRIPT "" PARENT_SCOPE)
>>>>>>>> + endif()
>>>>>>>> + # ARGS_UNPARSED_ARGUMENTS is a semicolon...
2016 Mar 24
1
[test-suite] r261857 - [cmake] Add support for arbitrary metrics
...ARGUMENTS}\n")
>>>>>>>>> endif()
>>>>>>>>> endmacro()
>>>>>>>>> +
>>>>>>>>> +macro(llvm_test_metric)
>>>>>>>>> + CMAKE_PARSE_ARGUMENTS(ARGS "" "RUN_TYPE;METRIC" "" ${ARGN})
>>>>>>>>> + if(NOT DEFINED TESTSCRIPT)
>>>>>>>>> + set(TESTSCRIPT "" PARENT_SCOPE)
>>>>>>>>> + endif()
>>>>>>>>> + # ARGS_UNPARSED_ARGUMENT...