public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <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: Mon, 21 Jan 2008 01:53:00 -0000 [thread overview]
Message-ID: <20080121011032.17068.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34841-13529@http.gcc.gnu.org/bugzilla/>
------- Comment #22 from manu at gcc dot gnu dot org 2008-01-21 01:10 -------
"make check" failing is expected since there is undefined behaviour in the
program and we warn about it with -Wstrict-overflow=5 (I guess that we warn
with lower values as well, probably simply with -Wstrict-overflow). So this is
a duplicate of PR 32102.
About the signed/unsigned warnings, it seems a minor issue. But if you still
want us to investigate it, please open a new PR (this one got a bit messy). If
you include just the relevant floating_point_test.c file and the headers to
make it compile (or better, use -save-temps and attach floating_point_test.i),
then we can easily reproduce the bug at will and investigate it. Thanks.
*** This bug has been marked as a duplicate of 32102 ***
--
manu at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |DUPLICATE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34841
next prev parent reply other threads:[~2008-01-21 1:11 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
2008-01-18 2:11 ` sergstesh at yahoo dot com
2008-01-18 2:11 ` pinskia at gcc dot gnu dot org
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 [this message]
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=20080121011032.17068.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: 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).