public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sergstesh at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/34841] 'make check' of libsndfile-1.0.17 fails with gcc-4.2.2 -O2 optimization, OK with -O1 one Date: Fri, 18 Jan 2008 01:53:00 -0000 [thread overview] Message-ID: <20080118014354.16317.qmail@sourceware.org> (raw) In-Reply-To: <bug-34841-13529@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from sergstesh at yahoo dot com 2008-01-18 01:43 ------- I've tried CFLAGS='-O2 -fwrapv -Wstrict-overflow' and I see no warnings at all in 'make_check.log' file - I tried "grep -i warn make_check.log". OTOH: " sergei@amdam2:/mnt/sda8/sergei/gcc4.2.x-O2_bug/gcc-4.2.2-O2/libsndfile-1.0.17> grep -i warn make.log sndfile.c:491: warning: the address of 'sf_error' will never be NULL sndfile-play.c:292: warning: the address of ‘status’ will always evaluate as ‘true’ floating_point_test.c:338: warning: comparison between signed and unsigned floating_point_test.c:388: warning: comparison between signed and unsigned floating_point_test.c:438: warning: comparison between signed and unsigned floating_point_test.c:488: warning: comparison between signed and unsigned floating_point_test.c:538: warning: comparison between signed and unsigned floating_point_test.c:588: warning: comparison between signed and unsigned floating_point_test.c:638: warning: comparison between signed and unsigned floating_point_test.c:688: warning: comparison between signed and unsigned sergei@amdam2:/mnt/sda8/sergei/gcc4.2.x-O2_bug/gcc-4.2.2-O2/libsndfile-1.0.17> ", but these warning say nothing about overflow since it's compilation, not execution. Did you mean CFLAGS='-O2 -fwrapv -Wstrict-overflow' or, rather, CFLAGS='-O2 -Wstrict-overflow' ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34841
next prev parent reply other threads:[~2008-01-18 1:44 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-18 0:30 [Bug c/34841] New: " sergstesh at yahoo dot com 2008-01-18 1:30 ` [Bug c/34841] " sergstesh at yahoo dot com 2008-01-18 1:33 ` pinskia at gcc dot gnu dot org 2008-01-18 1:37 ` sergstesh at yahoo dot com 2008-01-18 1:44 ` sergstesh at yahoo dot com 2008-01-18 1:46 ` pinskia at gcc dot gnu dot org 2008-01-18 1:53 ` sergstesh at yahoo dot com [this message] 2008-01-18 2:11 ` pinskia at gcc dot gnu dot org 2008-01-18 2:11 ` sergstesh at yahoo dot com 2008-01-18 3:21 ` ismail at pardus dot org dot tr 2008-01-18 3:58 ` sergstesh at yahoo dot com 2008-01-18 4:06 ` ismail at pardus dot org dot tr 2008-01-18 4:09 ` sergstesh at yahoo dot com 2008-01-18 4:18 ` ismail at pardus dot org dot tr 2008-01-18 11:36 ` manu at gcc dot gnu dot org 2008-01-18 14:27 ` sergstesh at yahoo dot com 2008-01-18 14:37 ` sergstesh at yahoo dot com 2008-01-18 15:23 ` manu at gcc dot gnu dot org 2008-01-18 15:26 ` manu at gcc dot gnu dot org 2008-01-18 19:12 ` manu at gcc dot gnu dot org 2008-01-18 23:47 ` sergstesh at yahoo dot com 2008-01-19 0:46 ` manu at gcc dot gnu dot org 2008-01-20 23:58 ` sergstesh at yahoo dot com 2008-01-21 1:53 ` manu at gcc dot gnu dot org 2008-01-21 7:23 ` sergstesh at yahoo dot com 2008-01-21 8:05 ` manu at gcc dot gnu dot 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=20080118014354.16317.qmail@sourceware.org \ --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: linkBe 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).