Displaying 18 results from an estimated 18 matches for "0.1400".
Did you mean:
0.0400
2012 Apr 04
1
[LLVMdev] scalar replacement of aggregates slower?
I just upgraded our optimizer to LLVM 3.0 from 2.8 and noticed that the
scalar replacement of aggregates pass takes a lot longer for some code.
Has there been a performance regression in this pass, or does it do more
work?
LLVM 3.0:
Total Execution Time: 1.0600 seconds (1.0526 wall clock)
---User Time--- --System Time-- --User+System-- ---Wall
Time--- --- Name ---
0.5100
2009 Sep 20
2
missing level of a nested factor results in an NA in lm output
Hello All,
I have posted to this list before regarding the same issue so I
apologize for the multiple e-mails. I am still struggling with this
issue so I thought I'd give it another try. This time I have included
reproducible code and a subset of the data I am analyzing.
I am running an ANOVA with three factors: GROUP (5 levels), FEATURE
(2 levels), and PATIENT (2 levels), where
2008 May 06
4
General Plotting Question
f <- (structure(list(X = structure(96:97, .Label = c("119DAmm", "119DN",
"119DNN", "119DO", "119DOC", "119Flow", "119Nit", "119ON", "119OPhos",
"119OrgP", "119Phos", "119TKN", "119TOC", "148DAmm", "148DN",
"148DNN", "148DO",
2005 Jul 01
0
[LLVMdev] execution time of bytecode and native
On Thu, 30 Jun 2005, Tanu Sharma wrote:
> I am compiling SPEC 2000 benchmarks with llvm .Got stuck with
> calculating "execution time" of all the .bc and native files.
>
> The log for nightly test itself gives execution times but I am passing
> the bytecode files to my pass which gives another bytecode file.I have
> to calculate execution time of such bytecode and
2005 Jul 01
1
[LLVMdev] execution time of bytecode and native
Hello ,
I am compiling SPEC 2000 benchmarks with llvm .Got stuck with calculating "execution time" of all the .bc and native files.
The log for nightly test itself gives execution times but I am passing the bytecode files to my pass which gives another bytecode file.I have to calculate execution time of such bytecode and native files as well.If i simply do this:
time lli
2003 May 30
2
Coefficients: (20 not defined because of singularities)
Hello,
I am trying to run a linear regression analysis on my data set. For some
reason most variables are removed due to singularities.
My linear regression looks this way (I am using only partial data, which
is selected by flags):
fm<-lm(log(cplex6.time..sec..[flags]) ~ cplex6.cities[flags] +
log(1/features.meanOver.frust[flags]) +
log(1/features.meanOver.minDist[flags]) +
[...]
2005 Jul 21
1
[LLVMdev] execution time of bytecode and native
Hello All,
Thanks for the reply.I can generate the reports by compiling Spec through llvm, but that couldn't resolve my problem.
I m trying to determine execution time for the bytecode and native files , which are obtained as a result of running my pass over the original bytecode .I am running these experiments on spec benchmark.
In SPEC we have command line tools such as runspec where
2009 Oct 20
1
[LLVMdev] 2.6 pre-release2 ready for testing
G'Day Tanya,
Is it too late to bring in the following patches to fix some major
brokenness in the AuroraUX tool chain for 2.6?
http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Driver/Tools.cpp?r1=84468&r2=84469&view=diff&pathrev=84469
http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Driver/Tools.cpp?r1=84265&r2=84266&view=diff&pathrev=84266
2009 Oct 20
0
[LLVMdev] 2.6 pre-release2 ready for testing
Hi Tanya,
> 1) Compile llvm from source and untar the llvm-test in the projects
> directory (name it llvm-test or test-suite). Choose to use a
> pre-compiled llvm-gcc or re-compile it yourself.
I compiled llvm and llvm-gcc with separate objects directories.
Platform is x86_64-linux-gnu.
> 2) Run make check, report any failures (FAIL or unexpected pass). Note
> that you need to
2001 Nov 28
1
Help with ICC
Hello, R-folks:
Here is a statement I use to make a data frame:
iccdata <- data.frame(i=rep(1:10,rep(2,10)),j=rep(1:2,10),
x=c(0.35011,0.11989,0.13081,0.09919,0.16000,0.12000,0.00000,0.00000,
0.44023,0.32977,2.67081,2.63919,0.09050,0.03950,0.44019,0.30981,0.59000,
0.57000,4.03000,3.77000))
Then here are the data:
> iccdata
i j x
1 1 1 0.35011
2 1 2 0.11989
3 2 1 0.13081
4
2009 Oct 20
1
[LLVMdev] 2.6 pre-release2 ready for testing
On Oct 20, 2009, at 6:02 AM, Duncan Sands wrote:
> Hi Tanya,
>
>> 1) Compile llvm from source and untar the llvm-test in the projects
>> directory (name it llvm-test or test-suite). Choose to use a pre-
>> compiled llvm-gcc or re-compile it yourself.
>
> I compiled llvm and llvm-gcc with separate objects directories.
> Platform is x86_64-linux-gnu.
>
Ok.
2007 Sep 18
0
[LLVMdev] 2.1 Pre-Release Available (testers needed)
Hi,
LLVM 2.1-pre1 test results:
Linux (SUSE) on x86 (P4)
Release mode, but with assertions enabled
LLVM srcdir == objdir
# of expected passes 2250
# of expected failures 5
I ran the llvm-test suite on my desktop while I was also working on that PC,
so don't put too much trust in the timing info. Especially during the "spiff"
test the machine was swapping
2009 Oct 17
12
[LLVMdev] 2.6 pre-release2 ready for testing
LLVMers,
2.6 pre-release2 is ready to be tested by the community.
http://llvm.org/prereleases/2.6/
If you have time, I'd appreciate anyone who can help test the release.
To test llvm-gcc:
1) Compile llvm from source and untar the llvm-test in the projects
directory (name it llvm-test or test-suite). Choose to use a pre-
compiled llvm-gcc or re-compile it yourself.
2) Run make check,
2005 Jun 30
3
[LLVMdev] X86AsmPrinter + MASM and NASM backends
Some wheird problem, Target/X86 builds okay now.
But there seems to be another problem with the Cygwin build :-
make[4]: Entering directory `/usr/build/llvm/lib/Target/SparcV9/ModuloScheduling'
llvm[4]: Compiling ModuloSchedulingSuperBlock.cpp for Debug build
/usr/src/llvm/lib/Target/SparcV9/ModuloScheduling/ModuloSchedulingSuperBlock.cpp
: In member function `virtual bool
2007 Dec 21
5
[LLVMdev] Status of Elsa->LLVM
I'm a little further along now. I've started to put together a simple
driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think
it works).
The file being compiled is a "printf" function. Here are timing results
for optimized and unoptimized runs:
[~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i -time-actions
Adding test/ofmt.i as a preprocessed C file
2012 Feb 19
2
[LLVMdev] Problem While Running Test Suite
Hello;
I was able to build and install llvm(3.0) under Ubuntu 11.10 (using the
./configure script found under llvm source, and then make and make
install). While configuring, I gave --prefix as a directory where I would
like llvm to be installed. I did not give --with-llvmgccdir and the
--enable-optimized argument to configure. Because 3.0 doesn't come with
llvmgcc source/binaries and I
2009 Feb 07
11
[LLVMdev] 2.5 Pre-release1 available for testing
LLVMers,
The 2.5 pre-release is available for testing:
http://llvm.org/prereleases/2.5/
If you have time, I'd appreciate anyone who can help test the release.
Please do the following:
1) Download/compile llvm source, and either compile llvm-gcc source or
use llvm-gcc binary (please compile llvm-gcc with fortran if you can).
2) Run make check, send me the testrun.log
3) Run "make
2007 Sep 15
22
[LLVMdev] 2.1 Pre-Release Available (testers needed)
LLVMers,
The 2.1 pre-release (version 1) is available for testing:
http://llvm.org/prereleases/2.1/version1/
I'm looking for members of the LLVM community to test the 2.1
release. There are 2 ways you can help:
1) Download llvm-2.1, llvm-test-2.1, and the appropriate llvm-gcc4.0
binary. Run "make check" and the full llvm-test suite (make
TEST=nightly report).
2) Download