Displaying 10 results from an estimated 10 matches for "0.00135".
Did you mean:
0.0013
2010 Jul 22
0
[LLVMdev] fp Question
On Jul 22, 2010, at 4:18 PMPDT, Reza Yazdani wrote:
> Hi,
>
> I ran Spec2006 with -O4. All integer benchmarks passed, but only 8
> out 17 of floating point benchmarks passed. Is this normal or I
> made a mistake in my build?
Hi Reza. Somebody on Linux should answer, but I don't think it's
normal. You may have checked out the source at a moment when it had a
bug
2010 Jul 22
3
[LLVMdev] fp Question
Hi,
I ran Spec2006 with -O4. All integer benchmarks passed, but only 8 out 17
of floating point benchmarks passed. Is this normal or I made a mistake in
my build?
Reza
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100722/4c4a81a9/attachment.html>
2010 Jul 23
3
[LLVMdev] fp Question
Following is the list of fp benchmarks that fail. They all pass with -O3,
but some fail with -O4. I did the test run.
Thanks,
Reza
Estimated Estimated
Base Base Base Peak Peak Peak
Benchmarks Ref. Run Time Ratio Ref. Run Time Ratio
-------------- ------ --------- ---------
2010 Jul 23
0
[LLVMdev] fp Question
433.milc, 447.deall, and 450.soplex are run as part of the nightly
tests on Darwin (=MacOSX) in a way that closely approximates -O4.
They are working there. I am inclined to suspect gold given that they
work at -O3. Can a Linux person comment?
On Jul 23, 2010, at 10:19 AMPDT, Reza Yazdani wrote:
> Following is the list of fp benchmarks that fail. They all pass with
> -O3, but
2007 Dec 07
1
Adding a subset to a glm messes up factors?
Hi everyone,
I have a problem with running a glm using a subset of my data. Whenever I choose a subset, in the summary the factors arent shown (as if the variable was a continuous variable). If I dont use subsets then all the factors are shown. I have copied the output from summary for both cases.
Thanks for the help,
Muri
> model<-glm(log(cpue)~year,family=gaussian)
Call:
glm(formula =
2012 Aug 22
1
Error in if (n > 0)
I've searched the Web with Google and do not find what might cause this
particular error from an invocation of cenboxplot:
cenboxplot(cu.t$quant, cu.t$ceneq1, cu.t$era, range=1.5, main='Total
Recoverable Copper', ylab='Concentration (mg/L)', xlab='Time Period')
Error in if (n > 0) (1L:n - a)/(n + 1 - 2 * a) else numeric() :
argument is of length zero
I do
2011 Aug 20
4
I have a problem with R!!
Dear all
i?m working with a program i?ve made in R (using functions that others
created)
to run my program i need a sample. if i generate the sample using for
example, rnorm(n, mu, sigma) i have no problem
but if i obtain a sample from a column in excel and i copy it, the program
says that there is a mistake: it says "Error en `[.data.frame`(data,
indices) : undefined columns
2006 Apr 03
5
Strange Problem with ActionController (I think)
I''m working through the Agile Depot example
I have no idea what I did, but when I try and delete something from the
web page I get this error on the log.
Processing AdminController#destroy (for 127.0.0.1 at 2006-04-02
22:28:06) [GET]
Session ID: 4371bd7ca2cb5ec5e08e60a7590df90a
Parameters: {"action"=>"destroy", "id"=>"5",
2007 Feb 24
1
Woolf's test, Odds ratio, stratification
Just a general question concerning the woolf test (package vcd), when we have
stratified data (2x2 tables) and when the p.value of the woolf-test is
below 0.05 then we assume that there is a heterogeneity and a common odds
ratio cannot be computed?
Does this mean that we have to try to add more stratification variables
(stratify more) to make the woolf-test p.value insignificant?
Also in the
2005 May 17
6
RPC error logging in to PDC on Win-64
I've upgraded one of my client boxes to Windows 64 bit edition but now it cannot login to the Samba PDC, instead it gives a RPC error after entering the password. The Win32 boxes can still login fine.
I can get accounts without admin rights to login but those with the rights are given a message stating "The system cannot log you on due to the following error:
A remote procedure call