All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Arnd Bergmann <arnd@arndb.de>, x86@kernel.org
Cc: "Nicolas Pitre" <nico@linaro.org>,
	"Andi Kleen" <ak@linux.intel.com>,
	linux-kernel@vger.kernel.org, "Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [PATCH 0/3] x86 bugfixes for LTO
Date: Fri, 09 Feb 2018 22:24:33 +0000	[thread overview]
Message-ID: <151821507347.9954.4785393248908071074@mail.alporthouse.com> (raw)
In-Reply-To: <20180202145434.100626-1-arnd@arndb.de>

Quoting Arnd Bergmann (2018-02-02 14:54:28)
> Here are three bugfixes for x86 that I needed to get LTO-enabled
> kernels to build reliably. I'm not sure abouto that first one
> though.

Is there a howto on how to build LTO kernels? I tried Andi's lto-415-2
branch, but linking fails with lots of arcane PIE-vs-PIC errors. We are
wanting to investigate how we can use LTO to reduce our (i915.ko) module
size (by e.g. supporting a subset of chipsets).
-Chris

  parent reply	other threads:[~2018-02-09 22:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-02 14:54 [PATCH 0/3] x86 bugfixes for LTO Arnd Bergmann
2018-02-02 14:56 ` [PATCH 1/3] x86: dumpstack: avoid uninitlized variable Arnd Bergmann
2018-02-02 14:56   ` [PATCH 2/3] x86: fix swsusp_arch_resume prototype Arnd Bergmann
2018-02-02 22:37     ` [tip:x86/urgent] x86/power: Fix " tip-bot for Arnd Bergmann
2018-02-08 10:12     ` [PATCH 2/3] x86: fix " Rafael J. Wysocki
2018-02-02 14:56   ` [PATCH 3/3] x86: error_inject: make just_return_func globally visible Arnd Bergmann
2018-02-03 13:21     ` Masami Hiramatsu
2018-02-13 15:25     ` [tip:x86/urgent] x86/error_inject: Make just_return_func() " tip-bot for Arnd Bergmann
2018-02-02 22:36   ` [tip:x86/urgent] x86/dumpstack: Avoid uninitlized variable tip-bot for Arnd Bergmann
2018-02-05 21:21     ` Arnd Bergmann
2018-02-05 21:39       ` Josh Poimboeuf
2018-02-05 21:48         ` Arnd Bergmann
2018-02-09 22:24 ` Chris Wilson [this message]
2018-02-09 23:00   ` [PATCH 0/3] x86 bugfixes for LTO Andi Kleen

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=151821507347.9954.4785393248908071074@mail.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=ak@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@linaro.org \
    --cc=x86@kernel.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.