From: viro@parcelfarce.linux.theplanet.co.uk
To: John Cherry <cherry@osdl.org>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: IA32 (2.6.2 - 2004-02-05.22.30) - 3 New warnings (gcc 3.2.2)
Date: Fri, 6 Feb 2004 11:33:05 +0000 [thread overview]
Message-ID: <20040206113305.GF21151@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200402061122.i16BMZ10009537@cherrypit.pdx.osdl.net>
On Fri, Feb 06, 2004 at 03:22:35AM -0800, John Cherry wrote:
> drivers/net/ne.c:168: warning: unused variable `irq'
> drivers/scsi/imm.c:1146: warning: `ports' might be used uninitialized in this function
> drivers/scsi/ppa.c:1006: warning: `ports' might be used uninitialized in this function
Sigh... we have
switch (dev->mode) {
case IMM_NIBBLE:
case IMM_PS2:
ports = 3;
break;
case IMM_EPP_8:
case IMM_EPP_16:
case IMM_EPP_32:
ports = 8;
break;
default: /* Never gets here */
BUG();
}
...
/* use the value of 'ports' */
IOW, gcc doesn't realize that we never return from BUG(). AFAICS, it
should. Some changes of __volatile__ semantics?
next prev parent reply other threads:[~2004-02-06 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 11:22 IA32 (2.6.2 - 2004-02-05.22.30) - 3 New warnings (gcc 3.2.2) John Cherry
2004-02-06 11:33 ` viro [this message]
2004-02-06 16:52 ` Linus Torvalds
2004-02-06 18:22 ` viro
2004-02-06 18:35 ` Petr Vandrovec
2004-02-06 18:42 ` Linus Torvalds
2004-02-06 18:47 ` viro
2004-02-06 19:09 ` viro
2004-02-10 13:32 ` Dick Streefland
2004-02-10 15:44 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2004-02-08 1:00 Jon Foster
2004-02-08 5:45 ` viro
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=20040206113305.GF21151@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=cherry@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.