segfault on entry to ia64_single kernel
The CVS version is doing something strange with the single-precision kernels on ia64. After correcting the last bug I posted about checking for a valid file point for the logfile http://bugzilla.gromacs.org/show_bug.cgi?id=262, I found a further problem.
Using a selection of Intel compilers from versions 9, 10 and 11, and gcc 4.0, I get a segfault in the first non-neighbor-search kernel function to be called - 310 in my case. With NOASSEMBLYLOOPS set, the run goes fine. Stepping through with Totalview on four MPI processes, I can see that on program entry, the generic kernel table is fine, but static kernellist_ia64_single does not contain the addresses of the nb_kernelxxx_ia64_single functions. Later, when kernelptr in do_nonbonded gets such a pointer there's a segfault. I'm at a loss to understand how the static table can get mangled in this way.
#3 Updated by Mark Abraham over 9 years ago
I no longer have access to such a machine, so am not sure whether it's still an issue.
I'm fairly sure that I never resolved this satisfactorily, and shifted my focus off the then-CVS version. It could easily have been a compiler/linker issue, rather than a GROMACS issue, as there were numerous threads on gmx-users complaining about that kind of machine (some SGI Altix) with various Intel compilers.
How about we resolve this as "WORKSFORME"?