Displaying 4 results from an estimated 4 matches for "ref_in_dir".
2009 Sep 01
0
[LLVMdev] spec tests + PWD=
...nv("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 the desktop, with...
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 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