qp() in Octave 3.0.0 returns result egregiously violating input constraints

[Thomas Treichl]

Ben Abbott schrieb:
> I've built octave using Apple's lapack/blas (i.e. vecLib), so the 
> problem isn't directly related to the lapack/blas, correct?

True. Then what about the difference between your PPC and our IAs? Just an idea...

> However, when I tried the release-3-0-x branch which I build yesterday 
> (and passed all tests), it fails (also built with vecLib).
> 
> octave:8> result = 0.5*X'*H*X + X'*Q
> result =  5.4445e+58
> octave:9> tol = 10*eps;
> octave:10> all ( X > LB-tol & X < UB+tol)
> ans = 0
> octave:11> all ( A_LB-tol < A_IN*X & A_UB+tol > A_IN*X)
> ans = 0

Hhhmmm...

> Thomas, when did you build last? The sources for one I'm running were 
> pulled from John's archive archive 2-3 days ago.

I've just pulled a new snapshot from John's repository and rebuilt everything. 
The same qr() results than before. However, somehow I think I still don't know 
what's going on. Is it possible to reduce that kind of problem to a much easier 
exercise (that also looks like a fail)?

> ls /sw/bin/octave
> lrwxr-xr-x 1 root admin 13 2008-04-03 19:22 /sw/bin/octave -> octave-3.0.0+
> 
> I'll pull the most recent sources, build the default branch, and then 
> test the result.
> 
> Ben