- User Since
- Oct 2 2015, 1:17 PM (260 w, 19 h)
Thu, Sep 24
Wed, Sep 23
Yup, this matches what I envisioned when you pitched it! =)
Sure, that's reasonable- while we don't expect people to look at the output, it is good for it to look at least somewhat clean in case we need to sanity check it.
Tagging Brooks in as well for Cheri perspective
Tue, Sep 22
Mon, Sep 21
Sat, Sep 19
Why do we currently -Wno-pointer-sign? Too many false positives?
Fri, Sep 18
Thu, Sep 17
Wed, Sep 16
Tue, Sep 15
I've added the following post-patch target locally to address the build breakage on -CURRENT that I mentioned, let me know if you'd prefer to do it otherwise -- I think sed'ing it is OK if it's not worth upstreaming the expression change. I've test-built on -CURRENT/amd64 and 12.1/i386, with 11.3/amd64 in progress:
Mon, Sep 14
I think I'm going to go ahead and commit this in the coming days -- FWIW, I hacked together a reallllly primitive interface for browsing warnings by crude 'path' (based solely on output, so not perfect) : https://warns.kevans.dev/ -- this should work in the interim until we can get something in CI proper. I'll hack together some pretty graphs from it when it gets a couple more builds under its belt.
Sun, Sep 13
Sat, Sep 12
Fri, Sep 11
This seems reasonable, though getenv_bool is defined static but declared/used as if it were not. :-)
Thu, Sep 10
Wed, Sep 9
I took a "trust, but verify" stance and confirmed that it built on 12i386 and 11amd64. :-)
Would you prefer to receive attribution for this review at your phab email address (@gmx) or bugzilla (@siemens)?
Tue, Sep 8
Rework, drop *.[0-9] from FILEPAT and use hopefully less-fragile fingerprint comparison. This fixes the previously reported issue: