Page MenuHomeFreeBSD

netbsd-tests t_regex_att: Use __nonstring for a non-string constant
ClosedPublic

Authored by jhb on Jan 25 2026, 4:54 AM.
Tags
None
Referenced Files
F167792438: D54866.id170549.diff
Mon, Aug 24, 2:12 PM
F167792433: D54866.id170549.diff
Mon, Aug 24, 2:12 PM
F167792426: D54866.id170549.diff
Mon, Aug 24, 2:12 PM
F167792413: D54866.id170549.diff
Mon, Aug 24, 2:12 PM
Unknown Object (File)
Tue, Aug 18, 1:33 AM
Unknown Object (File)
Wed, Aug 12, 3:26 PM
Unknown Object (File)
Mon, Aug 10, 8:00 AM
Unknown Object (File)
Mon, Aug 10, 8:00 AM
Subscribers

Details

Summary

Fixes the following warning from GCC 15:

contrib/netbsd-tests/lib/libc/regex/t_regex_att.c:54:30: error: initializer-string for array of 'char' truncates NUL terminator but destination lacks 'nonstring' attribute (4 chars into 3 available) [-Werror=unterminated-string-initialization]

54 | static const char delim[3] = "\\\\\0";
   |                              ^~~~~~~~

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Jan 25 2026, 10:35 AM

LGTM. Weird that I didn't see this one with clang 21, which also has the same warnings about __nonstring. But maybe I just didn't run this test?

Definitely could be contributed upstream.

Yeah, I have no idea why clang didn't warn about this one. I wonder if clang doesn't warn if the string ends with an explicit nul?