search for: wuninitialized

FYI, After applying some patches to use gcc pragmas to disable -Wuninitialized in places we know are safe, I discovered a bug that makes this strategy much less desirable: gcc Bug 55881 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55881 Basically, gcc loses information about disabled diagnostics when inlining, to the point where the only way to supress the warning is to put...

...aikie at gmail.com> writes: > Selfhost clang. Whenever we get a warning from Clang we either fix > Clang or fix the build quite quickly. Not possible, > If you want to fix the build such that LLVM can be built -Werror clean > with GCC the right solution is going to be to turn off -Wuninitialized > when the LLVM build system detects that it is using GCC rather than > Clang (we have the inverse, where we turn on certain Clang warning > flags when we detect that we're using Clang). I would like to keep -Wuninitialized if at all possible because it does in fact detect bugs. >...

Chandler Carruth <chandlerc at google.com> writes: > The implementations of -Wuninitialized, -Wreturn-type, and a few other > GCC warnings are extremely aggressive. They have high false positive > rates with few benefits. We regularly keep -Wreturn-type working > despite this (see all of the llvm_unreachable after switch > statements), So why not add -Wno-uninitialized and f...

On Wed, 17 Feb 2016, Tom G. Christensen wrote: > On 12/02/16 04:56, Damien Miller wrote: > > Portable OpenSSH is available via Git at > > https://anongit.mindrot.org/openssh.git/ or via a mirror on Github at > > https://github.com/openssh/openssh-portable > > > > I'm seeing a hang in the testsuite on Solaris: > run test transfer.sh ... > transfer data:

...roduces Clang warnings & break other people's builds and you'll receive code that other people have committed that's Clang clean but produces GCC warnings. If you want to fix the build such that LLVM can be built -Werror clean with GCC the right solution is going to be to turn off -Wuninitialized when the LLVM build system detects that it is using GCC rather than Clang (we have the inverse, where we turn on certain Clang warning flags when we detect that we're using Clang). > How about initializing things to a garbage value and then doing an > assert after all the following condi...

...version information & suppress certain known-bad warnings on > > specific GCC versions. > > That would be ideal, but honestly in my experience there are very few > gcc warnings that should be ignored. Which ones do you think should be > ignored? > The implementations of -Wuninitialized, -Wreturn-type, and a few other GCC warnings are extremely aggressive. They have high false positive rates with few benefits. We regularly keep -Wreturn-type working despite this (see all of the llvm_unreachable after switch statements), but the fix to silence GCC's -Wuninitialized false positi...

David Blaikie <dblaikie at gmail.com> writes: > The other point Chandler was making, though, was that this sort of fix > means that other tools (Valgrind/MemSan) won't catch a broader class > of errors because we will have silenced them too. Does buildbot do a valgrind build with the same frequency as any other build? If so, then either we should fix the warnings or we should

David Blaikie <dblaikie at gmail.com> writes: >>> There's little effort to keep the GCC build warning clean, >> >> Why? It seems like a pertty important compiler to support. > > It has some silly warnings (at least in some versions) that we don't > want to workaround/suppress. Arguably we could have the build system > check version information &

...has an internal build system & I could do my development there, but I tend to develop with an upstream-style CMake+Ninja (& selfhosting) setup)) >> If you want to fix the build such that LLVM can be built -Werror clean >> with GCC the right solution is going to be to turn off -Wuninitialized >> when the LLVM build system detects that it is using GCC rather than >> Clang (we have the inverse, where we turn on certain Clang warning >> flags when we detect that we're using Clang). > > I would like to keep -Wuninitialized if at all possible because it does >...

> Portable OpenSSH is also available via [...] Github: https://github.com/openssh/openssh-portable > > Running the regression tests supplied with Portable OpenSSH does not require installation and is a simply: > > $ ./configure && make tests I was going to try this on Kali Linux (latest version), but ran into trouble right away. No "configure" script exists

On Thu, Jun 07, 2018 at 06:14:42PM -0700, PGNet Dev wrote: > On 6/7/18 6:08 PM, Darren Tucker wrote: > > Well the intent is you should be able to set CC and LD to whatever you > > want as long as they work. In this case, the OSSH_CHECK_LDFLAG_LINK > > test invokes autoconf's AC_LINK_IFELSE with uses CC not LD. I'm not > > sure what to do about it yet though. I

...Translate v4 in v6 hack: yes BSD Auth support: no Random number source: Privsep sandbox style: seccomp_filter Host: x86_64-pc-linux-gnu Compiler: /usr/bin/gcc-8 Compiler flags: -g -O2 -pipe -Wall -Wpointer-arith -Wuninitialized -Wsign-compare -Wformat-security -Wsizeof-pointer-memaccess -Wno-pointer-sign -Wno-unused-result -fno-strict-aliasing -mfunction-return=thunk -mindirect-branch=thunk -D_FORTIFY_SOURCE=2 -ftrapv -fno-builtin-memset -fstack-protector-strong -fPIE Preprocessor flags: -D_XOPEN_SOURCE=600 -D_BSD_SOUR...

Hi, Ive just downloaded and build the portable openssh-5.0p1 source on my Linux box, and when I add the CFLAGS '-Wshadow -Wpointer-arith -Wcast-qual -W' I get a lot of warnings of the following type: - -Wuninitialized is not supported without -O - cast discards qualifiers from pointer target type - warning: `foo' is not at beginning of declaration - cast discards qualifiers from pointer target type - unused parameter 'foo' - declaration of 'foo' shadows a global declaration - empty body in an...

On 1/2/2013 10:37 PM, greened at obbligato.org wrote: > Chandler Carruth <chandlerc at google.com> writes: > >> but the fix to silence GCC's -Wuninitialized false positives actively >> degrades the quality of the code -- it forces dead stores to >> variables. These dead stores are a waste and prevent tools like >> Valgrind from finding very real bugs in the logic which cause a >> variable to be left uninitialized. > > I...

Is it possible to add any flags to this command so that the resulting compile runs perfectly fine (-c builds, but does not work)? llvm-gcc -o conftest -g -O2 -Wall -Wpointer-arith -Wuninitialized -Wsign-compare -Wno-pointer-sign -Wformat-security -fno-builtin-memset -emit-llvm <filename.c> where <filename.c> contains #include <stdio.h> int main() { exit(0); } Thanks in advance for any assistance.

...tive output may be truncated writing up to 511 bytes into a region of size between 509 and 1020 [-Wformat-truncation=] > snprintf(encoded, sizeof(encoded), "%s%s%c%s", HASH_MAGIC, uu_salt, not sure yet. . > gcc -O2 -mcpu=powerpc -D_LINUX_SOURCE_COMPAT -pipe -Wall -Wpointer-arith -Wuninitialized -Wsign-compare -Wformat-security -Wsizeof-pointer-memaccess -Wno-pointer-sign -Wno-unused-result -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -ftrapv -fno-builtin-memset -I. -I. -I/opt/freeware/include -I/opt/phs/include -DSSHDIR=\"/usr/local/etc\" -D_PATH_SSH_PROGRAM=\"/usr/local/bin/...

Hi, I tried to build on AIX 5.2 and 5.3 and found a problem with openssh-4.4p1 / openssl-0.9.8d during make: when using gcc I get make echo (cd openbsd-compat && make) /usr/bin/gcc -g -O2 -Wall -Wpointer-arith -Wuninitialized -Wsign-compare -I. -I.. -I. -I./.. -DHAVE_CONFIG_H -c daemon.c daemon.c:81: warning: implicit declaration of function `open' daemon.c:81: error: `O_RDWR' undeclared (first use in this function) daemon.c:81: error: (Each undeclared identifier is reported only once daemon.c:81: error: for...

Good Day to You! THANKS for ALL your work on this project! We appreciate any help you can give! ----We are attempting to install OpenSSH v4.3p2 on OpenStep 4.2 for Intel -----our configure completes but when we run make we get: labnx02:136# make cc -g -O2 -Wall -Wpointer-arith -Wuninitialized -I. -I. -I/usr/local/ssl/include -I/usr/local/include -DSSHDIR=\"/usr/local/etc\" -D_PATH_SSH_PROGRAM=\"/usr/local/bin/ssh\" -D_PATH_SSH_ASKPASS_DEFAULT=\"/usr/local/libexec/ssh-askpass\" -D_PATH_SFTP_SERVER=\"/usr/local/libexec/sftp-server\" -D_PA...

...an simply ignoring warnings and then missing > a real bug in the haystack of warning messages. Definitely agree with that. Our project coding standards require _zero_ warnings at commit time (but that only applies to our code, not imported libraries). > I've committed fixes to lots of -Wuninitialized warnings in my tree. > It's all just initializing local variables, which shouldn't result in > extra stores. What do you think the initialization is? Something has to write the initial value, and that write is frequently pointless. The real problem with this specific warning is tha...

On Feb 26, 2009, at 10:16 AMPST, Brice Lin wrote: > Is it possible to add any flags to this command so that the resulting > compile runs perfectly fine (-c builds, but does not work)? > > llvm-gcc -o conftest -g -O2 -Wall -Wpointer-arith -Wuninitialized > -Wsign-compare -Wno-pointer-sign -Wformat-security -fno-builtin-memset > -emit-llvm <filename.c> > > where <filename.c> contains > > #include <stdio.h> > > int main() { > exit(0); > } The line you have works fine for me. There have been a lo...