From: Blue Swirl <blauwirbel@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: Paul Bolle <pebolle@tiscali.nl>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] [TRIVIAL] usb-linux: remove unreachable default in switch statement
Date: Wed, 17 Mar 2010 22:15:33 +0200 [thread overview]
Message-ID: <f43fc5581003171315g7e14afdat2c31d54bb1d42bd0@mail.gmail.com> (raw)
In-Reply-To: <201003171743.06728.paul@codesourcery.com>
On 3/17/10, Paul Brook <paul@codesourcery.com> wrote:
> > > If something should never happen (as in this case) then an abort/assert
> > > is completely appropriate. Once things get that screwed up there's no
> > > right answer, and the best thing we can do is terminate immediately to
> > > try and avoid further damage.
> >
> > This case was:
> >
> > switch (foo & 0x03) {
> > case 0: case 1: case 2: case 3:
> > default:
> > }
> >
> > The default is unreachable. Having it there just introduces more code
> > that serves no purpose. Unless someone does something totally foolish
> > and changes the mask in the switch statement, there's no way it will
> > ever be reachable.
>
>
> I mistakenly remembered this was using a symbolic mask rather than a literal
> 0x03. In that case I'd argue it's much easier to make the dumb error you
> describe, and the assert can be a handy cluebat.
>
> I guess it's largely personal preference - I prefer to add the default case to
> make it clear that falling through is never gong to be the right answer.
This breaks build (gcc 4.3.2):
CC usb-linux.o
cc1: warnings being treated as errors
/src/qemu/usb-linux.c: In function 'usb_linux_update_endp_table':
/src/qemu/usb-linux.c:759: error: 'type' may be used uninitialized in
this function
next prev parent reply other threads:[~2010-03-17 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 12:58 [Qemu-devel] [PATCH] [TRIVIAL] usb-linux: remove unreachable default in switch statement Paul Bolle
2010-03-08 13:31 ` Paul Brook
2010-03-17 15:59 ` Anthony Liguori
2010-03-17 16:14 ` Paul Bolle
2010-03-17 16:39 ` Anthony Liguori
2010-03-17 17:08 ` Paul Brook
2010-03-17 17:15 ` Anthony Liguori
2010-03-17 17:43 ` Paul Brook
2010-03-17 20:15 ` Blue Swirl [this message]
2010-03-17 20:41 ` Anthony Liguori
2010-03-17 20:56 ` Paul Bolle
2010-03-17 20:59 ` Anthony Liguori
2010-03-17 21:05 ` Blue Swirl
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=f43fc5581003171315g7e14afdat2c31d54bb1d42bd0@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=paul@codesourcery.com \
--cc=pebolle@tiscali.nl \
--cc=qemu-devel@nongnu.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).