diff options
| author | Heiko Carstens <hca@linux.ibm.com> | 2026-10-05 11:22:56 +0200 |
|---|---|---|
| committer | Heiko Carstens <hca@linux.ibm.com> | 2026-10-09 15:35:22 +0200 |
| commit | 833ee20e712bd0c71435feddaa7b578799fe50c6 (patch) | |
| tree | fb5f2a437e66ae373b7aa7ce9869b653e83d13c0 /tools/lib/python | |
| parent | 74a31be974dde1d12ed9db131b413c519f8fc429 (diff) | |
| download | linux-next-833ee20e712bd0c71435feddaa7b578799fe50c6.tar.gz linux-next-833ee20e712bd0c71435feddaa7b578799fe50c6.zip | |
s390/dis: Mark non-NUL-terminated character arrays with __nonstring
With [1] the generated string initializers were changed to use an
array instead of a non-NUL-terminated string. The reason was that GCC 15
warns about string initializers that truncate the NUL terminator with
-Wunterminated-string-initialization.
The better solution is to use the __nonstring annotation, which exists
to deal exactly with this problem. Therefore use it and basically
revert [1] in order to generate more readable initializers:
Before:
[LONG_INSN_ALGHSIK] = { 'a', 'l', 'g', 'h', 's', 'i', 'k', },
After:
[LONG_INSN_ALGHSIK] = "alghsik",
[1] commit 7cbae7ea3de5 ("s390/tools: Use array instead of string initializer")
Reviewed-by: Jens Remus <jremus@linux.ibm.com>
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions
