hkaiser 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/ | GSoC2018: https://wp.me/p4pxJf-k1
parsa[[w]] has quit [Read error: Connection reset by peer]
parsa[w] has joined #ste||ar
mcopik_ has joined #ste||ar
eschnett has joined #ste||ar
aserio has joined #ste||ar
mcopik_ has quit [Ping timeout: 260 seconds]
jaafar has joined #ste||ar
ste||ar-github has joined #ste||ar
<ste||ar-github>
[hpx] msimberg opened pull request #3415: WIP: Scheduler NUMA hint and shared priority scheduler (master...scheduler-numa-hint) https://github.com/STEllAR-GROUP/hpx/pull/3415
ste||ar-github has left #ste||ar [#ste||ar]
<zao>
Interesting... Boost.Context is not built on OpenBSD at all.
<zao>
Might not have to care about that OS at all then :P
<K-ballo>
this is interesting, starting 1.68.0 using boost.system for C++14 requires boost build for C++14
<zao>
I'm a bit unsure. Should I fake this to be N cores with one PU each, or one core with N PUs?
<zao>
Leaning toward N cores, as it feels like it'd be less likely to confuse HPX algorithms than a single core that happens to have 8+ PUs.
nikunj has quit [Quit: goodnight]
eschnett has quit [Quit: eschnett]
<zao>
2>c:\local\boost_1_68_0\boost\iostreams\positioning.hpp(96): warning C4996: 'std::fpos<_Mbstatet>::seekpos': warning STL4019: The member std::fpos::seekpos() is non-Standard, and is preserved only for compatibility with workarounds for old versions of Visual C++. It will be removed in a future release, and in this release always returns 0. Please use standards-conforming mechanisms to manipulate fpos, such as conversions to and from
<zao>
streamoff, or an integral type, instead. If you are receiving this message while compiling Boost.IOStreams, a fix has been submitted upstream to make Boost use standards-conforming mechanisms, as it does for other compilers. You can define _SILENCE_FPOS_SEEKPOS_DEPRECATION_WARNING to acknowledge that you have received this warning, or define _REMOVE_FPOS_SEEKPOS to remove std::fpos::seekpos entirely.
<zao>
K-ballo: I didn't expect them to actually modify VC++ to cope with Boost's stupidity :D