From: Kees Cook <keescook@chromium.org>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
corbet@lwn.net, masahiroy@kernel.org,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com
Subject: Re: [PATCH] Documentation/llvm: add documentation on building w/ Clang/LLVM
Date: Mon, 24 Feb 2020 20:25:17 -0800 [thread overview]
Message-ID: <202002242019.A9F519A33A@keescook> (raw)
In-Reply-To: <20200225041643.GA17425@ubuntu-m2-xlarge-x86>
On Mon, Feb 24, 2020 at 09:16:43PM -0700, Nathan Chancellor wrote:
> I think the clang one should be added in a separate patch that
> solidifies that in include/linux/compiler-clang.h with a CLANG_VERSION
> macro and version check, like in include/linux/compiler-gcc.h.
Sounds good.
> ld.lld's minimum version should also be 9, what is the blocking issue
> that makes it 11?
I think I've mostly got future patches on my mind. lld before 11 will
blow up on this:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=build/link-time
(but I haven't sent this patch yet since I didn't want to break lld
until it was fixed, which it is now, but I got distracted by other
stuff).
Additionally there will be LTO, but LTO will be version-checked. Then I
was thinking about the orphan section handling, and there is very
clearly more work to be done there too... (i.e. the synthesized sections
get reported by the orphan warning before they're actually processed by
DISCARD is some cases -- I still need to isolate the behavior and open a
bug.)
--
Kees Cook
next prev parent reply other threads:[~2020-02-25 4:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 17:41 [PATCH] Documentation/llvm: add documentation on building w/ Clang/LLVM Nick Desaulniers
2020-02-24 21:20 ` Randy Dunlap
2020-02-25 0:33 ` Masahiro Yamada
2020-02-25 20:52 ` Nick Desaulniers
2020-02-26 12:00 ` Masahiro Yamada
2020-02-26 12:33 ` Sedat Dilek
2020-02-27 4:38 ` Nathan Chancellor
2020-02-25 4:08 ` Kees Cook
2020-02-25 4:16 ` Nathan Chancellor
2020-02-25 4:25 ` Kees Cook [this message]
2020-02-25 20:59 ` Nick Desaulniers
2020-02-25 21:56 ` Kees Cook
2020-02-25 22:20 ` Joe Perches
2020-02-26 23:18 ` Nick Desaulniers
2020-02-26 23:23 ` Joe Perches
2020-02-27 4:44 ` Nathan Chancellor
2020-02-25 6:33 ` Sedat Dilek
2020-02-25 21:02 ` [PATCH v2] " Nick Desaulniers
2020-02-26 11:30 ` Masahiro Yamada
2020-02-26 12:29 ` Sedat Dilek
2020-02-26 12:38 ` Masahiro Yamada
2020-02-26 13:02 ` Sedat Dilek
2020-02-26 15:45 ` Randy Dunlap
2020-02-26 23:23 ` [PATCH v3] " Nick Desaulniers
2020-02-27 3:58 ` Masahiro Yamada
2020-02-27 16:11 ` Masahiro Yamada
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=202002242019.A9F519A33A@keescook \
--to=keescook@chromium.org \
--cc=clang-built-linux@googlegroups.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
/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