public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/42290] strange 'warning: "ISRA.2" may be used uninitialized in this function'
Date: Sat, 26 Dec 2009 10:51:00 -0000 [thread overview]
Message-ID: <20091226105050.13709.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42290-14164@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from zsojka at seznam dot cz 2009-12-26 10:50 -------
Created an attachment (id=19393)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19393&action=view)
even more reduced testcase
I have a suspicion this warning is valid. There is an app that (sometimes)
crashes when code construction like this one is called. valgrind warns about
using uninitialized variable. Also, it started crashing when compiled with gcc
r154886 (r154830 was fine).
--
zsojka at seznam dot cz changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #19231|0 |1
is obsolete| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42290
next prev parent reply other threads:[~2009-12-26 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 23:52 [Bug c++/42290] New: strange 'warning: ‘ISRA.2’ may be used uninitialized in this function' in C++0x mode zsojka at seznam dot cz
2009-12-04 23:53 ` [Bug c++/42290] " zsojka at seznam dot cz
2009-12-04 23:54 ` [Bug middle-end/42290] " pinskia at gcc dot gnu dot org
2009-12-05 0:16 ` [Bug middle-end/42290] strange 'warning: "ISRA.2" may be used uninitialized in this function' zsojka at seznam dot cz
2009-12-26 10:51 ` zsojka at seznam dot cz [this message]
2009-12-26 11:23 ` zsojka at seznam dot cz
2009-12-30 16:29 ` manu at gcc dot gnu dot org
2010-02-04 3:01 ` zsojka at seznam dot cz
2010-02-04 11:26 ` 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=20091226105050.13709.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).