From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-17.4 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5EED3C433E2 for ; Tue, 8 Sep 2020 17:31:04 +0000 (UTC) Received: from mother.openwall.net (mother.openwall.net [195.42.179.200]) by mail.kernel.org (Postfix) with SMTP id 6EC0B2076C for ; Tue, 8 Sep 2020 17:31:03 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="AzIN32ul" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6EC0B2076C Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernel-hardening-return-19822-kernel-hardening=archiver.kernel.org@lists.openwall.com Received: (qmail 23769 invoked by uid 550); 8 Sep 2020 17:30:56 -0000 Mailing-List: contact kernel-hardening-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Received: (qmail 23728 invoked from network); 8 Sep 2020 17:30:55 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=/5WUqOjLHPAdLAI0MKh9zhuMyV7IC1nlysZjintZ/W0=; b=AzIN32ulFSn0Cg8a7U6pqoMQp2nPeaRLHJAx4wWGA8CJaevtEmegxP/Z/uIxm/mEpu QVOrS/Ir/CxKvGymkWaSrXUyeKbbg65sx4q09ssmoAXIt6bm8jV1LH45TsyB5/QvO6Qe pSg9MqH9AVTpVpXvwoaCFmKjx/m6VIWugbAKBCS/XL0KnFFDPP0JrCP80TKO4jQk1l8S wZd7N9m2+fYup3wy0GHLd7qSFjvCk9cqS0RN9Ik5g/nfu3wKrjCUUWhivmYZDrkqWnnn OxFDZvlGFT0EA/qrpHwZR1QXKjTo0BlWMq5+aAWrCKqvUbyJyaxDNVHcgxbFAvzgGEAS e78g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=/5WUqOjLHPAdLAI0MKh9zhuMyV7IC1nlysZjintZ/W0=; b=psnadgl5siWsqnP9B2KnEmqX8aZQUA3AbReSCh4wrrBBrARtKDzhyWPU1WC9maOmpR jG3VrDBb+vtPqtmHUtkPIvaDMKFfejX+FHJ+idKLqDGNtVXod4q5+VOHqR5YlhCMhNbH PbEClX272DzhBba3LRJ6KVogF0fCmT/A73mTdM2H18D4jWI4NmPOx7HNEUKtApC8TjCx XD/iFY+UCxuji6zIjvdWqSoxoTA2gSR6aZdEHb8LxvY6v7Hgtt3AcMse2Y88vR+gOykA wsycn2EB0f04c1UMroS+Se37BGC/Y+kxrNSJ2EZpZ83z6LVtaYKkwg0iaTu94N+cpSq9 s3Fg== X-Gm-Message-State: AOAM532TfD5m8WAGoIwIp3U//jyUdVKloLXZfo01xuaNXitXKkPjjopr ywx9iY3HJy2l+KAHTO5B5fLdPw== X-Google-Smtp-Source: ABdhPJzOBlE39s5MhGzUGu96iQjHpMxBRxzAFujrD+zw10TmjrKYdMPOuT7bZ60x6uln4rayX4+T8w== X-Received: by 2002:a63:ca0c:: with SMTP id n12mr18009749pgi.209.1599586243396; Tue, 08 Sep 2020 10:30:43 -0700 (PDT) Date: Tue, 8 Sep 2020 10:30:36 -0700 From: Sami Tolvanen To: Masahiro Yamada Cc: Will Deacon , Peter Zijlstra , Steven Rostedt , Greg Kroah-Hartman , "Paul E. McKenney" , Kees Cook , Nick Desaulniers , clang-built-linux , Kernel Hardening , linux-arch , linux-arm-kernel , Linux Kbuild mailing list , Linux Kernel Mailing List , linux-pci@vger.kernel.org, X86 ML Subject: Re: [PATCH v2 09/28] kbuild: add support for Clang LTO Message-ID: <20200908173036.GD2743468@google.com> References: <20200624203200.78870-1-samitolvanen@google.com> <20200903203053.3411268-1-samitolvanen@google.com> <20200903203053.3411268-10-samitolvanen@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Tue, Sep 08, 2020 at 12:30:14AM +0900, Masahiro Yamada wrote: > On Fri, Sep 4, 2020 at 5:31 AM Sami Tolvanen wrote: > > > > This change adds build system support for Clang's Link Time > > Optimization (LTO). With -flto, instead of ELF object files, Clang > > produces LLVM bitcode, which is compiled into native code at link > > time, allowing the final binary to be optimized globally. For more > > details, see: > > > > https://llvm.org/docs/LinkTimeOptimization.html > > > > The Kconfig option CONFIG_LTO_CLANG is implemented as a choice, > > which defaults to LTO being disabled. To use LTO, the architecture > > must select ARCH_SUPPORTS_LTO_CLANG and support: > > > > - compiling with Clang, > > - compiling inline assembly with Clang's integrated assembler, > > - and linking with LLD. > > > > While using full LTO results in the best runtime performance, the > > compilation is not scalable in time or memory. CONFIG_THINLTO > > enables ThinLTO, which allows parallel optimization and faster > > incremental builds. ThinLTO is used by default if the architecture > > also selects ARCH_SUPPORTS_THINLTO: > > > > https://clang.llvm.org/docs/ThinLTO.html > > > > To enable LTO, LLVM tools must be used to handle bitcode files. The > > easiest way is to pass the LLVM=1 option to make: > > > > $ make LLVM=1 defconfig > > $ scripts/config -e LTO_CLANG > > $ make LLVM=1 > > > > Alternatively, at least the following LLVM tools must be used: > > > > CC=clang LD=ld.lld AR=llvm-ar NM=llvm-nm > > > > To prepare for LTO support with other compilers, common parts are > > gated behind the CONFIG_LTO option, and LTO can be disabled for > > specific files by filtering out CC_FLAGS_LTO. > > > > Note that support for DYNAMIC_FTRACE and MODVERSIONS are added in > > follow-up patches. > > > > Signed-off-by: Sami Tolvanen > > --- > > Makefile | 18 +++++++- > > arch/Kconfig | 68 +++++++++++++++++++++++++++++++ > > include/asm-generic/vmlinux.lds.h | 11 +++-- > > scripts/Makefile.build | 9 +++- > > scripts/Makefile.modfinal | 9 +++- > > scripts/Makefile.modpost | 24 ++++++++++- > > scripts/link-vmlinux.sh | 32 +++++++++++---- > > 7 files changed, 154 insertions(+), 17 deletions(-) > > > > > #define TEXT_MAIN .text > > diff --git a/scripts/Makefile.build b/scripts/Makefile.build > > index 6ecf30c70ced..a5f4b5d407e6 100644 > > --- a/scripts/Makefile.build > > +++ b/scripts/Makefile.build > > @@ -111,7 +111,7 @@ endif > > # --------------------------------------------------------------------------- > > > > quiet_cmd_cc_s_c = CC $(quiet_modtag) $@ > > - cmd_cc_s_c = $(CC) $(filter-out $(DEBUG_CFLAGS), $(c_flags)) $(DISABLE_LTO) -fverbose-asm -S -o $@ $< > > + cmd_cc_s_c = $(CC) $(filter-out $(DEBUG_CFLAGS) $(CC_FLAGS_LTO), $(c_flags)) -fverbose-asm -S -o $@ $< > > > > $(obj)/%.s: $(src)/%.c FORCE > > $(call if_changed_dep,cc_s_c) > > @@ -428,8 +428,15 @@ $(obj)/lib.a: $(lib-y) FORCE > > # Do not replace $(filter %.o,^) with $(real-prereqs). When a single object > > # module is turned into a multi object module, $^ will contain header file > > # dependencies recorded in the .*.cmd file. > > +ifdef CONFIG_LTO_CLANG > > +quiet_cmd_link_multi-m = AR [M] $@ > > +cmd_link_multi-m = \ > > + rm -f $@; \ > > + $(AR) rcsTP$(KBUILD_ARFLAGS) $@ $(filter %.o,$^) > > > KBUILD_ARFLAGS no longer exists in the mainline. > (commit 13dc8c029cabf52ba95f60c56eb104d4d95d5889) Thanks, I'll drop this in the next version. > > +ifdef CONFIG_LTO_CLANG > > +# With CONFIG_LTO_CLANG, .o files might be LLVM bitcode, > > or, .o files might be even thin archives. Right, and with LTO the thin archive might also point to a mix of bitcode and ELF to further complicate things. > For example, > > $ file net/ipv6/netfilter/nf_defrag_ipv6.o > net/ipv6/netfilter/nf_defrag_ipv6.o: thin archive with 6 symbol entries > > > Now we have 3 possibilities for .o files: > > - ELF (real .o) > - LLVM bitcode (.bc) > - Thin archive (.a) > > > Let me discuss how to proceed with this... Did you have something in mind to make this cleaner? Sami