Lines Matching refs:with

9 intersection with the -fbounds-safety C extension.
22 `strncmp` is always wrong with -fbounds-safety, and it's unavailable as a
31 Using `strncmp` with two NUL-terminated strings is uncommon and it has no
43 # The problems with string functions
71 terminated string. Because of coexistence with `strn` functions that make no
87 # Changes with -fbounds-safety
91 prevents confusing the two in the way that is problematic with `strlcpy`, for
101 -fbounds-safety and XNU enshrine this practice with the following additions:
190 `tsnprintf` or `strbufcpy` once. As a quick reference, with -fbounds-safety
195 build a string with successive calls to `scnprintf`, you would use
200 (usually to interoperate with copy APIs that need a pointer and a byte count).
205 (if you need it). Also keep in mind that in code which pervasively deals with