All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@cardoe.com>
To: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Wei Liu" <wei.liu2@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Cc: Julien Grall <julien.grall@arm.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Jan Beulich <JBeulich@suse.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] xen/common: Drop function calls for Xen compile/version information
Date: Wed, 18 Jan 2017 14:01:46 -0500	[thread overview]
Message-ID: <277f9e5c-bb87-7980-77c6-1e4e117522fb@cardoe.com> (raw)
In-Reply-To: <ae7d5e3e-ffc7-8125-9e7c-5c084b190f8d@citrix.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 759 bytes --]

On 1/18/17 12:04 PM, Andrew Cooper wrote:

> Last time I tried LTO:
> 
> * The GCC build did work, but the net binary was bigger rather than
> smaller, and it successfully boot
> * The Clang build worked, made a much smaller binary, but due to a clang
> bug, "optimised" code into using SSE, and blew up spectacularly when
> booting.
> 
> From experiments with XTF, Clang 3.9 LTO is far more comprehensive, and
> is basically capable of optimising entire XTF tests into one single test
> function, and properly respects the "no FPU ever" options used during boot.
> 
> ~Andrew

FWIW, some of the clang issues I reported against LTO and FPU bits are
marked as fixed in 3.9 and 4.0. Not sure if things got backported.

-- 
Doug Goldstein


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2017-01-18 19:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 13:04 [PATCH] xen/common: Drop function calls for Xen compile/version information Andrew Cooper
2017-01-16 13:18 ` Jan Beulich
2017-01-16 13:26   ` Andrew Cooper
2017-01-16 18:23 ` Stefano Stabellini
2017-01-16 19:44 ` Doug Goldstein
2017-01-17 18:05 ` Konrad Rzeszutek Wilk
2017-01-17 18:16   ` Andrew Cooper
2017-01-17 18:42     ` Konrad Rzeszutek Wilk
2017-01-17 19:00       ` Konrad Rzeszutek Wilk
2017-01-17 20:39         ` Andrew Cooper
2017-01-17 20:46           ` Konrad Rzeszutek Wilk
2017-01-18 10:13             ` Roger Pau Monné
2017-01-18 16:10               ` Konrad Rzeszutek Wilk
2017-01-18 16:21                 ` Roger Pau Monné
2017-01-18 16:30                   ` Wei Liu
2017-01-18 17:04                     ` Andrew Cooper
2017-01-18 19:01                       ` Doug Goldstein [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=277f9e5c-bb87-7980-77c6-1e4e117522fb@cardoe.com \
    --to=cardoe@cardoe.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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.