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/
jaafar has quit [Ping timeout: 246 seconds]
vamatya has quit [Ping timeout: 240 seconds]
hkaiser has joined #ste||ar
vamatya has joined #ste||ar
vamatya has quit [Ping timeout: 240 seconds]
eschnett has joined #ste||ar
mcopik has quit [Quit: Leaving]
K-ballo has quit [Quit: K-ballo]
hkaiser has quit [Quit: bye]
ajaivgeorge has quit [Read error: Connection reset by peer]
ajaivgeorge has joined #ste||ar
EverYoung has joined #ste||ar
EverYoung has quit [Ping timeout: 246 seconds]
ajax67 has joined #ste||ar
patg has joined #ste||ar
patg has quit [Quit: This computer has gone to sleep]
<david_pfander>
specifically hpx::util::plugin::dll::LoadLibrary(hpx::error_code&, bool) seems to use dlopen, which requires a dynamically linked libc, if I interpret the warning correctly. This also trigger undefined references, as the application now wants a dlopen symbol
<david_pfander>
heller_: ^ this is on tave, maybe you've seen this
pree has quit [Ping timeout: 240 seconds]
<zao>
Not sure if HPX static builds are supposed to only have static HPX or also static flavors of dependencies.
<zao>
Down that route lies horror.
ajaivgeorge_ has joined #ste||ar
<david_pfander>
zao: sure, but that "-ldl" stuff is introduced by the hpx_application pkg-config
<david_pfander>
and the error I mentioned is immediately in the plugin infrastructure of HPX
<zao>
I'd reckon that the pkgconfig files are not overly vetted for link line order, considering that it's a very weirdo niche use of the library.
<zao>
Haven't touched it since dynamic HPX broke on my systems.
jbjnr has quit [Remote host closed the connection]
pree has joined #ste||ar
david_pfander has quit [Quit: david_pfander]
ajaivgeorge_ has quit [Remote host closed the connection]
ajaivgeorge_ has joined #ste||ar
david_pfander has joined #ste||ar
vamatya has joined #ste||ar
david_pfander has quit [Ping timeout: 246 seconds]
aserio has joined #ste||ar
Matombo has quit [Remote host closed the connection]
vamatya has quit [Ping timeout: 268 seconds]
pree_ has joined #ste||ar
<parsa[w]>
pree: yeah
pree has quit [Ping timeout: 240 seconds]
vamatya has joined #ste||ar
aserio has quit [Ping timeout: 240 seconds]
Matombo has joined #ste||ar
pree_ has quit [Ping timeout: 240 seconds]
eschnett has quit [Quit: eschnett]
pree_ has joined #ste||ar
eschnett has joined #ste||ar
eschnett has quit [Ping timeout: 268 seconds]
eschnett has joined #ste||ar
hkaiser has joined #ste||ar
aserio has joined #ste||ar
troska has left #ste||ar [#ste||ar]
<hkaiser>
heller_: could you comment on #2696, please?
<hkaiser>
akheir: could you add a -DHPX_WITH_CXX14=On to the gcc 7.1 builders on buildbot, please?
<akheir>
hkaiser: sure
<hkaiser>
thanks
<ABresting>
hkaiser: bryce wants me to ask you regarding the use of libsigsegv as an external dependency
<ABresting>
as even if I write it again it will be a derivative from libsigsegv
<hkaiser>
ABresting: as said before, using it is fine as long as the integration happens on the user's machine
<ABresting>
but we do need to handle it correct?
<ABresting>
as detecting stack overflow is a low hanging fruit with libsigsegv
<hkaiser>
so what's your question?
<ABresting>
thread in which stack overflow occurred we need to handle it as in allocate more space if available ?
aserio has quit [Ping timeout: 240 seconds]
<hkaiser>
sorry you lost me
<ABresting>
ok let me try again: in a multi-threaded environment, if a stack overflow occurs in one of the threads, libsigsegv is going to detect it, but that might have occurred due to grain size is less. Now, if space is available to us then can we re-allocate the thread to larger space than before?
<ABresting>
such type of handling I am talking about
aserio has joined #ste||ar
<hkaiser>
ABresting: you tell me if we can do that
<ABresting>
everything is possible at a price i.e. performance
<hkaiser>
sure
<hkaiser>
I still don't know what's your question, sorry :/
<ABresting>
you tell me if this tradeoff will be acceptable
<hkaiser>
ABresting: let's assume it is - what now?
EverYoung has joined #ste||ar
<ABresting>
ok I think we need to be on the same page first, https://www.gnu.org/software/libsigsegv/ here they have described the handlers which do clean ups, I am talking about such functionality
EverYoung has quit [Remote host closed the connection]
Matombo has quit [Remote host closed the connection]
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
hkaiser has quit [Quit: bye]
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
<ABresting>
still ambiguous?
<pree_>
parsa[w] : yt ?
EverYoung has quit [Ping timeout: 246 seconds]
EverYoung has joined #ste||ar
jbjnr has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
Matombo has joined #ste||ar
Matombo has quit [Remote host closed the connection]
Matombo has joined #ste||ar
Matombo has quit [Remote host closed the connection]
dmarce2 has joined #ste||ar
<dmarce2>
heller: wash[m]: Is it a problem if a "direct action" thread is suspended with a call to wait, get, etc?
<dmarce2>
washplanez: ^
pree_ has quit [Quit: AaBbCc]
<jbjnr>
dmarce2: I think that heller_ fixed it so that if a direct action goes into suspended state, the task is moved into a normal one and the background thread is resumed.
<jbjnr>
so it should be ok - but try to avoid it 'just in case'
<dmarce2>
jbjnr: OK. I think a bug in Octo-tiger I have been stalking for a month may be related to that.
<heller_>
It should be fine nowadays
bikineev has joined #ste||ar
dmarce2 has quit [Quit: Leaving.]
dmarce2 has joined #ste||ar
eschnett has quit [Quit: eschnett]
dmarce21 has joined #ste||ar
dmarce2 has quit [Ping timeout: 240 seconds]
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
jaafar has quit [Ping timeout: 240 seconds]
mcopik_ has joined #ste||ar
EverYoung has quit [Ping timeout: 246 seconds]
EverYoung has joined #ste||ar
EverYoun_ has joined #ste||ar
EverYoung has quit [Ping timeout: 246 seconds]
EverYoun_ has quit [Remote host closed the connection]
aserio has joined #ste||ar
aserio has quit [Ping timeout: 246 seconds]
EverYoung has joined #ste||ar
EverYoun_ has joined #ste||ar
EverYoun_ has quit [Remote host closed the connection]
EverYoun_ has joined #ste||ar
EverYoung has quit [Ping timeout: 246 seconds]
EverYoun_ has quit [Ping timeout: 246 seconds]
bikineev has quit [Remote host closed the connection]
bikineev has joined #ste||ar
mcopik_ has quit [Ping timeout: 246 seconds]
bikineev has quit [Remote host closed the connection]