hkaiser changed the topic of #ste||ar to: The topic is '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/
nikunj has quit [Ping timeout: 260 seconds]
K-ballo has quit [Quit: K-ballo]
hkaiser has quit [Ping timeout: 260 seconds]
nikunj has joined #ste||ar
nikunj has quit [Ping timeout: 260 seconds]
nikunj has joined #ste||ar
nikunj97 has joined #ste||ar
nikunj has quit [Ping timeout: 260 seconds]
nikunj97 has quit [Ping timeout: 260 seconds]
nikunj97 has joined #ste||ar
nikunj97 has quit [Quit: Leaving]
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
<K-ballo>
the new debug::dec is causing quite a few warnings on msvc
hkaiser has quit [Ping timeout: 260 seconds]
hkaiser has joined #ste||ar
<hkaiser>
K-ballo: #4289 is working around this as a flyby
<hkaiser>
K-ballo: not a good solution but silences the warnings, jbjnr_ needs to change dec to deduce the type
<K-ballo>
debug::dec should be prepared to handle all kinds of integers
<hkaiser>
right
<hkaiser>
K-ballo: I might have some time later today to look into this
nikunj has joined #ste||ar
nikunj has quit [Ping timeout: 260 seconds]
nikunj has joined #ste||ar
nikunj has quit [Ping timeout: 260 seconds]
hkaiser has quit [Ping timeout: 260 seconds]
hkaiser has joined #ste||ar
nikunj has joined #ste||ar
<K-ballo>
I noticed it uses clunky iostreams :{
nikunj has quit [Ping timeout: 260 seconds]
<hkaiser>
K-ballo: I wanted to redirect jbjnr_'s logging to our logging infrastructure
<K-ballo>
I'm completely rewriting it...
<hkaiser>
jbjnr_: 's logging?
<K-ballo>
no, ours
<hkaiser>
right
<hkaiser>
good!
<K-ballo>
it's so full of cruft
<hkaiser>
yah
<hkaiser>
jbjnr_'s main complaint is that you can't control what is output and what not
<K-ballo>
what does that mean?
<hkaiser>
he complained about that logging is either printing everything or nothing, he wanted to have something on a file-by-file basis (at least)
<K-ballo>
file-by-file as in TU? header? ..?
<K-ballo>
we do have __FILE__, something could be done perhaps..? I shall discuss with jbjnr_