On 26 February 2018 at 16:58, Zbigniew Jędrzejewski-Szmek
wrote:
[..]
>
> > Can you repeat above and show output of the command "size /var/tmp/inst-*"?
>
> After stripping:
> 24808 /var/tmp/inst-O2
> 21060 /var/tmp/inst-O2-lto
> 22240 /var/tmp/inst-O3
> 21812 /v
On Mon, Feb 26, 2018 at 04:47:31PM +, Tomasz Kłoczko wrote:
> On 26 February 2018 at 07:11, Zbigniew Jędrzejewski-Szmek > wrote:
>
> > On Mon, Feb 26, 2018 at 05:24:28AM +0100, Kevin Kofler wrote:
> > > Zbigniew Jędrzejewski-Szmek wrote:
> > > > But size is easy:
> > > > $ du -s /var/tmp/inst
On 26 February 2018 at 07:11, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Feb 26, 2018 at 05:24:28AM +0100, Kevin Kofler wrote:
> > Zbigniew Jędrzejewski-Szmek wrote:
> > > But size is easy:
> > > $ du -s /var/tmp/inst-O*
> > > 74428 /var/tmp/inst-O3
> > > 56136 /var/tmp/inst-O3-lto
> > > 61992
On Sun, 2018-02-25 at 13:19 +0100, Florian Weimer wrote:
> On 02/25/2018 12:45 PM, Zbigniew Jędrzejewski-Szmek wrote:
> > > What's our current take on using LTO for Fedora package builds?
> > systemd would like to use it.
>
> Why? What are the benefits?
I'v
On 02/26/2018 07:11 UTC, Zbigniew Jędrzejewski-Szmek wrote:
(Note, it's all unstripped.)
It would be interesting to apply /usr/bin/size, then sum the columns.
Similarly for the debuginfo, particularly the line numbers section.
Optimizations which re-schedule, move, or merge instructions
can ge
On Mon, Feb 26, 2018 at 05:24:28AM +0100, Kevin Kofler wrote:
> Zbigniew Jędrzejewski-Szmek wrote:
> > But size is easy:
> > $ du -s /var/tmp/inst-O*
> > 74428 /var/tmp/inst-O3
> > 56136 /var/tmp/inst-O3-lto
> > 61992 /var/tmp/inst-Os
> > 43572 /var/tmp/inst-Os-lto
>
> The current default is -O2,
Zbigniew Jędrzejewski-Szmek wrote:
> But size is easy:
> $ du -s /var/tmp/inst-O*
> 74428 /var/tmp/inst-O3
> 56136 /var/tmp/inst-O3-lto
> 61992 /var/tmp/inst-Os
> 43572 /var/tmp/inst-Os-lto
The current default is -O2, not -O3, though.
Kevin Kofler
_
On Sun, Feb 25, 2018 at 03:35:39PM +0100, Kevin Kofler wrote:
> Tomasz Kłoczko wrote:
> > BTW size. Did you try to compile systemd with optimisation for size (-Os)?
> >
> > There are many Linux packages which should be optimised for size
> > because they provide binaries which are speed critical l
te:
> > > > > What's our current take on using LTO for Fedora package builds?
> > > > systemd would like to use it.
> > >
> > > Why? What are the benefits?
> >
> > There's a small change in size. When I tested recently it was ~7%,
Hi,
On Sun, 2018-02-25 at 12:30 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Sun, Feb 25, 2018 at 01:19:24PM +0100, Florian Weimer wrote:
> > On 02/25/2018 12:45 PM, Zbigniew Jędrzejewski-Szmek wrote:
> > > > What's our current take on using LTO for Fedora package b
rdening quality control tooling because the annobin GCC plug-in may
> not be active when the final LTO link with new code generation happens (bug
> 1548821).
>
> What's our current take on using LTO for Fedora package builds?
>
Mir uses LTO on all platforms except ppc64 (the b
Tomasz Kłoczko wrote:
> BTW size. Did you try to compile systemd with optimisation for size (-Os)?
>
> There are many Linux packages which should be optimised for size
> because they provide binaries which are speed critical like boot
> loaders and boot tools (grub, lilo, gubby) some diagnostics a
On 25 February 2018 at 12:30, Zbigniew Jędrzejewski-Szmek
wrote:
> On Sun, Feb 25, 2018 at 01:19:24PM +0100, Florian Weimer wrote:
>> On 02/25/2018 12:45 PM, Zbigniew Jędrzejewski-Szmek wrote:
>> >>What's our current take on using LTO for Fedora package builds?
>>
On Sun, Feb 25, 2018 at 01:19:24PM +0100, Florian Weimer wrote:
> On 02/25/2018 12:45 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >>What's our current take on using LTO for Fedora package builds?
>
> >systemd would like to use it.
>
> Why? What are the benefits?
On 02/25/2018 12:45 PM, Zbigniew Jędrzejewski-Szmek wrote:
What's our current take on using LTO for Fedora package builds?
systemd would like to use it.
Why? What are the benefits?
Thanks,
Florian
___
devel mailing list --
gt; some of the hardening quality control tooling because the annobin
> GCC plug-in may not be active when the final LTO link with new code
> generation happens (bug 1548821).
>
> What's our current take on using LTO for Fedora package builds?
systemd would like to use it. Currently linkin
active when the final LTO link with new code generation
happens (bug 1548821).
What's our current take on using LTO for Fedora package builds?
Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
17 matches
Mail list logo
