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/
<jbjnr_>
testing cholesky against master branch and all compiles, but something is wrong with the numa binding, so I may want to get an emergency last minute patch in before the release if I can locate the problem
<ste||ar-github>
hpx/segmented_algorithms 2bb2140 Hartmut Kaiser: Fixing errors introduced during re-applying the patches from ticket 2859
ste||ar-github has left #ste||ar [#ste||ar]
Anushi1998 has quit [Ping timeout: 240 seconds]
<simbergm>
hkaiser (IRC): yt?
Anushi1998 has joined #ste||ar
<hkaiser>
simbergm: here
<simbergm>
hkaiser (IRC): hey, I'd like to ask two things of you
<hkaiser>
sure
<simbergm>
1. could you upload the public part of the stellar group signing key to the stellar group github profile or something
<simbergm>
I'm not 100% sure that's possible but could you at least check?
<hkaiser>
ok, no idea what that means, but I can try
<simbergm>
2. for the release notes, I think last time you copied them over to the stellar.cct.lsu page from stellar-group.org
<simbergm>
do you want to do that again? otherwise I can do it, I'd just need an account there as well (don't know if I'm allowed to have one)
<hkaiser>
simbergm: aserio can give you access
<simbergm>
about the key, on personal accounts one can upload a pgp key to make it show up as verified, if the stellar key goes somewhere like that we can have a signed, tagged release show up as verified on github
<simbergm>
ok, thanks
nikunj has quit [Ping timeout: 244 seconds]
<aserio>
simbergm: You need access to the .cct page?
<hkaiser>
simbergm: there is no such option for organizations, at least I don't see any
<simbergm>
hkaiser (IRC): ok, thanks for checking
<simbergm>
aserio: yeah, if possible
<simbergm>
then I can do the release announcement (and update download pages etc) on both at the same time
<hkaiser>
simbergm: I can add the pgp key to my account, but not sure if that's what we need
<aserio>
simbergm: done
<aserio>
simbergm: btw did we decide if we wanted to schedule a separate remote stellar meeting or did we want to just tack onto the GB
Anushi1998 has quit [Remote host closed the connection]
<aserio>
call
david_pfander has quit [Ping timeout: 250 seconds]
<simbergm>
um, I think we go with the separate call on the 27th first and see where we go after that
<simbergm>
I'm happy either way, we can decide later
<simbergm>
hkaiser (IRC): ok, thanks, I can also do that and also don't know if that's what we need
<simbergm>
I'll push a tag signed with the key and see what happens
<aserio>
simbergm: I am fine with going for November 27th
nikunj has joined #ste||ar
<simbergm>
aserio (IRC): ok, good, let's go with that then
<simbergm>
aserio: thanks for the account, got the email :)
<aserio>
np :)
nikunj has quit [Remote host closed the connection]
<galabc>
where we actually see a -fopenmp=libomp flag. I dont understand why cmake would call a -fopenmp flag when I never specified it in the cmake file
<hkaiser>
afaiu, blaze is adding this
<parsa[w]>
because Blaze uses BLAS functions that use OpenMP underneath
Anushi1998 has joined #ste||ar
<galabc>
Ok so basically anytime you run blaze you will use secretely openMP
<hkaiser>
depends on the options you use for blaze
<parsa[w]>
Blaze uses BLAS functions that use OpenMP. Yes. Unless you have a BLAS library that uses HPX instead of OpenMP yes you would still use OpenMP for executing those BLAS functions
<galabc>
Ok Im actually trying to run blazemark with openmp and HPX and compare the two
<galabc>
I've already collected data for openMP and now Im trying with HPX
<parsa[w]>
Blaze itself however will not directly use OpenMP if you instruct it to use HPX threads by defining BLAZE_USE_HPX_THREADS
<hkaiser>
galabc: note that we're working on improving the HPX backend for blaze
<hkaiser>
please coordinate with diehlpk_work
Anushi1998 has quit [Ping timeout: 246 seconds]
<galabc>
parsa: So if I use the BLAZE_USE_PX_THREADS flags ,even if I put -fopenmp BLAZE should only use HPX?
<diehlpk_work>
galabc, Please ask Sharzad about the compilation
Anushi1998 has joined #ste||ar
<parsa[w]>
galabc: i think Blaze gives you the choice to use HPX threads, OpenMP, std::thread, and Boost.Thread... regardless of which implementation you choose, for some operations it will use BLAS functions that use OpenMP