kr_bitcmp: adjust semantics -> memcmp (!234) · Merge requests · Knot projects / Knot Resolver · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.

Vladimír Čunát requested to merge kr_bitcmp into master Mar 15, 2017

Motivation: allow bits=0 and consequently 0.0.0.0/0 matches in view and renumber modules. https://gitter.im/CZ-NIC/knot-resolver?at=58c940c721d548df2cdfda5e

We shouldn't mix up error codes with valid results from memcmp; let's just segfault if someone passes a NULL, just as memcmp() itself.