linux-mips
[Top] [All Lists]

Re: MIPS: Fix build error with modern GCC for non-Cavium.

To: "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: MIPS: Fix build error with modern GCC for non-Cavium.
From: Ralf Baechle <ralf@linux-mips.org>
Date: Mon, 10 Sep 2012 19:11:57 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: <alpine.LFD.2.00.1209082024560.8926@eddie.linux-mips.org>
List-archive: <http://www.linux-mips.org/archives/linux-mips/>
List-help: <mailto:ecartis@linux-mips.org?Subject=help>
List-id: linux-mips <linux-mips.eddie.linux-mips.org>
List-owner: <mailto:ralf@linux-mips.org>
List-post: <mailto:linux-mips@linux-mips.org>
List-software: Ecartis version 1.0.0
List-subscribe: <mailto:ecartis@linux-mips.org?subject=subscribe%20linux-mips>
List-unsubscribe: <mailto:ecartis@linux-mips.org?subject=unsubscribe%20linux-mips>
References: <S1903390Ab2IDU16/20120904202758Z+1425@eddie.linux-mips.org> <alpine.LFD.2.00.1209082024560.8926@eddie.linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.21 (2010-09-15)
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

<Prev in Thread] Current Thread [Next in Thread>