------- Comment #60 from jv244 at cam dot ac dot uk 2007-02-13 09:20 ------- > When you have a moment, could you confirm that all is now well with trunk, > please? Once again, I am sorry about the breakage. Now I see Daniel's > testcase, I realise that I could easily have devised a test... with 20:20 > hindsight:) Yes, current trunk compiles CP2K again at -O0 (still blocked by PR 30391 at -O1). No need to apologize, I realize that many of the change you make fall into the 'subtle' category and do not pop-up with the normal regtesting. As said before, I'm, unfortunately, used to the fact that even good commercial compilers (say NAG's f95, IBM's xlf90, Intel's ifort) regress on CP2K from time to time. It is very annoying to have to fight compilers, after the computer center upgraded a machine. My hope is that CP2K being freely available (even in a handy single file format, see initial comment) could prevent this from happening. Ultimately, I want to see some runtime regression tester... maybe I should try to get CP2K in a future version of SPEC ... any hints on how to do that ??
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29975
