aserio 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/
ct-clmsn has joined #ste||ar
ct-clmsn has quit [Ping timeout: 264 seconds]
ct-clmsn has joined #ste||ar
ct-clmsn is now known as Guest55069
Guest55069 is now known as ct_clmsn__
daissgr has joined #ste||ar
EverYoung has quit [Ping timeout: 255 seconds]
EverYoung has joined #ste||ar
<daissgr>
Is there currently a problem building hpx with gcc 7.2? I am running into a bunch of undefined references to __atomic_load_16 and other atomic stuff. The same build scripts used to work fine with gcc5.4. I have no problems building hpx with the most current clang on this machine either
EverYoung has quit [Ping timeout: 265 seconds]
<hkaiser>
daissgr: that's a new
<K-ballo>
that's -latomic again, isn't it?
<hkaiser>
K-ballo: most probably
<K-ballo>
I remember someone contributed a more robust check, I thought it was nice, we merged it but then reverted it
<hkaiser>
it broke something, iirc
<daissgr>
Yeah I just did a quick search through the build log and there is no -latomic in there
<hkaiser>
daissgr: try adding it explicitly to the build flags
<github>
hpx/master 9138c70 Thomas Heller: Fixing Docker Image creation
hkaiser has quit [Quit: bye]
mcopik has quit [Ping timeout: 240 seconds]
<daissgr>
That`s odd! Even with -latomic added I still get the same undefined references
<daissgr>
Any idea how I could fix this?
<ct_clmsn__>
@K-ballo phalpern's polymorphic allocator work did the trick
<K-ballo>
uh?
<ct_clmsn__>
@K-ballo this is in reference to the allocator question i may have asked a week or two back
<K-ballo>
ct_clmsn__: I'm missing context
<K-ballo>
lol
<ct_clmsn__>
@K-ballo - yeah apologies
<ct_clmsn__>
@K-ballo i was being a knuckle-head :P
<ct_clmsn__>
thanks for the conversation the other eek
<ct_clmsn__>
week
<ct_clmsn__>
gah
<daissgr>
Nvm, for now I just installed gcc-6 on this machine and the build scripts work again with this one. Though somebody should get on this considering it is still broken with gcc7.2 (which is the standard in ubuntu 17.10) and hpx 1.1.0
daissgr has quit [Ping timeout: 265 seconds]
Vir has quit [Ping timeout: 265 seconds]
hkaiser has joined #ste||ar
Vir has joined #ste||ar
K-ballo has quit [Quit: K-ballo]
ct_clmsn__ has quit [Ping timeout: 265 seconds]
daissgr has joined #ste||ar
daissgr has quit [Client Quit]
hkaiser has quit [Quit: bye]
nanashi55 has quit [Ping timeout: 240 seconds]
david_pfander has joined #ste||ar
nanashi55 has joined #ste||ar
nanashi55 has quit [Ping timeout: 260 seconds]
nanashi55 has joined #ste||ar
nanashi55 has quit [Ping timeout: 260 seconds]
nanashi55 has joined #ste||ar
<github>
[hpx] sithhell created docker_image (+1 new commit): https://git.io/vxdaa
<github>
hpx/docker_image 26a325d Thomas Heller: Fixing Docker image creation...
<heller>
the docker image creation is a bitch
<github>
[hpx] sithhell pushed 1 new commit to ctest_warnings: https://git.io/vxdaj
<github>
hpx/ctest_warnings d8b4f23 Thomas Heller: Merge branch 'master' into ctest_warnings
<heller>
hmmm, looks like the different jobs in the workflow are not interleaving :(
<heller>
this was my main motivation behind splitting the tests up, to have a higher throughput with interleaving job steps
<heller>
simbergm: it's still waiting until all your jobs completed
<simbergm>
heller: I think it's just slow, now I see one running on my branch and configure running on the ctest_warnings branch
<heller>
ok
<github>
[hpx] msimberg opened pull request #3279: Add two variations to the future_overhead benchmark (master...future_overhead-more-benchmarks) https://git.io/vxdou