From: Adrian Hunter <adrian.hunter@intel.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Stephen Boyd <sboyd@kernel.org>, John Stultz <jstultz@google.com>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: tinyconfig: kernel/time/timekeeping.c:286:1: error: no return statement in function returning non-void [-Werror=return-type]
Date: Wed, 10 Apr 2024 18:35:01 +0300 [thread overview]
Message-ID: <b9d3138b-000a-49ca-bc82-6517231eca91@intel.com> (raw)
In-Reply-To: <52cf2d1a-76ec-48cb-96c3-211fa1eb721a@intel.com>
On 10/04/24 16:03, Adrian Hunter wrote:
> On 10/04/24 13:56, Naresh Kamboju wrote:
>> The powerpc,s390, superSh and sparc tinyconfig builds failed due to
>> following build
>> warnings / errors on the Linux next-20240410 with gcc-13 and gcc-11.
>>
>> List build failures:
>> ---
>> * s390, build
>> - gcc-13-tinyconfig - failed
>> - gcc-8-tinyconfig - failed
>>
>> * sh, build
>> - gcc-11-tinyconfig - failed
>>
>> * sparc, build
>> - gcc-11-tinyconfig - failed
>>
>> * mips, build
>> - gcc-12-tinyconfig - failed
>> - gcc-8-tinyconfig - failed
>>
>> * powerpc, build
>> - gcc-13-tinyconfig - failed
>> - gcc-8-tinyconfig - failed
>>
>> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>>
>> Build log:
>> --------
>> kernel/time/timekeeping.c: In function 'timekeeping_debug_get_ns':
>> kernel/time/timekeeping.c:286:1: error: no return statement in
>> function returning non-void [-Werror=return-type]
>> 286 | }
>> | ^
>> cc1: some warnings being treated as errors
>
> Using unreachable() in the default BUG() seems to make this go
> away.
>
> diff --git a/include/asm-generic/bug.h b/include/asm-generic/bug.h
> index 6e794420bd39..891bd9b0be70 100644
> --- a/include/asm-generic/bug.h
> +++ b/include/asm-generic/bug.h
> @@ -156,7 +156,7 @@ extern __printf(1, 2) void __warn_printk(const char *fmt, ...);
>
> #else /* !CONFIG_BUG */
> #ifndef HAVE_ARCH_BUG
> -#define BUG() do {} while (1)
> +#define BUG() do { do {} while (1) ; unreachable(); } while (0)
> #endif
>
> #ifndef HAVE_ARCH_BUG_ON
>
Patch here:
https://lore.kernel.org/all/20240410153212.127477-1-adrian.hunter@intel.com/
prev parent reply other threads:[~2024-04-10 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 10:56 Naresh Kamboju
2024-04-10 13:03 ` Adrian Hunter
2024-04-10 15:35 ` Adrian Hunter [this message]
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=b9d3138b-000a-49ca-bc82-6517231eca91@intel.com \
--to=adrian.hunter@intel.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®