Displaying 6 results from an estimated 6 matches for "0.0634".
Did you mean:
0.0034
2010 Mar 17
1
constrOptim - error: initial value not feasible
Hello at all,
working with a dataset I try to optimize a non-linear function with
constraint.
test<-read.csv2("C:/Users/Herb/Desktop/Opti/NORM.csv")
fkt<- function(x){
a<-c(0)
s<-c(0)
#Minimizing square error
for(j in 1:107){
s<-(test[j,2] - (x[1] * test[j,3]) - (x[2] * test[j,4]) - (x[3]*test[j,5]) -
(x[4]*test[j,6]) - (x[5]*test[j,7]))^2
a<- a+s}
a<-as.double(a)
2011 Dec 01
1
[LLVMdev] [llvm-testresults] bwilson__llvm-gcc_PROD__i386 nightly tester results
Are these 225 compile time regressions real? It sure looks bad!
Ciao, Duncan.
On 01/12/11 09:39, llvm-testresults at cs.uiuc.edu wrote:
>
> bwilson__llvm-gcc_PROD__i386 nightly tester results
>
> URL http://llvm.org/perf/db_default/simple/nts/380/
> Nickname bwilson__llvm-gcc_PROD__i386:4
> Name curlew.apple.com
>
> Run ID Order Start Time End Time
> Current 380
2012 Nov 23
2
[LLVMdev] [cfe-dev] costing optimisations
On 23.11.2012, at 15:12, john skaller <skaller at users.sourceforge.net> wrote:
>
> On 23/11/2012, at 5:46 PM, Sean Silva wrote:
>
>> Adding LLVMdev, since this is intimately related to the optimization passes.
>>
>>> I think this is roughly because some function level optimisations are
>>> worse than O(N) in the number of instructions.
>>
2007 Sep 18
0
[LLVMdev] 2.1 Pre-Release Available (testers needed)
On Fri, Sep 14, 2007 at 11:42:18PM -0700, Tanya Lattner wrote:
> The 2.1 pre-release (version 1) is available for testing:
> http://llvm.org/prereleases/2.1/version1/
>
> [...]
>
> 2) Download llvm-2.1, llvm-test-2.1, and the llvm-gcc4.0 source.
> Compile everything. Run "make check" and the full llvm-test suite
> (make TEST=nightly report).
>
> Send
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
2012 Sep 18
8
Collecting entropy from device_attach() times.
Hi.
I experimented a bit with collecting entropy from the time it takes for
device_attach() to run (in CPU cycles). It seems that those times have
enough variation that we can use it for entropy harvesting. It happens
even before root is mounted, so pretty early.
On the machine I'm testing it, which has minimal kernel plus NIC driver
I see 75 device_attach() calls. I'm being very careful