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 middle-end/42290] strange 'warning: "ISRA.2" may be used uninitialized in this function'
Date: Thu, 04 Feb 2010 11:26:00 -0000	[thread overview]
Message-ID: <20100204112609.7124.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42290-14164@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from manu at gcc dot gnu dot org  2010-02-04 11:26 -------
(In reply to comment #7)
> I can't reproduce this issue in current trunk (r156468)

Closing then as FIXED, the warning was caused by bug 42508.


-- 

manu at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |FIXED


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


      parent reply	other threads:[~2010-02-04 11:26 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: &#8216;ISRA.2&#8217; 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
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 [this message]

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=20100204112609.7124.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).