Hi, can the lapack maintainers say anything about the current state of this bug? Is this still a problem with 3.4 or 4.0? -- Falk