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
Yorlik_ has joined #ste||ar
Yorlik__ has quit [Ping timeout: 265 seconds]
hkaiser_ has quit [Quit: Bye!]
hkaiser has joined #ste||ar
hkaiser_ has joined #ste||ar
hkaiser has quit [Ping timeout: 268 seconds]
HHN93 has joined #ste||ar
hkaiser_ has quit [Quit: Bye!]
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 240 seconds]
K-ballo1 is now known as K-ballo
hkaiser has joined #ste||ar
<gdaiss[m]> hkaiser: do you know when the hpx hipcc tests last worked/succeeded? with my PR, the build itself works again and the tests hence run again -- half of them fail with timeout errors though. Was this an issue before as well?
HHN93 has quit [Quit: Client closed]
<hkaiser> mdiers[m]: could you try this patch, please: https://gist.github.com/hkaiser/8e3001377921456c383866c073e75bd3
<mdiers[m]> hkaiser: oh you are fast, yes I am testing
<mdiers[m]> <hkaiser> "mdiers: could you try this patch..." <- The first try with the changes didn't bring any improvement.
<mdiers[m]> I meant earlier also a yield() instead of the wait_any(), is probably already too late for me.
<mdiers[m]> With the yield() it ran through now, but then got stuck at the end when cleaning up.
<hkaiser> mdiers[m]: there is another change for wait_any, I will create a PR we can use to play with things
hkaiser has quit [Quit: Bye!]
<mdiers[m]> <hkaiser> "mdiers: there is another..." <- ok, then let me know when you have created it
hkaiser has joined #ste||ar
HHN93 has joined #ste||ar
<HHN93> I am getting an illegal instruction error when running a HPX program
<HHN93> Is it an generic error or does it point to a specific issue?
<srinivasyadav18[> may be if the code is compiled in one machine (architecture) and executed on different
<HHN93> ok will try compiling again
HHN93 has quit [Ping timeout: 245 seconds]
HHN93 has joined #ste||ar
HHN93 has quit [Quit: Client closed]
HHN93 has joined #ste||ar
HHN93 has quit [Ping timeout: 245 seconds]
HHN93 has joined #ste||ar
<HHN93> does something go horribly wrong if you call a hpx algorithm from within the lib?
<HHN93> something like an illegal instruction error?
<srinivasyadav18[> what do you mean by calling hpx algorithm within lib ? can you elaborate it please ?
<HHN93> my hpx::fold_left function calls hpx::reduce
<srinivasyadav18[> illegal instruction error usually happen when the generated executable file is not run/executed on the same machine architecture that it has been compiled on (or not same dependecies loaded)
<HHN93> I changed the hpx::reduce to my implementation of reduce and it works
<HHN93> I compiled it the same way
<srinivasyadav18[> thats strange
<srinivasyadav18[> can you share more information about the steps that you have performed (log file containing steps and outputs)
<HHN93> I don't think I have observed a hpx algorithm call another hpx algo either, they always call std:: versions of them
<HHN93> `can you share more information about the steps that you have performed (log file containing steps and outputs)`
<HHN93> sure, will try
<srinivasyadav18[> <HHN93> "I don't think I have observed..." <- There are many places where one hpx algorithm calls other hpx algo, there is nothing wrong in that I belive. Its just another function-like call
HHN93 has quit [Quit: Client closed]
hkaiser has quit [Ping timeout: 240 seconds]
hkaiser has joined #ste||ar
<gnikunj[m]> HHN93: Illegal instruction error is not HPX specific error. When building with —march=native and running on a different architecture, you may observe such errors. This is because compilers use architecture optimized instructions which may not be available on another architectural.
<gnikunj[m]> For HPX calling into internal HPX algo implementations, go into GDB and step through functions. It’s a nice exercise ;)
hkaiser has quit [Ping timeout: 240 seconds]
hkaiser has joined #ste||ar