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!]
<gonidelis[m]> i know there is ctad
<gonidelis[m]> but what about functions?
<gonidelis[m]> namely, https://godbolt.org/z/WrzYv35nG
<gonidelis[m]> 1. is there function tempalte argument deduciton?
<gonidelis[m]> 2. how can i force the compiler to show me what the "3" arguments that I am passing are?
<gonidelis[m]> hkaiser:
Yorlik_ has joined #ste||ar
Yorlik__ has quit [Ping timeout: 265 seconds]
<gonidelis[m]> what! `std::cout << std::is_same<std::remove_reference<unsigned int &>, unsigned int>::value; \\false`
HHN93 has joined #ste||ar
HHN93 has quit [Client Quit]
Yorlik_ has quit [Read error: Connection reset by peer]
K-ballo has quit [Ping timeout: 260 seconds]
K-ballo1 has joined #ste||ar
Yorlik_ has joined #ste||ar
K-ballo1 is now known as K-ballo
karamemp[m] has quit [Quit: You have been kicked for being idle]
PoornaGunathilak has quit [Quit: You have been kicked for being idle]
gdaiss[m] has quit [Quit: You have been kicked for being idle]
<satacker[m]> <gonidelis[m]> "what! `std::cout << std::..." <- std::remove_reference_t
<satacker[m]> > <@gonidelis:matrix.org> 1. is there function tempalte argument deduciton?
<satacker[m]> > 2. how can i force the compiler to show me what the "3" arguments that I am passing are?
<satacker[m]> if there's so suitable candidate the compiler lists all the candidates and also lists how the function was instantiated
HHN93 has joined #ste||ar
<HHN93> Executable /hpx/build/bin/set_operations_3442_test does not exist <_io.TextIOWrapper name='<stderr>' mode='w' encoding='utf-8'>
<HHN93> any idea what this test failure means?
<HHN93> I have tried building the test executable and it does build
HHN93 has quit [Client Quit]
<satacker[m]> please paste the complete error somewhere including CLI args
HHN93 has joined #ste||ar
<HHN93> 13/179 Test #504: tests.regressions.modules.algorithms.set_operations_3442 ............................................***Failed 0.04 sec
<HHN93> Executable /hpx/build/bin/set_operations_3442_test does not exist <_io.TextIOWrapper name='<stderr>' mode='w' encoding='utf-8'>
<HHN93> encountered the error during CI checks
<satacker[m]> it does not exist, probably it has not been built
<satacker[m]> it would be better if you send the CI log link
<HHN93> I did change a few things in that file test
<HHN93> ok got the error
<satacker[m]> Because of the following error your file was not built... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/a506efc40212a1465997ca1a2ba7ecebe2b06bfd>)
<HHN93> thank you
HHN93 has quit [Quit: Client closed]
hkaiser has joined #ste||ar
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 264 seconds]
K-ballo1 is now known as K-ballo
parsa[fn] has joined #ste||ar
scofield_zliu has joined #ste||ar
KhushiBalia[m] has quit [Quit: You have been kicked for being idle]
scofield_zliu has quit [Ping timeout: 252 seconds]
HHN93 has joined #ste||ar
<HHN93> where exactly does hpx request for a CPU thread pool or GPU threads to run the algorithm?
<hkaiser> HHN93: in the executor
<HHN93> do we provide an API to request for a pool of HPX threads?
<hkaiser> the index_queue_spawning is doing that, no?
<hkaiser> why do you ask?
<HHN93> oh ok
<HHN93> untill now I have been running parallel tasks with HPX by finding number of cores using (processing_units_count) and launching those many async tasks
<HHN93> is that the ideal way of doing it?
<hkaiser> not always
<hkaiser> this works well if your tasks are large enough to compensate for the overheads involved
<HHN93> ok, that's how most of the hpx algorithms do it, right?
<hkaiser> no, the algorithms rely on the executor to spawn tasks - those also decide how that's done
<hkaiser> my talk at ccpcon last year has the basics explained
<hkaiser> cppcon*
<HHN93> will go through it (https://www.youtube.com/watch?v=npufmMlGOoM )
<HHN93> thank you
<HHN93> for most algorithms I have observed they call bulk_async_execute using the policy.executor()
<HHN93> does the policy.executor() mention where the processing happens?
<hkaiser> policy.executor() returns a reference to the executor used to do the spawning
<HHN93> thank you
HHN93 has quit [Quit: Client closed]
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 255 seconds]
K-ballo1 is now known as K-ballo