-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking key issues to complete our IBM Lightweight OpenMP Runtime (LOMP) port #44
Comments
dongahn
changed the title
Failing tests with LOMP Runtime
Tracking key issues to complete our IBM Lightweight OpenMP Runtime (LOMP) port
Jul 3, 2017
FYI -- serban reported these issues have been fixed by IBM. |
Is the new version already in rzmanta?
… On Jul 22, 2017, at 01:07, Dong H. Ahn ***@***.***> wrote:
FYI -- serban reported these issues have been fixed by IBM.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Not yet. You may want to ping Serban and Alex.
________________________________
From: Simone Atzeni <notifications@github.com>
Sent: Saturday, July 22, 2017 7:10:49 AM
To: PRUNERS/archer
Cc: Ahn, Dong H.; Comment
Subject: Re: [PRUNERS/archer] Tracking key issues to complete our IBM Lightweight OpenMP Runtime (LOMP) port (#44)
Is the new version already in rzmanta?
On Jul 22, 2017, at 01:07, Dong H. Ahn ***@***.***> wrote:
FYI -- serban reported these issues have been fixed by IBM.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#44 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AA0nqzjEl32T0TcsOthfLuho4Kbzx23oks5sQgLogaJpZM4OMivv>.
|
I made a "coral" branch, and currently it fails only 4 tests: The following OMPT tests hang:
above we have a comment that "the explicit task is not scheduled", but I don't remember the reason. The others are:
above we have a comment "The parent task (implicit) is NULL", it may still be a bug on LOMP. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Failing tests:
The task_schedule event returns
status=task_completed
when it should betask_other
, since the explicit task has not been scheduled yettest/OMPT/parallel/parallel_if0.c
test/OMPT/parallel/serialized.c
It seems this is due to a bug in the OMPT in LOMP
The explicit task is not scheduled
test/OMPT/tasks/explicit_task.c
test/OMPT/tasks/task_in_joinbarrier.c
It seems this is due to how these test cases are written
The parent task (implicit) is NULL
task/task-taskgroup-nested.c
task/task-taskgroup.c
It seems this is due to a bug in the OMPT in LOMP
The text was updated successfully, but these errors were encountered: