hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar-group.org | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | This channel is logged: irclog.cct.lsu.edu
hkaiser has quit [Quit: Bye!]
Yorlik_ has joined #ste||ar
Yorlik has quit [Ping timeout: 265 seconds]
tufei has quit [Remote host closed the connection]
tufei has joined #ste||ar
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 246 seconds]
K-ballo1 is now known as K-ballo
K-ballo has quit [Read error: Connection reset by peer]
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 268 seconds]
K-ballo1 is now known as K-ballo
prakhar has joined #ste||ar
<prakhar> My name is Prakhar Agrawal and I am in my final year of btech (electronics and communications engineering).
<prakhar> I was going through the list of projects for gsoc’23 and stellar group caught my interest. The project “Async I/O using Coroutines and S/R” seems ideal as I have hands-on working experience with c++ and cmake.
<prakhar> While reading about the project, I went through the attached reference pages and got an idea about async I/O, their benefits and their basic implementation using coroutines in cpp.
<prakhar> Please guide me further so I can start contributing to the project and create a roadmap for the same.
<prakhar> Looking forward to hearing from you
TanishqJain[m] has left #ste||ar [#ste||ar]
<satacker[m]> Hello prakhar The main aim of the project is to implement a non trivial example of I/O workload using the recently added Senders and Receivers (google P2300 C++) and co_await integration.
<satacker[m]> For more info on P2300 checkout my report --> https://satacker.github.io/blog/gsoc-2022-work
<satacker[m]> I would recommend you to get acquainted with C++ 20 coroutines
<prakhar> sure, looking into it, thank you for the quick response!
<prakhar> I read few blogs related to c++ coroutines and got a sense of its working and its basic implementation
<satacker[m]> As far as contributions go, there are plenty of issues on GitHub, you can just pick your (poison)
<satacker[m]> Speaking of contributions Isidoros any updates on the set_intersection issue?
<satacker[m]> For those interested in P2300, we have a type erased sender `any_sender` and the last time I used it had an issue with race conditions. You can experiment with it as well.
HHN93 has joined #ste||ar
<HHN93> how can I get my GSoC project proposal reviewed?
<satacker[m]> You can ask your mentors (any of the listed ones) to review your proposal (forming a google docs link where mentors might suggest some things) privately (because sharing it openly may cause spamming).
prakhar has quit [Quit: Client closed]
HHN93 has quit [Quit: Client closed]
<Isidoros[m]> > <@satacker:matrix.org> For those interested in P2300, we have a type erased sender `any_sender` and the last time I used it had an issue with race conditions. You can experiment with it as well.
<Isidoros[m]> Hey, I have made some suggestions, not much due to working on `trivial_relocation` for my proposal. Here is the issue I opened up: https://github.com/STEllAR-GROUP/hpx/issues/6198
<hkaiser> Isidoros[m]: thanks
<Isidoros[m]> Happy to help!
<Isidoros[m]> By the way I have a couple of questions about `trivially_relocatable` that I have not been able to clear up. Should I send you a pm or is this the place to talk about specific issues too?
<hkaiser> let's talk about things here
<Isidoros[m]> s/voof6EnK8/Kxvh5PGP7/
<Isidoros[m]> This is a branch of llvm in which P1144 (trivially_relocatable) has been implemented
<hkaiser> ms[m]1: thanks!
HHN93 has joined #ste||ar
diehlpk_work has joined #ste||ar
<diehlpk_work> I got today this warning
<diehlpk_work> warning: ‘compute_action’ has a base ‘hpx::actions::action<double (*)(data_client, double), compute, compute_action>’ whose type uses the anonymous namespace [-Wsubobject-linkage]
<diehlpk_work> 23 | HPX_PLAIN_ACTION(compute, compute_action)
<K-ballo> that's odd
<Isidoros[m]> s/llvm/`clang`/, s//`/, s//`/
<hkaiser> diehlpk_work: I've never seen this, do you have a small reproducing example?
<K-ballo> diehlpk_work: is the build otherwise error free?
<HHN93> diehlpk_work can you post the trace of the warning, I am not able to grep for HPX_PLAIN_ACTION(comp
HHN93 has quit [Quit: Client closed]
<diehlpk_work> K-ballo, yes, the code compiles and run, but I recently got this warning with HPX 1.8.0 and gcc 12.2.1
<diehlpk_work> gcc --version
<diehlpk_work> gcc (GCC) 12.2.1 20221121 (Red Hat 12.2.1-4)
HHN93 has joined #ste||ar
<HHN93> diehlpk_work I have tried compiling with g++ 11.3(ubuntu), 12.1(ubuntu) and 13.0 (experimental) and haven't come across any warnings
<HHN93> can you try changing data_client to ::data_client
<diehlpk_work> HHN93, Yes, that happened with some newer gcc
<HHN93> yes, I have come across cases where different GCC versions give warnings and even errors in some cases
<diehlpk_work> Fedora uses always the latest gcc
<diehlpk_work> Next release will come with gcc 13
<hkaiser> the funny thing is that we don't use any anonymous namespaces
<K-ballo> we don't? that sounds bad
<K-ballo> also, unnamed, that warning gets the terminology wrong
tufei has quit [Remote host closed the connection]
tufei has joined #ste||ar
HHN93 has quit [Quit: Client closed]
<hkaiser> K-ballo: well, we do, just not for actions
K-ballo has quit [Ping timeout: 255 seconds]
K-ballo has joined #ste||ar
diehlpk_work has quit [Remote host closed the connection]