Skip to content

Conversation

@swappik
Copy link
Contributor

@swappik swappik commented Jun 28, 2021

See #32 for details

Before this fix I had a lot of error messages about illegal value in P?TRORD in x?hseqr tests on some systems.

{    1,    0}:  On entry to PDTRORD parameter number **** had an illegal value
{    0,    0}:  On entry to PDTRORD parameter number **** had an illegal value
{    1,    1}:  On entry to PDTRORD parameter number **** had an illegal value
{    0,    1}:  On entry to PDTRORD parameter number **** had an illegal value

And interesting detail is that xdhseqr test prints such messages and then finishes with PASSED check, but xshseqr test prints messages endlessly and never finishes.

After this fix these messages are gone and x?hseqr tests works normally on all systems.

Also I found same error in PSTRSEN and fixed it.

@langou langou merged commit 6c76aaa into Reference-ScaLAPACK:master Jun 28, 2021
@julielangou julielangou added this to the 2.2 release milestone Feb 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants