hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar-group.org | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | This channel is logged: irclog.cct.lsu.edu
<hkaiser>
I don't think hpxcl needs anything special
<hkaiser>
-DHPX_WITH_VALGRIND=On
<pedro_barbosa[m]>
But in order for it to work on HPXCL I need to use that flag on HPX?
<hkaiser>
I believe so, yes
<pedro_barbosa[m]>
Ok thank you
<hkaiser>
pedro_barbosa[m]: the valgrind support was not tested in a while, please report back if you run into issues
<pedro_barbosa[m]>
Will do, thanks
<gonidelis[m]>
hkaiser: what's hpx::unwrapping?
<gonidelis[m]>
wrong phrasing
<gonidelis[m]>
i get what uwrapping is
<gonidelis[m]>
the question is, do we always need it in comination with dataflow
<gonidelis[m]>
?
diehlpk_work has quit [Remote host closed the connection]
diehlpk_work has joined #ste||ar
Yorlik has joined #ste||ar
diehlpk has joined #ste||ar
diehlpk has quit [Quit: Leaving.]
<hkaiser>
gonidelis[m]: it's a convenience wrapper
<hkaiser>
it is a function object that calls .get() on all of it's arguments that are futures and dispatches to the wrapped function, it forwards either the arguments themselves or whatever was returned from those .get() calls
hkaiser has quit [Ping timeout: 264 seconds]
hkaiser has joined #ste||ar
jehelset has joined #ste||ar
diehlpk has joined #ste||ar
Yorlik has quit [Ping timeout: 268 seconds]
diehlpk has quit [Quit: Leaving.]
Yorlik has joined #ste||ar
Yorlik has quit [Ping timeout: 245 seconds]
diehlpk_work has quit [Remote host closed the connection]
diehlpk_work has joined #ste||ar
K-ballo has quit [Ping timeout: 265 seconds]
K-ballo has joined #ste||ar
hkaiser has quit [Read error: Connection reset by peer]