I just downloaded lapack 3.2.2 and compiling it with NAG nagfor compiler version 5.2 with option -C=undefined to detect access to undefined variables I found that during make lapack_testing an undefined varable is indeed accessed. I am attaching two files: 1)typescript with a script of what is happening with a cat of file snep.out where you can see the backtrace produced by the NAG runtime 2) snep.ou I hope this is of help for you Vittorio Zecca -------------- next part -------------- A non-text attachment was scrubbed... Name: typescript Type: application/octet-stream Size: 45796 bytes Desc: not available Url : http://lists.eecs.utk.edu/mailman/private/lapack/attachments/20100719/e16e744f/typescript-0001.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: snep.out Type: application/octet-stream Size: 1494 bytes Desc: not available Url : http://lists.eecs.utk.edu/mailman/private/lapack/attachments/20100719/e16e744f/snep-0001.obj |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Lapack] LAPACK compiling problem on Solaris Machine, julie langou |
|---|---|
| Next by Date: | [Lapack] lapack 3.2.2 access to undefined element of array, Julien Langou |
| Previous by Thread: | [Lapack] lapack 3.2.2 division by zero in slatm7.f line 188, Vittorio Zecca |
| Next by Thread: | [Lapack] lapack 3.2.2 access to undefined element of array, Julien Langou |
| Indexes: | [Date] [Thread] |