5 ms·
Yes. Two things though: 1. Hopefully none of your users run an unreleased clang from head, so you're not using anything a user will run into. 2. Consider if
by Nitramp 6y ago
Yes.
Two things though:
1. Hopefully none of your users run an unreleased clang from head, so you're not using anything a user will run into.
2. Consider if it is it worth the effort to validate every commit pushed to head, or whether you'd get more out of your investment if you only tested releases that received some more vetting (e.g. nightlies).
- saagarjha 6y agoI don’t think SQLite is literally vetting every commit. (Although kudos to them if they are!)
- progval 6y ago> 1. Hopefully none of your users run an unreleased clang from head, so you're not using anything a user will run into. Yes, but clang eventually gets released. You want to catch bugs in clang and get them fixed before that release happens.
- jfkebwjsbx 6y agoYes, but Clang is many months away from a release. It is not the same as playing with a release candidate.
- pas 6y agoIt's an automated fuzzer, it caught a bug very early, but the report got sent to SQLite instead of Clang. Probably because OSFuzz doesn't handle this distinction. (Though it might should. Or maybe usually new compiler versions catch problems in old code a lot more frequently than it catches compiler bugs. Dunno.)
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]