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/
<hkaiser> ok
hkaiser has quit [Quit: bye]
bita has quit [Read error: Connection reset by peer]
bita has joined #ste||ar
bita has quit [Ping timeout: 260 seconds]
bita has joined #ste||ar
bita has quit [Ping timeout: 244 seconds]
<ms[m]> K-ballo: `bits/exception.h` doesn't quite look right... as do the changes to the swapcontext files
<ms[m]> but nonetheless very cool if that now mostly works correctly to detect missing and unnecessary includes!
<ms[m]> re the manual global module headers: those are partly from before we renamed them to `hpx/modules/modulename.hpp` when we actually had `hpx/modulename.hpp` headers from before, and partly where the module only has one file and it didn't make much sense to have an extra level of indirection (not that it would hurt), but we could just as well generate all of them instead
<K-ballo> anything from bits/ is still missing in the libstdc++ mapping
<gonidelis[m]> K-ballo: what you are trying to push, is for our code to detect the proper includes automatically?
<K-ballo> something like that, yeah
<K-ballo> we are notoriously bad at getting our #includes right
<K-ballo> we already have some low tech regex based include checks, this is the real thing, an actual compiler understanding the code
<zao> Include What You Use, right? Took me a while to grok the acronym.
<gonidelis[m]> K-ballo: what are the disadvantages of having redundant #includes? Does it affect compile time performance a lot?
<gonidelis[m]> or is it just a readability issue?
<K-ballo> redundant as in the same include twice? or redundant as in including headers that nobody uses?
<gonidelis[m]> the second
<K-ballo> compile time and memory usage, false dependencies,
<gonidelis[m]> oh ok.... that sounds like a serious spaghetti that needs to get untightened here
<K-ballo> the more serious problem is the other side, not including things that are actually used
<gonidelis[m]> but doesn't the compiler provide that info in the first place?
<K-ballo> no?
<gonidelis[m]> how could be sth used if it's not included ? ;p
<K-ballo> that's precisely why we are getting modules in the language
<K-ballo> the compiler can't tell the difference between headers
<K-ballo> doesn't know whether a header includes something to export or to use it privately
<gonidelis[m]> hm... didn't know that. c++ compilation theory seems quite intriguing
<K-ballo> both std::string and its op<< are in <string>, which is not being included
<K-ballo> this particular standard library implementation happens to privately use those symbols in <iostream>, and they leak
<K-ballo> on a different implementation this may not compile
<K-ballo> this is what modules come to fix: leakage
<gonidelis[m]> so... one has to include exactly what they use and not just depend on random leakages to do the job
<gonidelis[m]> again I don't know why that might be a problem, although it sounds quite a sloppy way of doing things
<K-ballo> problem is it compiles in one place but not the other, compiles today but not tomorrow
<gonidelis[m]> ahhh yy!! I remember hkaiser noting this in one of our meetings. true. indeed your task is a serious one
<ms[m]> K-ballo: btw, did you see https://github.com/STEllAR-GROUP/docker_build_env/pull/26? do you think that'll do (i.e. iwyu based on clang 8) or do we need a newer one?
<K-ballo> I saw it, but I don't know how to review
<K-ballo> how do I try it out?
hkaiser has joined #ste||ar
<ms[m]> K-ballo: ooh, I see, you don't try it out (as in the image is not pushed anywhere until it's actually merged)... I suppose the easiest way for you to try it would be to pull our current image and do `apt update && apt install iwyu` and then try it out there
<gonidelis[m]> irrelevant link share for your spare time: https://www.youtube.com/watch?v=nWTvXbQHwWs
<K-ballo> ms[m]: i'll give that a try that later this week
<ms[m]> K-ballo: 👍️
<ms[m]> the alternative is we just merge it and you try it out with PR, we can always change it if it doesn't work
hkaiser has quit [Quit: bye]
hkaiser has joined #ste||ar
nanmiao11 has joined #ste||ar
akheir has joined #ste||ar
hkaiser has quit [Quit: bye]
Vir has quit [Ping timeout: 240 seconds]
Vir has joined #ste||ar
diehlpk_work has joined #ste||ar
hkaiser has joined #ste||ar
nanmiao11 has quit [Remote host closed the connection]
bita has joined #ste||ar
weilewei has joined #ste||ar
<K-ballo> it's been semi-officially announced, I will be allowed to leave the city starting december (for the summer season)
<gonidelis[m]> how long has it been? like 9 months?
<K-ballo> since march 19 I believe
<gonidelis[m]> wow that's a lot
<K-ballo> I came back home on the 16 or 17
<gonidelis[m]> what
<gonidelis[m]> what's your first trip ;p
<gonidelis[m]> ?
<K-ballo> I go to a beach town nearby in the summers, to escape the heat
<gonidelis[m]> oh wait a minute... is it like summer now where you are?
<K-ballo> spring
<gonidelis[m]> so google SUMMER of code as a tiltle, is a little biased towards the north hemishperers
<K-ballo> yeah
weilewei has quit [Remote host closed the connection]
weilewei has joined #ste||ar
bita has quit [Ping timeout: 260 seconds]
weilewei has quit [Remote host closed the connection]
<gnikunj[m]> freenode_gonidelis[m]: just realized it's spring/summers in the south hemisphere when it's fall/winter for north
<gnikunj[m]> Google summer of code does have a predisposition towards northern people in the regard
nanmiao11 has joined #ste||ar