The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Nathan Chancellor <natechancellor@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	x86@kernel.org
Subject: Re: x86 - clang / objtool status
Date: Thu, 18 Jul 2019 13:58:39 -0700	[thread overview]
Message-ID: <20190718205839.GA40219@archlinux-threadripper> (raw)
In-Reply-To: <alpine.DEB.2.21.1907182223560.1785@nanos.tec.linutronix.de>

Hi Thomas,

I can't comment on the objtool stuff as it is a bit outside of my area
of expertise (probably going to be my next major learning project) but I
can comment on the other errors.

On Thu, Jul 18, 2019 at 10:40:09PM +0200, Thomas Gleixner wrote:
>  Build fails with:
> 
>   clang-10: error: unknown argument: '-mpreferred-stack-boundary=4'
>   make[5]: *** [linux/scripts/Makefile.build:279: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_resource.o] Error 1

Arnd sent a patch for this which has been picked up:
https://lore.kernel.org/lkml/CADnq5_Mm=Fj4AkFtuo+W_295q8r6DY3Sumo7gTG-McUYY=CeVg@mail.gmail.com/

> 3) allmodconfig:
>  Build fails with:
> 
>   ERROR: "__compiletime_assert_2801" [drivers/net/wireless/intel/iwlwifi/iwlwifi.ko] undefined!
>   ERROR: "__compiletime_assert_2446" [drivers/net/wireless/intel/iwlwifi/iwlwifi.ko] undefined!
>   ERROR: "__compiletime_assert_2452" [drivers/net/wireless/intel/iwlwifi/iwlwifi.ko] undefined!
>   ERROR: "__compiletime_assert_2790" [drivers/net/wireless/intel/iwlwifi/iwlwifi.ko] undefined!

Being tracked here:
https://github.com/ClangBuiltLinux/linux/issues/580

It is a clang bug but has a kernel side fix. Nick sent one but it sounds
like Intel has another one pending:

https://lore.kernel.org/lkml/20190712001708.170259-1-ndesaulniers@google.com/

https://lore.kernel.org/lkml/da053a97d771eff0ad8db37e644108ed2fad25a3.camel@coelho.fi/

>  This also emits a boatload of warnings like this:
> 
>   linux/fs/nfs/dir.c:451:34: warning: variable 'wq' is uninitialized when used within its own initialization
>       [-Wuninitialized]
>         DECLARE_WAIT_QUEUE_HEAD_ONSTACK(wq);
>                                         ^~
>   linux/include/linux/wait.h:74:63: note: expanded from macro 'DECLARE_WAIT_QUEUE_HEAD_ONSTACK'
>         struct wait_queue_head name = __WAIT_QUEUE_HEAD_INIT_ONSTACK(name)
>                                ~~~~                                  ^~~~
>   linux/include/linux/wait.h:72:33: note: expanded from macro '__WAIT_QUEUE_HEAD_INIT_ONSTACK'
>         ({ init_waitqueue_head(&name); name; })

Being tracked here:
https://github.com/ClangBuiltLinux/linux/issues/499

Has a kernel workaround patch posted but it should be fixed in clang:

https://lore.kernel.org/lkml/20190703081119.209976-1-arnd@arndb.de/

https://bugs.llvm.org/show_bug.cgi?id=42604

Thanks for continuing to test it and keeping us posted on the issues!
Nathan

  reply	other threads:[~2019-07-18 20:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18 20:40 x86 - clang / objtool status Thomas Gleixner
2019-07-18 20:58 ` Nathan Chancellor [this message]
2019-07-19  6:39   ` Thomas Gleixner
2019-07-19  7:00     ` Arnd Bergmann
2019-07-19  7:03     ` Nathan Chancellor
2019-07-24 16:57     ` Nick Desaulniers
2019-07-18 22:42 ` Nick Desaulniers
2019-07-19  6:44   ` Thomas Gleixner
2019-07-19 11:37 ` Sedat Dilek
2019-07-19 13:48   ` Sedat Dilek
2019-07-22 15:40     ` Sedat Dilek
2019-07-25  6:17       ` Sedat Dilek
2019-07-24  2:43 ` Josh Poimboeuf
2019-07-24  7:47   ` Peter Zijlstra
2019-07-24 12:37     ` Josh Poimboeuf
2019-07-24 12:55     ` Josh Poimboeuf
2019-07-24 13:35       ` Peter Zijlstra
2019-07-24 14:05         ` Josh Poimboeuf
2019-07-24 14:10         ` Peter Zijlstra
2019-07-24 16:48           ` [PATCH] objtool: Improve UACCESS coverage Peter Zijlstra
2019-07-24 16:54             ` Nathan Chancellor
2019-07-24 16:55             ` Nick Desaulniers
2019-07-24 18:30             ` Sedat Dilek
2019-07-24 18:32               ` Sedat Dilek
2019-07-24 16:52   ` x86 - clang / objtool status Peter Zijlstra
2019-07-24 17:22   ` Nick Desaulniers

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=20190718205839.GA40219@archlinux-threadripper \
    --to=natechancellor@gmail.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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