-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert PRs 4515 and 4520 (restore second, dsecnd) #4696
Conversation
This reverts commit 9b24b31. It turns out that PRs 4515 and 4520 break the tests under lapack-netlib/TESTING which require SECOND and DSECND. IBM has decided this is a bigger biger problem than the conflict between lapack second_ and the xlf run time.
This reverts commit bdaa670. It turns out that PRs 4515 and 4520 break the tests under lapack-netlib/TESTING which require SECOND and DSECND. IBM has decided this is a bigger biger problem than the conflict between lapack second_ and the xlf run time.
Strange - unless I'm missing something, your original PRs were conditional on the compiler being xlf, and the value returned by second or dsecnd is only ever used to provide performance data that does not impact the validity of test results. |
A number of tests under lapack-netlib/TESTING/LIN and EIG call SECOND and DSECND and won't build grep -i '= *second' /.f /.F grep -i '= *dsecnd' /.f /.F |
I should have said that PRs 4515 and 4520 break xlf builds of some tests under lapack-netlib/TESTING , |
Right, but my understanding was that these routines were conflicting with equivalent implementations provided by xlf ? I have no problem with reverting the changes, I am only wondering if there might be a better solution for this issue (that ultimately affects Reference-LAPACK as well, from where OpenBLAS' lapack-netlib tree is copied) |
I understand your point, but we have had several discussions within IBM, and it So in the short term we would simply like to revert the changes in PRs 4515 and 4520. Thanks. |
It turns out that PRs 4515 and 4520 break xlf builds of tests under
lapack-netlib/TESTING which require SECOND and DSECND. IBM
has decided this is a bigger problem than the conflict
between lapack second_ and the xlf run time.