{"action":"opened","issue":{"url":"https://api.github.com/repos/yhoogstrate/segmentation-fold/issues/8","labels_url":"https://api.github.com/repos/yhoogstrate/segmentation-fold/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/yhoogstrate/segmentation-fold/issues/8/comments","events_url":"https://api.github.com/repos/yhoogstrate/segmentation-fold/issues/8/events","html_url":"https://github.com/yhoogstrate/segmentation-fold/issues/8","id":100396329,"number":8,"title":"-fopenmp + num_thread > 1 - weird behaviour","user":{"login":"yhoogstrate","id":2264697,"avatar_url":"https://avatars.githubusercontent.com/u/2264697?v=3","gravatar_id":"","url":"https://api.github.com/users/yhoogstrate","html_url":"https://github.com/yhoogstrate","followers_url":"https://api.github.com/users/yhoogstrate/followers","following_url":"https://api.github.com/users/yhoogstrate/following{/other_user}","gists_url":"https://api.github.com/users/yhoogstrate/gists{/gist_id}","starred_url":"https://api.github.com/users/yhoogstrate/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yhoogstrate/subscriptions","organizations_url":"https://api.github.com/users/yhoogstrate/orgs","repos_url":"https://api.github.com/users/yhoogstrate/repos","events_url":"https://api.github.com/users/yhoogstrate/events{/privacy}","received_events_url":"https://api.github.com/users/yhoogstrate/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-08-11T20:00:54Z","updated_at":"2015-08-11T20:00:54Z","closed_at":null,"body":"-fopenmp + num_thread > 1 results in very weird behaviour. I suspect that once in a while, the i in Zuker::energy() doesn't get allocated and therefore certain diagonals are not being executed in the filling phase. Therefore, once in a while, the results are different en some unit tests fail. Also valgrind indicates an error down there even if error doesn't appear.\r\n\r\nTo test, I ran Zuker::_print_vij() and I saw that occasionally the x or y axis skipped a line in a normal for loop.\r\n\r\nI should test whether this is a gcc/-fopenmp specific issue."}}