K-ballo 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/
hkaiser has quit [Quit: bye]
shahrzad has quit [Quit: Leaving]
akheir has quit [Quit: Leaving]
nanmiao11 has quit [Remote host closed the connection]
bita_ has quit [Ping timeout: 260 seconds]
camila[m] has quit [Quit: Idle for 30+ days]
hkaiser has joined #ste||ar
peltonp1 has quit [Quit: Lost terminal]
parsa has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
parsa has joined #ste||ar
weilewei has joined #ste||ar
akheir has joined #ste||ar
nanmiao11 has joined #ste||ar
shahrzad has joined #ste||ar
<rori> K-ballo: I need help again ^^'
<K-ballo> what kind of compiler is clang11 ?
<rori> what do you mean?
<K-ballo> is it a recent-ish clang with -std=c++11?
parsa has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
parsa has joined #ste||ar
<rori> possibly, it is the hipcc compiler wrapper using the rocm tag in llvm
<rori> I tried to override the cxxflags with c++14, but maybe it's not overridable
<rori> what is weird is that hipcc is using c++14 on windows but c++11 for other platforms..
<K-ballo> reminds me of silly stuff the cuda compiler used to do
<K-ballo> why would it pick the non-const overload given a const tuple?
<K-ballo> and then it complains that the tuple is const
parsa has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
parsa has joined #ste||ar
<K-ballo> rori: if you are willing to try anything, see what happens when dropping `HPX_HOST_DEVICE`
<rori> thanks!
bita has joined #ste||ar
khuck_ has joined #ste||ar
khuck has quit [Ping timeout: 260 seconds]
<tiagofg[m]> Hello,
<tiagofg[m]> K-ballo hkaiser Do you think that #4956 issue, the inheritance problem, still remain on hpx 1.5.0?
<hkaiser> tiagofg[m]: nobody has done anything about it
<K-ballo> I'm not familiar with 4956
<hkaiser> K-ballo: it's the inheritance ticket
<tiagofg[m]> hummm ok thanks anyway
<hkaiser> tiagofg[m] I'm just not sure whether we can do anything about it :/
<K-ballo> ban multiple inheritance?
<hkaiser> +1
khuck_ has quit [Remote host closed the connection]
khuck has joined #ste||ar
khuck has quit [Remote host closed the connection]
khuck has joined #ste||ar
khuck has quit [Client Quit]
khuck has joined #ste||ar
<K-ballo> the debug::print machinery is pushing a lot of unnecessary stuff into headers
<K-ballo> it also seems to be fooling the module system, half the implementation is at the threading_base module, but there's no declared dependency
nanmiao11 has quit [Ping timeout: 245 seconds]
<hkaiser> K-ballo: I don't like the debug::print stuff anyways
<hkaiser> K-ballo: moreover, a lot of the debug::print stuff is duplicated :/
<hkaiser> hmm, or not - I'm confused *puzzled*
<hkaiser> K-ballo: I'll clean it up
<K-ballo> sorry
mariella[m] has joined #ste||ar
<K-ballo> as a data point: replacing inclusion of <modules/functional> with the individual pieces resulted on a reduction of 78s *wall clock* time for building core on my machine
<K-ballo> functional is probably the worst though, by far
<K-ballo> it still sounds like way too much.. that must be across threads
<hkaiser> K-ballo: yes, there is a circular dependency between debugging and threading_base as well :/
<hkaiser> what a mess
<K-ballo> probably why the dependency was not expressed in the first place
bita has quit [Ping timeout: 240 seconds]
<hkaiser> yes
nanmiao11 has joined #ste||ar
weilewei has quit [Remote host closed the connection]
bita has joined #ste||ar