From: Mark Hindley <mark@hindley.org.uk>
To: Satyam Sharma <satyam@infradead.org>
Cc: Steffen Klassert <klassert@mathematik.tu-chemnitz.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Netdev Mailing List <netdev@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: [PATCH -mm 1/2] 3c59x: Fix uninitialized variable bug
Date: Thu, 6 Sep 2007 22:40:08 +0100 [thread overview]
Message-ID: <20070906214008.GA11224@hindley.org.uk> (raw)
In-Reply-To: 20070904085331.GH5944@hindley.org.uk
On Thu, Sep 06, 2007 at 03:25:55PM +0530, Satyam Sharma wrote:
> This is a GCC bug (regression, actually, as you've found out) -- no two
> ways about it. Although different from the kind Jeff mentioned couple days
> back -- that was about wising GCC up to false positives and /not/ emitting
> warnings. But here a genuine problem was not complained about, so this is
> more serious. Do you plan to open up a bug at gcc.gnu.org/bugzilla/ ?
>
Yes, I have just narrowed down a test case, which is remarkably simple!
int
main(int i)
{
int err;
if (i) {
err = 1;
}
return err;
}
Mark
prev parent reply other threads:[~2007-09-06 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.0.999.0709040340250.8504@enigma.security.iitk.ac.in >
2007-09-03 22:15 ` [PATCH -mm 1/2] 3c59x: Fix uninitialized variable bug Satyam Sharma
2007-09-03 22:22 ` [PATCH -mm 2/2] 3c59x MAINTAINERS Satyam Sharma
2007-09-04 7:55 ` Steffen Klassert
2007-09-04 8:16 ` [PATCH -mm 1/2] 3c59x: Fix uninitialized variable bug Steffen Klassert
2007-09-04 8:39 ` Satyam Sharma
2007-09-04 8:53 ` Mark Hindley
2007-09-04 9:17 ` Steffen Klassert
2007-09-04 9:35 ` Mark Hindley
2007-09-04 9:39 ` Steffen Klassert
2007-09-06 9:55 ` Satyam Sharma
2007-09-06 21:40 ` Mark Hindley [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=20070906214008.GA11224@hindley.org.uk \
--to=mark@hindley.org.uk \
--cc=jeff@garzik.org \
--cc=klassert@mathematik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=satyam@infradead.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 NNTP newsgroup(s).