You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These two benchmarks do currently not do self-verification beside checking the results of the computation, which is there to avoid dead-code elimination.
Furthermore these two benchmarks rely (like many others) on the availability of .awaitTermination() in most incarnations. I saw in the Habanero versions the use of finish() instead.
In my version I went with returning promises with the computation result or the number of messages processed.
However, that changes the benchmark quite a bit, so I wonder whether it is an acceptable solution.
These two benchmarks do currently not do self-verification beside checking the results of the computation, which is there to avoid dead-code elimination.
Furthermore these two benchmarks rely (like many others) on the availability of .awaitTermination() in most incarnations. I saw in the Habanero versions the use of finish() instead.
In my version I went with returning promises with the computation result or the number of messages processed.
However, that changes the benchmark quite a bit, so I wonder whether it is an acceptable solution.
See smarr/SOMns-corelib@e2cc695 and smarr/SOMns-corelib@6d0d97e
The text was updated successfully, but these errors were encountered: