From: "Khem Raj" <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Martin Jansa <martin.jansa@gmail.com>, Khem Raj <raj.khem@gmail.com>
Subject: [PATCH v4 3/4] lto.inc: Add -ffat-lto-objects and -fuse-linker-plugin
Date: Sat, 7 Nov 2020 14:23:56 -0800 [thread overview]
Message-ID: <20201107222357.43102-3-raj.khem@gmail.com> (raw)
In-Reply-To: <20201107222357.43102-1-raj.khem@gmail.com>
This helps to improve LTO and ensure the libs can be linked with non-LTO
objects too
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
meta/conf/distro/include/lto.inc | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/meta/conf/distro/include/lto.inc b/meta/conf/distro/include/lto.inc
index fe0f6c9f44..d7fea26c64 100644
--- a/meta/conf/distro/include/lto.inc
+++ b/meta/conf/distro/include/lto.inc
@@ -20,7 +20,16 @@ LTO_pn-libbsd = ""
# Override it for additional or different options if needed e.g.
# with clang thin-lto might be better for compile speed
-LTO ?= "-flto"
+#
+# ffat-lto-objects
+# object files that contain both the intermediate
+# language and the object code. This makes them
+# usable for both LTO linking and normal linking
+#
+# -fuse-linker-plugin
+# ensures that libraries participate in LTO by supplying intermediate
+# code from .a files to linker
+LTO ?= "-flto -ffat-lto-objects -fuse-linker-plugin "
SELECTED_OPTIMIZATION_append = "${@bb.utils.contains('DISTRO_FEATURES', 'lto', ' ${LTO}', '', d)}"
TARGET_LDFLAGS_append_class-target = "${@bb.utils.contains('DISTRO_FEATURES', 'lto', ' ${LTO}', '', d)}"
--
2.29.2
next prev parent reply other threads:[~2020-11-07 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 22:23 [PATCH v4 1/4] lto: Add global LTO distro policy file Khem Raj
2020-11-07 22:23 ` [PATCH v4 2/4] python3: Enable lto if its in DISTRO_FEATURES Khem Raj
2020-11-07 22:23 ` Khem Raj [this message]
2020-11-07 22:23 ` [PATCH v4 4/4] lto: Introduce LTOEXTRA variable Khem Raj
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=20201107222357.43102-3-raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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