From: Nathan Chancellor <natechancellor@gmail.com>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: tsbogend@alpha.franken.de, ndesaulniers@google.com,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com, stable@vger.kernel.org
Subject: Re: [PATCH] mips: vdso: fix DWARF2 warning
Date: Fri, 15 Jan 2021 12:28:03 -0700 [thread overview]
Message-ID: <20210115192803.GA3828660@ubuntu-m3-large-x86> (raw)
In-Reply-To: <20210115191330.2319352-1-anders.roxell@linaro.org>
On Fri, Jan 15, 2021 at 08:13:30PM +0100, Anders Roxell wrote:
> When building mips tinyconifg the following warning show up
>
> make --silent --keep-going --jobs=8 O=/home/anders/src/kernel/next/out/builddir ARCH=mips CROSS_COMPILE=mips-linux-gnu- HOSTCC=clang CC=clang
> /srv/src/kernel/next/arch/mips/vdso/elf.S:14:1: warning: DWARF2 only supports one section per compilation unit
> .pushsection .note.Linux, "a",@note ; .balign 4 ; .long 2f - 1f ; .long 4484f - 3f ; .long 0 ; 1:.asciz "Linux" ; 2:.balign 4 ; 3:
> ^
> /srv/src/kernel/next/arch/mips/vdso/elf.S:34:2: warning: DWARF2 only supports one section per compilation unit
> .section .mips_abiflags, "a"
> ^
>
> Rework so the mips vdso Makefile adds flag '-no-integrated-as' unless
> LLVM_IAS is defined.
>
> Link: https://github.com/ClangBuiltLinux/linux/issues/1256
> Cc: stable@vger.kernel.org # v4.19+
> Suggested-by: Nick Desaulniers <ndesaulniers@google.com>
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
I believe this is the better solution:
https://lore.kernel.org/r/20210115192622.3828545-1-natechancellor@gmail.com/
Cheers,
Nathan
next prev parent reply other threads:[~2021-01-15 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 19:13 [PATCH] mips: vdso: fix DWARF2 warning Anders Roxell
2021-01-15 19:28 ` Nathan Chancellor [this message]
2021-01-15 19:35 ` Anders Roxell
2021-01-15 20:13 ` Fangrui Song
2021-01-15 20:20 ` Nick Desaulniers
2021-01-15 23:05 ` kernel test robot
2021-01-16 0:46 ` kernel test robot
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=20210115192803.GA3828660@ubuntu-m3-large-x86 \
--to=natechancellor@gmail.com \
--cc=anders.roxell@linaro.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=stable@vger.kernel.org \
--cc=tsbogend@alpha.franken.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;
as well as URLs for NNTP newsgroup(s).