General

Profile

James Ostrander

  • Registered on: 01/26/2017
  • Last connection: 02/16/2017

Issues

Activity

02/17/2017

02:57 PM GROMACS Task #2102: decide future of xlc+power support
On the subject of XLC causing printf(tan(0)) to return -0 at -O3, -O3 in XLC enables -qnostrict, which apparently rel...

02/16/2017

03:31 PM GROMACS Task #2102: decide future of xlc+power support
You're right, I'm running gcc 4.8.5, which is the latest rpm for RHEL 7.3. I'll try on Ubuntu ppc64le, where I have a...

02/10/2017

08:54 PM GROMACS Task #2102: decide future of xlc+power support
The GCC error I mentioned in #20 occurs regardless of whether MPI is used.
08:52 PM GROMACS Task #2102: decide future of xlc+power support
With XLC+MPI in release mode, it failed to generate shell completions:...
08:04 PM GROMACS Task #2102: decide future of xlc+power support
I'm in the process of testing those changes now. I get the following when compiling with GCC+MPI (same result Release...

02/09/2017

02:44 PM GROMACS Task #2102: decide future of xlc+power support
If you can add your repro cases here, I'll gladly see to it that they're forwarded along to the XL team.

02/08/2017

09:43 PM GROMACS Task #2102: decide future of xlc+power support
Thanks for the updates, Mark. I was able to reproduce that issue. Here is my output without gdb (I tried release mode...

01/31/2017

05:03 PM GROMACS Task #2102: decide future of xlc+power support
BTW: https://gitlab.kitware.com/cmake/cmake/issues/16605
Thanks for the tip!
04:57 PM GROMACS Task #2102: decide future of xlc+power support
Would you accept pull requests for fixes for this group of compilers? You mentioned that there was further work to do...

01/27/2017

05:38 PM GROMACS Bug #2103: xlc/xlC: shellfc.cpp: empty array initializer "expression not supported"
The formatting was butchered, but the error's arrow should be pointing at the {}.

Also available in: Atom