Displaying 3 results from an estimated 3 matches for "wgnu".
Did you mean:
gnu
2020 Nov 09
4
[[PATCH v1 0/3] Fix clang build warnings
New clangs emit some warnings. The code isn't wrong, but should be updated to
prevent warning creep.
Bill Wendling (3):
[klibc] dash: shell: Fix clang warnings
[klibc] dash: shell: Fix clang warnings about format string
[klibc] Kbuild: use an enum to silence a clang warning
usr/dash/eval.c | 6 +++---
usr/dash/jobs.c | 2 +-
usr/kinit/nfsmount/dummypmap.c
2013 Jul 12
1
[LLVMdev] Break in loop expression-3
...in gcc and llvm behaviour with the following code:
$ cat test.c
#include <stdio.h>
int main()
{
for(int i = 0;; ({break;}))
printf("Hello, world\n");
}
$ clang test.c -pedantic && ./a.out
test.c:5:22: warning: use of GNU statement expression extension [-Wgnu]
for(int i = 0;; ({break;}))
^
1 warning generated.
Hello, world
$ gcc test.c -std=gnu11 -pedantic && ./a.out
test.c: In function 'main':
test.c:5:23: error: break statement not within loop or switch
for(int i = 0;; ({break;}))
^...
2020 Mar 28
0
[klibc:master] dash: output: Fix clang warnings about GNU old-style field designator
...[ dash commit 1379c310a3e822a577b06e2997f0793b402ae926 ]
Building with clang results in some warnings about the use of GNU
old-style field designators:
-----------------------------------------------------------------------
output.c:86:2: warning: use of GNU old-style field designator extension [-Wgnu-designator]
nextc: 0, end: 0, buf: 0, bufsize: OUTBUFSIZ, fd: 1, flags: 0
^~~~~~
.nextc =
...
-----------------------------------------------------------------------
Fix the issue bu using C99 initializers instead.
This should be safe and should not introduce any compatibi...