search for: wpedantic

...space/LLVM/llvm/projects/compiler-rt/lib/tsan/rtl/tsan_report.cc: In function ‘const char* __tsan::ReportTypeString(__tsan::ReportType, __sanitizer::uptr)’: ~/workspace/LLVM/llvm/projects/compiler-rt/lib/tsan/rtl/tsan_report.cc:95:41: warning: ISO C++ does not allow ?: with omitted middle operand [-Wpedantic] return GetReportHeaderFromTag(tag) ?: "race on external object"; ^ ~/workspace/LLVM/llvm/projects/compiler-rt/lib/tsan/rtl/tsan_report.cc:95:43: warning: ISO C++ forbids omitting the middle term of a ?: expression [-Wpedantic] return Get...

On 2019-11-27, Damien Miller <djm at mindrot.org> wrote: > applied, thanks. Surprised the fairly aggressive set of -W flags we use > by default didn't catch this... This can be caught with -Wpedantic, which seems to catch a few more instances of this, as well as passing non-void pointers to printf for the `%p` format specifier. Patches attached for these. However, it also catches conversion from dlsym result (void *) to function pointer, which is not allowed in ISO C, but POSIX requires it to...

...void (*)) R_GetCCallable("bdsmatrix", "bdsmatrix_prod4"); ??? fun(nrow, nblock, bsize, bmat, rmat, nfrail, y); ??? } .. The winbuilder run is flagging all of these with bdsmatrix_stub.h:22:6: warning: ISO C forbids assignment between function pointer and 'void *' [-Wpedantic] ? fun = (void (*)) R_GetCCallable("bdsmatrix", "bdsmatrix_prod4"); Ignore?? Or should these lines have been written in a different way? Terry T.

ninja all check-xray [0/981] Building libLLVMTableGen for native TableGen... ninja: no work to do. [673/979] Linking CXX shared library lib/liblldCommon.so.6.0.0svn FAILED: lib/liblldCommon.so.6.0.0svn : && /usr/bin/clang++-3.9 -fPIC -Wpedantic -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -fcolor-diagnostics -ffunction-se...

...ated. 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;})) ^ test.c:5:21: warning: ISO C forbids braced-groups within expressions [-Wpedantic] for(int i = 0;; ({break;})) I asked gcc developers about that fact, they answered that gcc is correct here, because statement expressions don't inherit the surrounding context. So, it seems to be an llvm bug. Kind regards, Markin Alex

...-DCMAKE_ASM_COMPILER=clang-3.9 -DLLVM_USE_LINKER=gold -DLLVM_USE_SPLIT_DWARF=On -DBUILD_SHARED_LIBS=ON -DLLVM_OPTIMIZED_TABLEGEN=On -DCOMPILER_RT_BUILD_XRAY=On -DLLVM_ENABLE_ASSERTIONS=On -DCOMPILER_RT_INCLUDE_TESTS=On -DLLVM_ENABLE_SPHINX=On -DSPHINX_WARNINGS_AS_ERRORS=On -DCMAKE_CXX_FLAGS="-Wpedantic" -DCMAKE_CXX_COMPILER_LAUNCHER=ccache ../llvm I'm building in Linux, x86_64. Cheers > > Thanks, > -Chris > >> On Oct 3, 2017, at 4:58 AM, Dean Michael Berris <dean.berris at gmail.com> wrote: >> >> Hi llvm-dev, >> >> I have unit tests...

This is not valid in ISO C. --- ssh-sk.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ssh-sk.c b/ssh-sk.c index 2b25c42f..3d6ac3d0 100644 --- a/ssh-sk.c +++ b/ssh-sk.c @@ -153,7 +153,7 @@ sshsk_free_enroll_response(struct sk_enroll_response *r) freezero(r->signature, r->signature_len); freezero(r->attestation_cert, r->attestation_cert_len); freezero(r,

...); >> fun(nrow, nblock, bsize, bmat, rmat, nfrail, y); >> } >> >> .. >> >> The winbuilder run is flagging all of these with >> >> bdsmatrix_stub.h:22:6: warning: ISO C forbids assignment between function >> pointer and 'void *' [-Wpedantic] >> fun = (void (*)) R_GetCCallable("bdsmatrix", "bdsmatrix_prod4"); >> >> Ignore? Or should these lines have been written in a different way? >> >> Terry T. >> >> ______________________________________________ >> R-devel at r-p...

...IMIT_MACROS -D NDEBUG /home/stark/src/llvm/lib/Support/ARMBuildAttrs.cpp -quiet -dumpbase ARMBuildAttrs.cpp -mtune=generic -march=x86-64 -auxbase-strip CMakeFiles/LLVMSupport.dir/ARMBuildAttrs.cpp.o -O3 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -Wpedantic -Wno-long-long -Wno-maybe-uninitialized -Wnon-virtual-dtor -Wno-comment -std=c++11 -fvisibility-inlines-hidden -ffunction-sections -fdata-sections -fPIC -fno-exceptions -fno-rtti -o /tmp/ccTTfqUE.s stark 26467 0.0 0.0 14452 932 pts/3 S+ 18:50 0:00 grep LLVMSupp -- greg

...x", "bdsmatrix_prod4"); > fun(nrow, nblock, bsize, bmat, rmat, nfrail, y); > } > > .. > > The winbuilder run is flagging all of these with > > bdsmatrix_stub.h:22:6: warning: ISO C forbids assignment between function > pointer and 'void *' [-Wpedantic] > fun = (void (*)) R_GetCCallable("bdsmatrix", "bdsmatrix_prod4"); > > Ignore? Or should these lines have been written in a different way? > > Terry T. > > ______________________________________________ > R-devel at r-project.org mailing list > htt...

..., bsize, bmat, rmat, nfrail, y); >>> } >>> >>> .. >>> >>> The winbuilder run is flagging all of these with >>> >>> bdsmatrix_stub.h:22:6: warning: ISO C forbids assignment between >>> function pointer and 'void *' [-Wpedantic] >>> fun = (void (*)) R_GetCCallable("bdsmatrix", "bdsmatrix_prod4"); >>> >>> Ignore? Or should these lines have been written in a different way? >>> >>> Terry T. >>> >>> __________________________________________...

Hi llvm-dev, I have unit tests set up in the XRay implementation (compiler-rt/lib/xray/tests/unit) following the pattern that the TSAN and other sanitiser unit tests. However, I'm running into the following problem: When I make changes to the runtime (in this case, XRay) and do `ninja all check-xray`, it seems that the unit tests don't get re-liked to the new version of the runtime. It

+ cfe-dev > On Mar 28, 2016, at 1:23 PM, Harlan Haskins via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi all, > > Recently I’ve noticed in coverage profiles that llvm_unreachable and the like are considered uncovered because there’s no special behavior in instrumentation to ‘ignore’ noreturn paths. FWIW, Daniel Dunbar and a few others have brought up the lack of a

Hi all, Recently I’ve noticed in coverage profiles that llvm_unreachable and the like are considered uncovered because there’s no special behavior in instrumentation to ‘ignore’ noreturn paths. While I don’t necessarily think it’s ideal to ignore all noreturn decls, I think there’s definitely room for some heuristics around ignoring things like llvm_unreachable (perhaps opt-in?). I’m

...52b > --- /dev/null > +++ b/images/mkzero/Makefile > @@ -0,0 +1,9 @@ > +CROSS=i686-w64-mingw32- > +CFLAGS=--std=c99 > +all: mkzero.exe > +clean: > + rm -f *.exe *.o > +mkzero.exe: mkzero.o > + $(CROSS)gcc -o $@ $< -lntdll > +%.o: %.c > + $(CROSS)gcc $(CFLAGS) -Wpedantic -Wall -o $@ -c $< > diff --git a/images/mkzero/mkzero.c b/images/mkzero/mkzero.c > new file mode 100644 > index 0000000..a95794a > --- /dev/null > +++ b/images/mkzero/mkzero.c > @@ -0,0 +1,59 @@ > +/* use the NT native API to create registry key and value that contain > +...

...ges/mkzero/Makefile new file mode 100644 index 0000000..affe52b --- /dev/null +++ b/images/mkzero/Makefile @@ -0,0 +1,9 @@ +CROSS=i686-w64-mingw32- +CFLAGS=--std=c99 +all: mkzero.exe +clean: + rm -f *.exe *.o +mkzero.exe: mkzero.o + $(CROSS)gcc -o $@ $< -lntdll +%.o: %.c + $(CROSS)gcc $(CFLAGS) -Wpedantic -Wall -o $@ -c $< diff --git a/images/mkzero/mkzero.c b/images/mkzero/mkzero.c new file mode 100644 index 0000000..a95794a --- /dev/null +++ b/images/mkzero/mkzero.c @@ -0,0 +1,59 @@ +/* use the NT native API to create registry key and value that contain + a zero character */ + +#include <n...

...> @@ -0,0 +1,9 @@ > > +CROSS=i686-w64-mingw32- > > +CFLAGS=--std=c99 > > +all: mkzero.exe > > +clean: > > + rm -f *.exe *.o > > +mkzero.exe: mkzero.o > > + $(CROSS)gcc -o $@ $< -lntdll > > +%.o: %.c > > + $(CROSS)gcc $(CFLAGS) -Wpedantic -Wall -o $@ -c $< > > diff --git a/images/mkzero/mkzero.c b/images/mkzero/mkzero.c > > new file mode 100644 > > index 0000000..a95794a > > --- /dev/null > > +++ b/images/mkzero/mkzero.c > > @@ -0,0 +1,59 @@ > > +/* use the NT native API to create registr...

I've been guilty several times recently of committing code that introduced build warnings. It's a poor excuse, but my excuse is that I've been working on code for Windows and LLVM doesn't enable strict warnings by default on Windows and produces nearly half a million warnings (literally) if you manually turn them on. As such, I thought I'd make an effort to see what it would

And again... LLVM_BUILD_LLVM_DYLIB:BOOL=ON LLVM_LINK_LLVM_DYLIB:BOOL=ON This one is the good one... maybe. On Tue, Sep 6, 2016 at 11:35 PM, Alexandre Isoard < alexandre.isoard at gmail.com> wrote: > That is because I mistyped it: > LLVM_ENABLE_LLVM_DYLIB:BOOL=ON > LLVM_LINK_LLVM_DYLIB:BOOL=ON > > On Tue, Sep 6, 2016 at 11:31 PM, Wink Saville <wink at saville.com>

--- images/README | 15 +++++++++++++++ images/mkzero/Makefile | 7 +++++++ images/mkzero/mkzero.c | 48 ++++++++++++++++++++++++++++++++++++++++++++++++ images/special | Bin 0 -> 8192 bytes 4 files changed, 70 insertions(+) create mode 100644 images/mkzero/Makefile create mode 100644 images/mkzero/mkzero.c create mode 100644 images/special diff --git a/images/README