hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar.cct.lsu.edu | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | Buildbot: http://rostam.cct.lsu.edu/ | Log: http://irclog.cct.lsu.edu/
jaafar has joined #ste||ar
Anushi1998 has joined #ste||ar
Anushi1998 has quit [Ping timeout: 244 seconds]
Anushi1998 has joined #ste||ar
Anushi1998 has quit [Ping timeout: 252 seconds]
Anushi1998 has joined #ste||ar
jaafar has quit [Quit: Konversation terminated!]
Anushi1998 has quit [Remote host closed the connection]
<zao>
Does this no-return-type-deduction branch require CUDA to blow up?
<zao>
My build seems to have gotten to building some of the tests now, with a GCC 7.3.0 with C++11 mode.
<K-ballo>
nvcc, presumably
<K-ballo>
the cuda build on rostam seems as broken with it as without it
<zao>
Then I'd have to build with the CUDA toolchains at work, no CUDA on my test machine at home :)
hkaiser has quit [Quit: bye]
nanashi55 has quit [Ping timeout: 252 seconds]
nanashi55 has joined #ste||ar
david_pfander has joined #ste||ar
mcopik has quit [Ping timeout: 245 seconds]
mcopik has joined #ste||ar
heller__ has quit [Read error: Connection reset by peer]
heller_ has joined #ste||ar
mcopik has quit [Ping timeout: 260 seconds]
mcopik has joined #ste||ar
Anushi1998 has joined #ste||ar
Anushi1998 has quit [Ping timeout: 240 seconds]
Anushi1998 has joined #ste||ar
mcopik has quit [Ping timeout: 260 seconds]
Anushi1998 has quit [Ping timeout: 252 seconds]
mcopik has joined #ste||ar
Anushi1998 has joined #ste||ar
hkaiser has joined #ste||ar
mdiers_ has quit [Remote host closed the connection]
david_pfander has quit [Ping timeout: 264 seconds]
mcopik has joined #ste||ar
mdiers_ has quit [Remote host closed the connection]
mdiers_ has joined #ste||ar
mdiers_1 has joined #ste||ar
mdiers_ has quit [Ping timeout: 244 seconds]
mdiers_1 is now known as mdiers_
mcopik has quit [Ping timeout: 260 seconds]
jaafar has quit [Ping timeout: 268 seconds]
<heller_>
hkaiser: hey
<heller_>
hkaiser: I can't do tomorrow, anthony williams is speaking in munich tomorrow
<heller_>
if you like we can talk now/later
jaafar has joined #ste||ar
<jbjnr_>
hkaiser: heller_ I want to add gpu targets to the resource partitioner, but target constructor calls find_here to init locality and I can't call that before the runtime is up. I'll have to have an abtract target type or something so that I can bind gpu resources to things and work without the locality ...
<heller_>
jbjnr_: if you want to add it to the resource partitioner, the target needs to depend on that, not the other way around
<heller_>
target is, IMHO, a higher level abstraction
<jbjnr_>
ok, then I provide an interface to create a target from the RP, but at init time, it just finds devices and stores them. I was hoping to save some work and reuse the target stuff