{"action":"created","issue":{"url":"https://api.github.com/repos/nncarlson/petaca/issues/1","repository_url":"https://api.github.com/repos/nncarlson/petaca","labels_url":"https://api.github.com/repos/nncarlson/petaca/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/nncarlson/petaca/issues/1/comments","events_url":"https://api.github.com/repos/nncarlson/petaca/issues/1/events","html_url":"https://github.com/nncarlson/petaca/issues/1","id":113737976,"number":1,"title":"Any chances for gfortran support?","user":{"login":"zmiimz","id":1889372,"avatar_url":"https://avatars.githubusercontent.com/u/1889372?v=3","gravatar_id":"","url":"https://api.github.com/users/zmiimz","html_url":"https://github.com/zmiimz","followers_url":"https://api.github.com/users/zmiimz/followers","following_url":"https://api.github.com/users/zmiimz/following{/other_user}","gists_url":"https://api.github.com/users/zmiimz/gists{/gist_id}","starred_url":"https://api.github.com/users/zmiimz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zmiimz/subscriptions","organizations_url":"https://api.github.com/users/zmiimz/orgs","repos_url":"https://api.github.com/users/zmiimz/repos","events_url":"https://api.github.com/users/zmiimz/events{/privacy}","received_events_url":"https://api.github.com/users/zmiimz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-10-28T03:44:57Z","updated_at":"2016-03-19T20:31:42Z","closed_at":null,"body":"First, thanks for this remarkable and instructive Fortran code.\r\n\r\nI did try to compile petaca with GNU gfortran 5.2.1 (this is the most recent stable version I have without compiling trunk source code) and got many errors and compiler bugs (ICEs), mostly for sourced allocations. Nevertheless, workarounds exist for many (all?) of them. Moreover, the next gfortran version (6.0) should fix this sourced allocation, so I am wondering if you have tried and abandoned this compiler already or there are still some plans to test and to include gfortran to the supported list?\r\n\r\n In principle, such gfortran fixes could be managed and merged into the code with combined  \\__GFORTRAN__  and \\__VERSION__ preprocessor directives (similarly to INTEL ifort bugs)? \r\n"},"comment":{"url":"https://api.github.com/repos/nncarlson/petaca/issues/comments/198779907","html_url":"https://github.com/nncarlson/petaca/issues/1#issuecomment-198779907","issue_url":"https://api.github.com/repos/nncarlson/petaca/issues/1","id":198779907,"user":{"login":"nncarlson","id":7231327,"avatar_url":"https://avatars.githubusercontent.com/u/7231327?v=3","gravatar_id":"","url":"https://api.github.com/users/nncarlson","html_url":"https://github.com/nncarlson","followers_url":"https://api.github.com/users/nncarlson/followers","following_url":"https://api.github.com/users/nncarlson/following{/other_user}","gists_url":"https://api.github.com/users/nncarlson/gists{/gist_id}","starred_url":"https://api.github.com/users/nncarlson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nncarlson/subscriptions","organizations_url":"https://api.github.com/users/nncarlson/orgs","repos_url":"https://api.github.com/users/nncarlson/repos","events_url":"https://api.github.com/users/nncarlson/events{/privacy}","received_events_url":"https://api.github.com/users/nncarlson/received_events","type":"User","site_admin":false},"created_at":"2016-03-19T20:31:42Z","updated_at":"2016-03-19T20:31:42Z","body":"Some progress to report.  Paul Richard Thomas has been working on some of the gfortran bugs over the last 1-2 months and things are looking much better, and possibly usable, with the current 6.0 svn branch (r234329).  The really serious problems associated with the now closed  PR54070 look to be resolved.  A few minor issues from https://github.com/nncarlson/petaca/issues/1#issuecomment-152920704 remain:\r\n- Warning: Only array FINAL procedures declared for derived type [...] There are a bunch of these warnings during compilation. They are bogus and can be ignored; see [PR58175](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58175) (Debug only)\r\n- The spurious runtime check errors thrown by -fcheck=all are still there, but I've added -fcheck=no-recursion to CMakeLists.txt to disable this check (Debug only)\r\n- The problems associated with [PR67564](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67564) (still open) remain in some of the unit tests (test_any_vector_type, test_any_matrix_type, and test_parameter_list_type), but I've worked around these by simply commenting out some parts of the tests.  The petaca code itself doesn't appear to trip this bug, but it may be an issue for client code to watch out for.\r\n- The failure of a couple of the subtests in test_secure_hash remains.\r\n\r\nSo all tests are now passing with the exception of test_secure_hash"}}