From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: asm/unified.h: guard the IT macros against redefinition when using LTO
Date: Mon, 27 Jul 2015 12:21:19 +0100 [thread overview]
Message-ID: <20150727112119.GG7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150727111613.GL10670@e103592.cambridge.arm.com>
On Mon, Jul 27, 2015 at 12:16:15PM +0100, Dave Martin wrote:
> Another scary thing with LTO is asms that use directives like
> .arch_extension, .fpu etc. that will stay active for the rest of the LTO
> unit of nothing is done about it.
That would be a problem, especially for things like the neon support,
as we specifically want stuff like that to be built separately. The
same probably applies where we want to build with different architecture
options.
So, maybe the answer is to build most of the kernel with LTO enabled, but
those bits which require explicit -march= or -mfpu= options need to remain
separate non-LTO-able objects.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2015-07-27 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 21:42 [PATCH] ARM: asm/unified.h: guard the IT macros against redefinition when using LTO Nicolas Pitre
2015-07-27 11:16 ` Dave Martin
2015-07-27 11:21 ` Russell King - ARM Linux [this message]
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=20150727112119.GG7557@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.