From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: MIPS: Fix build error with modern GCC for non-Cavium.
Date: Mon, 10 Sep 2012 19:11:57 +0200 [thread overview]
Message-ID: <20120910171157.GC24448@linux-mips.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1209082024560.8926@eddie.linux-mips.org>
On Sat, Sep 08, 2012 at 08:28:26PM +0100, Maciej W. Rozycki wrote:
> > An empty default block is not allowed so add a ; as empty statement to
> > make gcc happy.
>
> A dummy "break" is the usual solution though. I don't think GCC ever
> complains if it sees it unreachable after a "return" -- in a sense it is
> just as unreachable as this null instruction is.
I wasn't overly picky. Whatever gets the stuff to build correctly. I'm
doing one final round of test builds over all -stable branches before
dropping most of them like radioctive rocks. But more on that later.
Ralf
next prev parent reply other threads:[~2012-09-10 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1903390Ab2IDU16/20120904202758Z+1425@eddie.linux-mips.org>
2012-09-08 19:28 ` MIPS: Fix build error with modern GCC for non-Cavium Maciej W. Rozycki
2012-09-10 17:11 ` Ralf Baechle [this message]
2012-09-15 22:42 ` Maciej W. Rozycki
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=20120910171157.GC24448@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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.