diff options
| author | Gustavo A. R. Silva <gustavo@embeddedor.com> | 2020-02-12 00:06:18 +0300 |
|---|---|---|
| committer | Bartosz Golaszewski <bgolaszewski@baylibre.com> | 2020-03-02 10:52:55 +0300 |
| commit | ec18d7e7d28625355bf2f5c18d47c09b1cde5cde (patch) | |
| tree | bf90326702c7a14308441c35beec929426ae0634 /tools/perf/scripts/python | |
| parent | 869233f81337bfb33c79f1e7539147d52c0ba383 (diff) | |
| download | linux-ec18d7e7d28625355bf2f5c18d47c09b1cde5cde.tar.xz | |
gpio: uniphier: Replace zero-length array with flexible-array member
The current codebase makes use of the zero-length array language
extension to the C90 standard, but the preferred mechanism to declare
variable-length types such as these ones is a flexible array member[1][2],
introduced in C99:
struct foo {
int stuff;
struct boo array[];
};
By making use of the mechanism above, we will get a compiler warning
in case the flexible array does not occur last in the structure, which
will help us prevent some kind of undefined behavior bugs from being
inadvertenly introduced[3] to the codebase from now on.
This issue was found with the help of Coccinelle.
[1] https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html
[2] https://github.com/KSPP/linux/issues/21
[3] commit 76497732932f ("cxgb3/l2t: Fix undefined behaviour")
Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
