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/
khuck has quit [Remote host closed the connection]
khuck has joined #ste||ar
nikunj has quit [Remote host closed the connection]
hkaiser has quit [Quit: bye]
anushi has joined #ste||ar
khuck has quit [Ping timeout: 252 seconds]
anushi has quit [Remote host closed the connection]
anushi has joined #ste||ar
anushi has quit [Remote host closed the connection]
anushi has joined #ste||ar
anushi has quit [Remote host closed the connection]
Matombo444 has joined #ste||ar
daissgr has joined #ste||ar
Matombo444 has quit [Remote host closed the connection]
jaafar has joined #ste||ar
david_pfander has joined #ste||ar
daissgr has quit [Ping timeout: 252 seconds]
anushi has joined #ste||ar
jaafar has quit [Ping timeout: 240 seconds]
anushi has quit [Remote host closed the connection]
anushi has joined #ste||ar
anushi has quit [Remote host closed the connection]
<jbjnr>
no. you mentioned that warnings were worse since the recent fix of mine
<khuck>
ah!
<khuck>
ok
<jbjnr>
so I fixed the fix cos now I see the warnings too and realize I committed the wrong stuff first time
<khuck>
I can dig it
<jbjnr>
so much for testing and code reviews :(
<khuck>
overrated
<jbjnr>
when such a big mistake goes through
<khuck>
we could add -Wall -Werror and everything would fail
<zao>
-Wohoho
<khuck>
or at least -Werror
<jbjnr>
never
<jbjnr>
-Werror is awful
<khuck>
tyranny, really
<khuck>
turning on -Wall -Werror has found quite a few little nuggets over the years for me
<jbjnr>
on a small project ok - but on something this big wherewe support N compilers etc - horror
<zao>
khuck: It's not feasible in any configuration that should build on an open-ended set of compilers and OSes.
<zao>
You can do it locally and whatnot, but it cannot go into the generic build.
<khuck>
gotta keep those compilers happy. they are our friends.
<khuck>
I wouldn't suggest it for hpx
<zao>
It only works if everyone cares about warnings up-front, which no-one does.
<zao>
_ESPECIALLY_ as people don't even _build_ examples.
<zao>
Our examples have been warning-rotten since forever.
aserio has quit [Quit: aserio]
<khuck>
I was ignoring warnings from some code that a grad student (no offense) added a few months ago, and it turns out the compiler was actually trying to tell me something
<zao>
Given our compile times of like an hour, the build-fix-test cycle is painful too, even if you just do it locally.
<khuck>
(on another project, that is)
<zao>
I don't doubt that warnings may indicate underlying problems, but they are also an endless game of whack-a-mole if you dial up the sensitivity.
<khuck>
agreed
<zao>
"hi, this implicit conversion to bool may be costly, lol"
<jbjnr>
khuck: want to win some prizes - try running our inspect tool over apex!
<khuck>
I have. hundreds of things I don't care about at all
<khuck>
"space at the end of a line" - whatever
<khuck>
especially in the middle of a comment
<khuck>
that's what happens when you use vim to auto-break wrapped lines of text
<khuck>
jbjnr: although, I have started to use that very report to clean things up
<jbjnr>
just catches me out when I run inspect on my stuff and forget that I have apex in the tree. thousands of fails.
<jbjnr>
^^cool
<khuck>
yup.
<jbjnr>
you can get vim to trim lines
<khuck>
I actually misspoke - there's some other case where that happens. at any rate, I fail to see why that's a problem worth caring about.
<khuck>
(IMHO)
<jbjnr>
I tend to agree, but since I'm working on hpx, I kinda, needa, haveta obey the crappy rules as well as the good ones :(
<jbjnr>
(zao: examples are now built as part of tests, so we should start seeing and fixing most of the issues s they appear on the dashboard etc)
<zao>
Ooh, nice.
<zao>
I'm not innocent here either, my test machine only built core+components+tests :)
<khuck>
jbjnr: yeah, understood
<khuck>
tests/examples have a way of getting crufty and rusty
<khuck>
zao: I only build core
Matombo444 has quit [Remote host closed the connection]
eschnett_ has joined #ste||ar
quaz0r has quit [Ping timeout: 244 seconds]
hkaiser has joined #ste||ar
hkaiser has quit [Read error: Connection reset by peer]