aserio 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/
parsa has quit [Quit: Zzzzzzzzzzzz]
zbyerly_ has quit [Ping timeout: 276 seconds]
<K-ballo>
hkaiser: I'll have to abandon the acquire future range to vector fix for now
<K-ballo>
dataflow seems to need containers, strictly, not ranges
<hkaiser>
K-ballo: ok, np
<github>
[hpx] K-ballo force-pushed range from 69abf4d to 9a45b37: https://git.io/voasb
<github>
hpx/range 43ab9ed Agustin K-ballo Berge: Add C++11 range utilities
<github>
hpx/range 37d3805 Agustin K-ballo Berge: Cleanup acquire traits, replace boost::range with util/range in their implementation, patch broken whens
<K-ballo>
feels a bit awkward, dataflow should be working in place at best
<K-ballo>
I guess that's what its doing
<K-ballo>
except that instead of copying and working in place, it "copies" by acquiring and push-backing
<hkaiser>
K-ballo: yah dataflow currently has strange sematics wrt the futures passed, iirc
<hkaiser>
silently invalidate futures without explicit moving them
<K-ballo>
and it would explain why dataflow needs a has_push_back trait
<K-ballo>
oh, well, but that's on SG1
<K-ballo>
.then, when, etc
<hkaiser>
yah
eschnett has joined #ste||ar
eschnett has quit [Quit: eschnett]
eschnett has joined #ste||ar
<ajaivgeorge>
hkaiser: mcopik: I have replaced operator- with distance in the PR, and for segmented transform I looked at the non segmented version and saw that even in that the make_tagged_tuple is called in transform_ like in my segmented transform_ so I think we should leave that unchanged. So let segmented_transform() return a tuple which is converted to tagged_tuple by transform_() and returned.
<ajaivgeorge>
Let me know if there are any more issues with the PR.
<hkaiser>
ajaivgeorge: nod, sounds ok
<hkaiser>
ajaivgeorge: I'll have another look at the PR tomorrow
<hkaiser>
thanks!
<ajaivgeorge>
mcopik: I will have the test ready before the meeting so that you can check it out. Also if the dispatched function is to return a complex object should I create a separate find_end (and eventually find_first_of) function objects or modify the existing ones?
<ajaivgeorge>
hkaiser: ok cool, thank you.
<hkaiser>
ajaivgeorge: just use clang-format before we merge everything ;)
<ajaivgeorge>
hkaiser: ok I tried that before, but got an error in the .clang-format file with the AlignEscapedNewlines key
<zao>
The change of that key from a boolean to an enum was in like May, so you may need a newer clang-format binary.
<ajaivgeorge>
zao: ah ok, I was using the ubuntu repo version. :P
<github>
[hpx] ct-clmsn opened pull request #2740: PR for Stackoverflow detection for linux, e.g. based on libsigsegv #2408 (master...corosegfault) https://git.io/vQgpF
EverYoung has joined #ste||ar
hkaiser has quit [Quit: bye]
EverYoung has quit [Ping timeout: 246 seconds]
K-ballo has quit [Quit: K-ballo]
parsa has joined #ste||ar
EverYoung has joined #ste||ar
EverYoung has quit [Ping timeout: 258 seconds]
parsa has quit [Quit: Zzzzzzzzzzzz]
parsa has joined #ste||ar
parsa has quit [Client Quit]
parsa has joined #ste||ar
parsa has quit [Client Quit]
parsa has joined #ste||ar
parsa has quit [Client Quit]
Matombo has joined #ste||ar
Matombo has quit [Remote host closed the connection]
<github>
hpx/master 46d6021 Thomas Heller: Fixing gcc7 compiler error in unit test
vamatya has quit [Ping timeout: 248 seconds]
EverYoung has joined #ste||ar
mcopik has joined #ste||ar
EverYoung has quit [Ping timeout: 246 seconds]
bikineev has joined #ste||ar
denis_blank has joined #ste||ar
taeguk has joined #ste||ar
bikineev has quit [Ping timeout: 248 seconds]
bikineev has joined #ste||ar
hkaiser has joined #ste||ar
taeguk has quit [Ping timeout: 260 seconds]
mcopik_ has joined #ste||ar
mcopik_ has quit [Ping timeout: 260 seconds]
mcopik_ has joined #ste||ar
mcopik_ has quit [Ping timeout: 248 seconds]
eschnett has quit [Quit: eschnett]
K-ballo has joined #ste||ar
parsa has joined #ste||ar
<mcopik>
hkaiser: yesterday we talked about the segmented find_end/first_of, you mentioned an extension of the container for neighbor communication. do you think it's a better solution than handling sequences occupying multiple segments at the main algorithm level, not on container level?
eschnett has joined #ste||ar
Matombo has joined #ste||ar
<github>
[hpx] Naios opened pull request #2741: Replace the unwrapped internals for using the pack_traversal API (master...unwrap_pr) https://git.io/vQ2Qf
parsa has quit [Quit: Zzzzzzzzzzzz]
<K-ballo>
denis_blank: ping
hkaiser has quit [Quit: bye]
<denis_blank>
K-ballo: +
<K-ballo>
denis_blank: you have too many using directives in your test cases, try replacing some with using declarations instead, at the very least the ones that bring names from detail namespaces into scope
<denis_blank>
K-ballo: using namespace ... right? Yes I will replace those.
<github>
hpx/appveyor e6fb5d9 Hartmut Kaiser: Do not show full file paths in diagnostics when building on AppVeyor CI...
aserio has joined #ste||ar
parsa has joined #ste||ar
mbremer has joined #ste||ar
<ABresting>
Hi, I need to ask something.I have an implementation that uses void *.Is it okay to use void *?
<hkaiser>
ABresting: depends
<K-ballo>
some uses of void* are
aserio has quit [Quit: aserio]
aserio has joined #ste||ar
<ABresting>
I have an implementation that uses void * which depends on a library that uses void * as passing and returning arguments.So, I cannot alter that. But, I read online at a lot of places that void * is rarely used in C++.So, Is it OK if I use it in HPX?I also realize that you also have used void * in many places.
<hkaiser>
ABresting: not that many places
<ABresting>
hkaiser: have you processed my cluster access request?
<hkaiser>
ABresting: if you know the type of the thing void* refers to, why not reinterpret_cast it back asap
<hkaiser>
?
<hkaiser>
ABresting: yes, Al will get back to you today (we had a holiday yesterday)
<ABresting>
hkaiser: but if the dependency is on library side so is it ok if I use void * right?
<hkaiser>
ABresting: underneath you have to use void*, sure - but do you need to expose a void* to the user of your code?
<ABresting>
then good for me user never gets to see it.
<hkaiser>
would you mind commentin gon the ticket?
<ABresting>
sure let me see
ajaivgeorge_ has joined #ste||ar
ajaivgeorge has quit [Read error: Connection reset by peer]
EverYoung has joined #ste||ar
<ABresting>
hkaiser: first of all, a lot of code and method is same as libsigsegv, file names ar similar, re-written their code in c++, I am not a lawyer but IDK I avoided using libsigsegv's GPL'ed method.