public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "antomicx at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/49863] New: -Wunused-result not behaving correctly
Date: Wed, 27 Jul 2011 10:07:00 -0000	[thread overview]
Message-ID: <bug-49863-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49863

           Summary: -Wunused-result not behaving correctly
           Product: gcc
           Version: 4.5.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: antomicx@gmail.com


With a snippet as simple as the following

# cat main.c

#include <stdlib.h>

int main() {
  system("ls");

  return 0;
}

I'm getting these, different, compilation results:

1) # gcc main.c
Output: empty

2) # gcc -Wunused-result main.c
Output: empty

3) # gcc -W -Wall -Wextra main.c
Output: empty

4) # gcc -W -Wall -Wextra -Wunused-result main.c
Output: empty

5) # gcc -O0 -W -Wall -Wextra -Wunused-result main.c 
Output: empty

6) # gcc -O1 main.c # same thing with -O2 -O3
Output: 
main.c: In function ‘main’:
main.c:4:9: warning: ignoring return value of ‘system’, declared with attribute
warn_unused_result

Why is putting -Ox with x > 0 the only way to get the correct compilation
warning when invoking the 'system' call without parsing its result?

# gcc -v

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.5.2/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
4.5.2-8ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.5 --enable-shared --enable-multiarch
--with-multiarch-defaults=x86_64-linux-gnu --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib/x86_64-linux-gnu
--without-included-gettext --enable-threads=posix
--with-gxx-include-dir=/usr/include/c++/4.5 --libdir=/usr/lib/x86_64-linux-gnu
--enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --enable-plugin --enable-gold --enable-ld=default
--with-plugin-ld=ld.gold --enable-objc-gc --disable-werror --with-arch-32=i686
--with-tune=generic --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4)


             reply	other threads:[~2011-07-27 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 10:07 antomicx at gmail dot com [this message]
2011-07-27 10:20 ` [Bug c/49863] " rguenth at gcc dot gnu.org
2011-07-27 10:30 ` antomicx at gmail dot com
2012-05-23 17:21 ` jim.king at simplivity dot com
2012-05-23 17:27 ` pinskia at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-49863-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).