ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Unconference session on getting LTO into the kernel?
Date: Sat, 16 Aug 2014 17:20:52 -0700	[thread overview]
Message-ID: <20140817002051.GA25397@thin> (raw)

There's been a lot of discussion about link-time optimization of the
Linux kernel.  However, as of yet the patches have not yet gone in.
I've seen objections on the grounds that it increases build time and
memory usage, but those objections don't seem like reasons to omit the
patches, just reasons to keep LTO optional and disabled by default (and
potentially to prevent "allyesconfig" from enabling it).

Anyone interested in a session to hammer out the last details to get the
patches merged?

(If this mail ends up prompting discussion that settles this via email,
that'd be a fine result too.)

- Josh Triplett

             reply	other threads:[~2014-08-17  0:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-17  0:20 Josh Triplett [this message]
2014-08-17 22:04 ` H. Peter Anvin
2014-08-18  3:27   ` Josh Triplett

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=20140817002051.GA25397@thin \
    --to=josh@joshtriplett.org \
    --cc=ksummit-discuss@lists.linuxfoundation.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