K-ballo 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/
patrick22 has joined #ste||ar
hkaiser has joined #ste||ar
akheir has quit [Quit: Leaving]
patrick22 has quit [Ping timeout: 272 seconds]
hkaiser has quit [Quit: bye]
bita__ has quit [Ping timeout: 272 seconds]
bita__ has joined #ste||ar
shahrzad has quit [Quit: Leaving]
bita__ has quit [Ping timeout: 260 seconds]
wash[m] has quit [Ping timeout: 272 seconds]
wash[m] has joined #ste||ar
patrick22 has joined #ste||ar
hkaiser has joined #ste||ar
K-ballo has quit [Ping timeout: 256 seconds]
K-ballo has joined #ste||ar
K-ballo has quit [Ping timeout: 240 seconds]
K-ballo has joined #ste||ar
akheir has joined #ste||ar
<ms[m]>
K-ballo: can't reproduce leaking implies we do something naughty to break iwyu in hpx?
<K-ballo>
I don't really know, maybe it just takes a more convoluted scenario to reproduce
<ms[m]>
hmm, my first suspect would always be the generated module headers but it sounded like you already tried to handle those?
<K-ballo>
i'll have to try starting from hpx and reducing it in place