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/
rainmaker6[m] has quit [Ping timeout: 245 seconds]
rainmaker6[m] has joined #ste||ar
jaafar_ is now known as jaafar
K-ballo has quit [Quit: K-ballo]
<zao>
One sentiment I see from C developers is that a line of C does what it says and no more. A line of C++ can invoke all sorts of hidden functions all over the place, incurring untold copies and logic. This includes closing curly brackets.
diehlpk_work has quit [Ping timeout: 245 seconds]
<zao>
This extends to things like overload resolution, operator overloading, ADL lookup, signatures of the functions you call, implicit conversions. It’s in some way harder to tell what C++ code actually does. This is of course also more powerful for writing succinct and elegant code but for some people stating things explicitly is quite valuable.
<zao>
(note that I did not in any place use the phrasing that it “maps directly to the machine” as that’s a big lie :D )
hkaiser has quit [Quit: bye]
nanmiao has quit [Ping timeout: 240 seconds]
<ms[m]>
all: piz daint is down for maintenance today, so no ci runs over there currently
CynthiaPeter[m] has quit [Quit: Idle for 30+ days]
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
<tarzeau_>
do i need libhpx_parallelism.so for sure for every case or is it optional?
<ms[m]>
tarzeau_: for sure, libhpx.so depends on it (and they will be renamed soon again)
<ms[m]>
tarzeau_: ok, in that case the question is: why do you need to know if it's optional or not?
<tarzeau_>
so i'll for the moment just put it into libhpx-parallelism and libhpx will depend on that
<tarzeau_>
ms[m]: if it's not needed i would have dropped it ;)
<hkaiser>
tarzeau_: why would you like to drop it?
<tarzeau_>
i would not like to drop it, i just want to get it clean to be able to get it into official debian. i just didn't know if it's really needed or optional
<ms[m]>
ah, we may introduce separate cmake targets for those libraries, but for the moment they'll all come through the same cmake config, so they should all be provided together
<tarzeau_>
ok that answers already all my answers...
<ms[m]>
when (I hope, or if) we separate those fully they'll be different cmake projects (they'd still depend on each other, but one of them could be used without the other)
<tarzeau_>
since i don't know when that will happen or a future (1.6.0+ release happens) i'll just keep on trying with the current released version
<ms[m]>
1.7.0 is brewing right now, but won't change anything
<ms[m]>
it's safe to assume that everything that comes from the same repo needs to be packaged together
<mdiers[m]>
ms: hkaiser Hello, I would like to continue working on a solution for my #5117.
<hkaiser>
ok
<ms[m]>
mdiers: hey, sorry I haven't had the time to try to reproduce it yet... if our system is back online tomorrow I'll try to find some time for it
<mdiers[m]>
<ms[m] "mdiers: hey, sorry I haven't had"> It is important to take a release build 😉
<ms[m]>
👍️
<ms[m]>
are all your tests on 1.6.0 or have you reproduced on a recent-ish master as well?
<zao>
Yay, freenode is "dying".
<ms[m]>
zao: what does that mean? shutting down or just losing users...?
<zao>
ms[m]: A majority of staff resigned and are moving over to a new network, libera.chat, due to some ownership takeover of freenode.
<K-ballo>
that explains the weird spam from admins
<mdiers[m]>
<ms[m] "are all your tests on 1.6.0 or h"> tested with 1.5 and 1.6
hkaiser has quit [Quit: bye]
nanmiao has joined #ste||ar
hkaiser has joined #ste||ar
hkaiser has quit [Quit: bye]
<gnikunj[m]>
srinivasyadav227: yt?
<srinivasyadav227>
yes
<gnikunj[m]>
hey! I just realized I have GSoD meeting same time tomorrow.
<gnikunj[m]>
hkaiser and I were discussing today and hkaiser have Tuesday 9AM CDT time available. Would that work for you?
<srinivasyadav227>
on 25th?
<gnikunj[m]>
yes, and then weekly
<gnikunj[m]>
rori: I was told you're interested in mentoring the gsoc project as well. Does that time work for you?
<srinivasyadav227>
yes, it works :),
<srinivasyadav227>
i am okay with it I mean
<gnikunj[m]>
great! see you on tuesday ;)
<srinivasyadav227>
ok cool :)
rori has joined #ste||ar
<rori>
<gnikunj[m] "rori: I was told you're interes"> yes 👌
<gnikunj[m]>
great! Let me ask Katie to set up a weekly meet.
<gnikunj[m]>
srinivasyadav227: could you send your preferred email id for calendar invite for the weekly meeting?
<srinivasyadav227>
vasu.srinivasvasu.14@gmail.com (sorry its bit lengthy :) )
<gnikunj[m]>
cool, thanks!
<srinivasyadav227>
Thank you, received the mail!
<jedi18[m]>
@hkaiser I was about to start with unique but I noticed that you've added "(@kmoham6 works on this)" next to unique https://github.com/STEllAR-GROUP/hpx/issues/4822 . Is someone else working on it?
hkaiser has joined #ste||ar
diehlpk_work has joined #ste||ar
<gonidelis[m]>
<jedi18[m] "@hkaiser I was about to start wi"> Yup Karame started working on it
<gonidelis[m]>
And Chu works on rotate
<gonidelis[m]>
jedi18: we are still looking for the wanderer who will take on the uninitialized_* ones ;p
<hkaiser>
those should be trivial, actually
<jedi18[m]>
Oh ok in that case I'll start with those then, something easy to get the ball rolling
jehelset has quit [Quit: Using Circe, the loveliest of all IRC clients]