Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: [PATCH 2/2] MIPS: Optimize TLB handlers for Octeon CPUs
Date: Wed, 19 Jan 2011 11:41:15 -0800	[thread overview]
Message-ID: <4D373E5B.5010303@caviumnetworks.com> (raw)
In-Reply-To: <AANLkTinZZ2TziwkiBfhqV-3-VfXwU+EPx3OHsnTRVChT@mail.gmail.com>

On 01/19/2011 11:35 AM, Jonas Gorski wrote:
> On 28/12/2010, David Daney<ddaney@caviumnetworks.com>  wrote:
>> +#if defined(CONFIG_CAVIUM_OCTEON_CVMSEG_SIZE)&&  \
>> +    CONFIG_CAVIUM_OCTEON_CVMSEG_SIZE>  0
>> (...)
>> +#else
>> +static bool scratchpad_available(void)
>> +{
>> +	return false;
>> +}
>> +static int scratchpad_offset(int i)
>> +{
>> +	BUG();
>> +}
>> +#endif
>
> This seems to have broken the build for any non-octeon mips build:
>
>    CC      arch/mips/mm/tlbex.o
> cc1: warnings being treated as errors
> arch/mips/mm/tlbex.c: In function 'scratchpad_offset':
> arch/mips/mm/tlbex.c:112: error: no return statement in function
> returning non-void
>

Can you tell me which version of GCC you are using?

I tested it with gcc-4.5.x, BUG() may have problems if 
builtin_unreachable is not available.

David Daney

  reply	other threads:[~2011-01-19 19:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28  2:07 [PATCH 0/2] MIPS: Optimize TLB Refill for Octeon/Octeon2 David Daney
2010-12-28  2:07 ` [PATCH 1/2] MIPS: Add LDX and LWX instructions to uasm David Daney
2010-12-28 17:11   ` Ralf Baechle
2010-12-28  2:07 ` [PATCH 2/2] MIPS: Optimize TLB handlers for Octeon CPUs David Daney
2010-12-28 17:11   ` Ralf Baechle
2011-01-19 19:35   ` Jonas Gorski
2011-01-19 19:41     ` David Daney [this message]
2011-01-19 19:46       ` Jonas Gorski
2011-01-19 20:05         ` David Daney
2011-01-19 20:44           ` Jonas Gorski

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=4D373E5B.5010303@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=jonas.gorski+openwrt@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox