LChenGit
commented
1 year ago These are descriptions of the code snippets from the original repo. I was not sure about it either and kept it as what it is in the original repo. I will remove all the “[inline]”.
From: Chunhua Liao @.> Date: Wednesday, July 5, 2023 at 3:12 PM To: LLNL/dataracebench @.> Cc: Chen, Le @.>, Mention @.> Subject: Re: [LLNL/dataracebench] updated with delaware data part2 (PR #141)
@chunhualiao commented on this pull request.
In benchmarkList.mdhttps://github.com/LLNL/dataracebench/pull/141#discussion_r1253706490:
@@ -106,7 +106,11 @@ DRB179-thread-sensitivity-yes.cc |Y6 | Conflicting writes
DRB180-miniAMR-yes.c |Y6 | Race by shared index variable | MiniAMR app
DRB181-SmithWaterman-yes.c |Y6 | Race appears with larger data size | Smith-Waterman app
DRB183-atomic3_yes.c |Y3 | Races because the write is not protected by atomic | Sequential Consistency for Data-race-free Programs
-
+DRB185-bar1_yes.c |Y3 | wrong 2-thread flag barrier using busy-waits, race [inline] |Sequential Consistency for Data-race-free Programs
what does [inline] mean here? There are multiple appearances of [inline] in this pull request. @LChenGithttps://github.com/LChenGit
— Reply to this email directly, view it on GitHubhttps://github.com/LLNL/dataracebench/pull/141#pullrequestreview-1515448313, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFCDYG76MVU3MJTH2GIPBZ3XOXRDLANCNFSM6AAAAAAZWI7L6I. You are receiving this because you were mentioned.Message ID: @.***>
@chunhualiao part2 of delaware data. I broke down the dataset into several piece to avoid a huge PR.