search for: wtautological

When building with Clang + -Wtautological-compare and CONFIG_CPUMASK_OFFSTACK unset: arch/x86/mm/mmio-mod.c:375:6: warning: comparison of array 'downed_cpus' equal to a null pointer is always false [-Wtautological-pointer-compare] if (downed_cpus == NULL && ^~~~~~~~~~~ ~~~~ arch/x86/mm/mmio-mod.c:405...

On Mon, May 18, 2020 at 2:31 AM Nathan Chancellor <natechancellor at gmail.com> wrote: > > On Wed, Apr 08, 2020 at 01:53:23PM -0700, Nathan Chancellor wrote: > > When building with Clang + -Wtautological-compare and > > CONFIG_CPUMASK_OFFSTACK unset: > > > > arch/x86/mm/mmio-mod.c:375:6: warning: comparison of array 'downed_cpus' > > equal to a null pointer is always false [-Wtautological-pointer-compare] > > if (downed_cpus == NULL && > >...

On Wed, 8 Apr 2020 13:53:23 -0700 Nathan Chancellor <natechancellor at gmail.com> wrote: > When building with Clang + -Wtautological-compare and > CONFIG_CPUMASK_OFFSTACK unset: > > arch/x86/mm/mmio-mod.c:375:6: warning: comparison of array 'downed_cpus' > equal to a null pointer is always false [-Wtautological-pointer-compare] > if (downed_cpus == NULL && > ^~~~~~~~~~~ ~...

On Wed, Apr 8, 2020 at 10:53 PM Nathan Chancellor <natechancellor at gmail.com> wrote: > > When building with Clang + -Wtautological-compare and > CONFIG_CPUMASK_OFFSTACK unset: > Hi Nathan, thanks for the quick patch. I can confirm I have no CONFIG_CPUMASK_OFFSTACK set. Regards, - Sedat - > arch/x86/mm/mmio-mod.c:375:6: warning: comparison of array 'downed_cpus' > equal to a null pointer is always fals...

On Wed, Apr 8, 2020 at 11:12 PM Sedat Dilek <sedat.dilek at gmail.com> wrote: > > On Wed, Apr 8, 2020 at 10:53 PM Nathan Chancellor > <natechancellor at gmail.com> wrote: > > > > When building with Clang + -Wtautological-compare and > > CONFIG_CPUMASK_OFFSTACK unset: > > > > Hi Nathan, > > thanks for the quick patch. > > I can confirm I have no CONFIG_CPUMASK_OFFSTACK set. > Feel free to add appropriate credits: Tested-by: Sedat Dilek <sedat.dilek at gmail.com> Regards,...

On Wed, Apr 08, 2020 at 01:53:23PM -0700, Nathan Chancellor wrote: > When building with Clang + -Wtautological-compare and > CONFIG_CPUMASK_OFFSTACK unset: > > arch/x86/mm/mmio-mod.c:375:6: warning: comparison of array 'downed_cpus' > equal to a null pointer is always false [-Wtautological-pointer-compare] > if (downed_cpus == NULL && > ^~~~~~~~~~~ ~...

...0700 Nick Desaulniers <ndesaulniers at google.com> wrote: > On Mon, May 18, 2020 at 2:31 AM Nathan Chancellor > <natechancellor at gmail.com> wrote: > > > > On Wed, Apr 08, 2020 at 01:53:23PM -0700, Nathan Chancellor wrote: > > > When building with Clang + -Wtautological-compare and > > > CONFIG_CPUMASK_OFFSTACK unset: > > > > > > arch/x86/mm/mmio-mod.c:375:6: warning: comparison of array 'downed_cpus' > > > equal to a null pointer is always false [-Wtautological-pointer-compare] > > > if (downed_cpus ==...

...Make all warnings into errors. > > and so its effect depends on what other flags are used (people typically use > -Wall, and most new versions of both gcc and clang add more warnings to > -Wall -- I read this week exactly such a discussion about the interaction of > -Werror with -Wtautological-constant-compare as part of -Wall in clang > trunk). > >> Is there a way to get R CMD check to not raise warnings in cases like >> this? I know I could modify the C library's configure.ac (which is >> used to generate the configure script) but I'd prefer to leave the...

On recent builds of R-devel, R CMD check gives a WARNING when some compiler warning flags are detected, such as -Werror, because they are non-portable. This appears to have been added in this commit: https://github.com/wch/r-source/commit/2e80059 I'm working on a package where these compiler warning flags are present in a Makefile generated by a configure script -- that is, the configure

...-Werror Make all warnings into errors. and so its effect depends on what other flags are used (people typically use -Wall, and most new versions of both gcc and clang add more warnings to -Wall -- I read this week exactly such a discussion about the interaction of -Werror with -Wtautological-constant-compare as part of -Wall in clang trunk). > Is there a way to get R CMD check to not raise warnings in cases like > this? I know I could modify the C library's configure.ac (which is > used to generate the configure script) but I'd prefer to leave the > library's...

...on what other flags are used >>> (people typically use -Wall, and most new versions of >>> both gcc and clang add more warnings to -Wall -- I read >>> this week exactly such a discussion about the >>> interaction of -Werror with >>> -Wtautological-constant-compare as part of -Wall in >>> clang trunk). >>> >>>> Is there a way to get R CMD check to not raise warnings >>>> in cases like this? I know I could modify the C >>>> library's configure.ac (which is used to g...

...CC fseeko.lo CC getgroups.lo CC ioctl.lo CC mktime.lo CC openpty.lo CC printf-args.lo CC printf-parse.lo CC pthread_sigmask.lo CC random_r.lo CC rawmemchr.lo CC regex.lo In file included from regex.c:70: ./regex_internal.c:1392:11: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare] if (idx < 0 || idx >= set->nelem) ~~~ ^ ~ 1 warning generated. CC secure_getenv.lo CC timegm.lo CC vasnprintf.lo CCLD libgnu.la GEN charset.alias GEN ref-add.sed GEN ref-del.sed Making all in include Making all in libvirt Making all in src GEN libvirt_access.xml GEN libvirt_access...

...s into errors. >> >> and so its effect depends on what other flags are used (people typically use >> -Wall, and most new versions of both gcc and clang add more warnings to >> -Wall -- I read this week exactly such a discussion about the interaction of >> -Werror with -Wtautological-constant-compare as part of -Wall in clang >> trunk). >> >>> Is there a way to get R CMD check to not raise warnings in cases like >>> this? I know I could modify the C library's configure.ac (which is >>> used to generate the configure script) but I'd...

...cess -Wstrict-aliasing -Wstrict-prototypes -Wstringop-truncation -Wsuggest-attribute=cold -Wsuggest-attribute=const -Wsuggest-attribute=format -Wsuggest-attribute=noreturn -Wsuggest-attribute=pure -Wsuggest-final-methods -Wsuggest-final-types -Wswitch -Wswitch-bool -Wswitch-unreachable -Wsync-nand -Wtautological-compare -Wtrampolines -Wtrigraphs -Wtype-limits -Wuninitialized -Wunknown-pragmas -Wunused -Wunused-but-set-parameter -Wunused-but-set-variable -Wunused-function -Wunused-label -Wunused-local-typedefs -Wunused-parameter -Wunused-result -Wunused-value -Wunused-variable -Wvarargs -Wvariadic-macros -W...

...on what other flags are used >>>> (people typically use -Wall, and most new versions of >>>> both gcc and clang add more warnings to -Wall -- I read >>>> this week exactly such a discussion about the >>>> interaction of -Werror with >>>> -Wtautological-constant-compare as part of -Wall in >>>> clang trunk). >>>> >>>>> Is there a way to get R CMD check to not raise warnings >>>>> in cases like this? I know I could modify the C >>>>> library's configure.ac (which is used to g...

...speed improvements for large inputs. [r321871](http://reviews.llvm.org/rL321871). ## Clang commits * Clang will use a recent addition to the libLLVMOption API to suggest correctly spelled driver options when an unrecognised argument is given. [r321917](http://reviews.llvm.org/rL321917). * The `-Wtautological-constant-compare` warning has intentionally limited and is now disabled by default. As described in the commit message, there are a number of cases where the warning may not be correctly given but unhelpful in identifying buggy code. [r321691](http://reviews.llvm.org/rL321691). ## Other project c...

On 19 Jan 2018, at 17:11, Hans Wennborg <hans at chromium.org> wrote: > > On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric <dimitry at andric.com> wrote: >> On 18 Jan 2018, at 15:03, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: >>> >>> Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >>>> On 17 Jan 2018, at 18:53, Hans Wennborg

On Thu, Sep 24, 2020 at 2:58 PM Ján Tomko <jtomko@redhat.com> wrote: > On a Thursday in 2020, Wei Wang wrote: > >Seems it didn't appear on the mailing list, resent it. > > > > Hi folks, > > > >I'm trying to build libvirt using meson with the latest upstream libvirt, > >but the compilation fails: > >(followed on

On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 18 Jan 2018, at 15:03, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: >> >> Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >>> On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers >>> <release-testers at lists.llvm.org> wrote: >>>> Start

...are used >>>>> (people typically use -Wall, and most new versions of >>>>> both gcc and clang add more warnings to -Wall -- I read >>>>> this week exactly such a discussion about the >>>>> interaction of -Werror with >>>>> -Wtautological-constant-compare as part of -Wall in >>>>> clang trunk). >>>>> >>>>>> Is there a way to get R CMD check to not raise warnings >>>>>> in cases like this? I know I could modify the C >>>>>> library's configure.ac...