From: "Martin Liška" <mliska@suse.cz>
To: Mark Wielaard <mark@klomp.org>,
"Dmitry V. Levin" <ldv@altlinux.org>,
elfutils-devel@sourceware.org
Subject: Re: [PATCH v2] Improve building with LTO
Date: Tue, 9 Nov 2021 14:31:45 +0100 [thread overview]
Message-ID: <64e5109f-1515-c0d1-88e1-7cbc963a0e75@suse.cz> (raw)
In-Reply-To: <618afb58a9328bc9bbcc394fc17ef907ac6f188e.camel@klomp.org>
On 11/9/21 12:45, Mark Wielaard wrote:
> Hi Martin,
>
> On Tue, 2021-11-09 at 10:04 +0100, Martin Liška wrote:
>> On 11/9/21 09:58, Dmitry V. Levin wrote:
>>> Yes, but those who build elfutils with -flto are likely using
>>> -ffat-lto-objects if they build static libraries.
>>
>> Yes, I can confirm that we do that as openSUSE, we actually build
>> with:
>>
>> -flto -flto-partition=none -Wno-error=stack-usage= -ffat-lto-objects
>
> As Dmitry pointed out you should now be able to drop both -flto-
> partition=none an -Wno-error=stack-usage= (the linker will still warn,
> but not error on the large stack-usage issues (we should probably still
> fix them though).
Correct, I'm not using:
F="-O2 -g -Wall -flto=auto -ffat-lto-objects" && export CFLAGS="$F" && export CXXFLAGS="$F" && export LDFLAGS="$F" && ./configure
>
> What do the test results look like? Do they all PASS with -ffat-lto-
> objects?
>
> Could you try the proposed patch for
> https://sourceware.org/bugzilla/show_bug.cgi?id=27367
> https://sourceware.org/pipermail/elfutils-devel/2021q4/004314.html
With the suggested patch (and BFD) all is green and shiny:
============================================================================
Testsuite summary for elfutils 0.185
============================================================================
# TOTAL: 252
# PASS: 249
# SKIP: 3
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
Cheers,
Martin
>
> Thanks,
>
> Mark
>
next prev parent reply other threads:[~2021-11-09 13:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 22:57 [PATCH] " Alexander Miller
2021-02-17 20:22 ` Mark Wielaard
2021-02-18 14:27 ` Alexander Miller
2021-02-18 2:38 ` [PATCH v2] " Alexander Miller
2021-08-28 9:31 ` Dmitry V. Levin
2021-11-04 11:23 ` Dmitry V. Levin
2021-11-04 12:12 ` Mark Wielaard
2021-11-08 10:02 ` Dmitry V. Levin
2021-11-08 23:18 ` Mark Wielaard
2021-11-09 8:58 ` Dmitry V. Levin
2021-11-09 9:04 ` Martin Liška
2021-11-09 9:09 ` Dmitry V. Levin
2021-11-09 9:11 ` Martin Liška
2021-11-09 11:45 ` Mark Wielaard
2021-11-09 13:31 ` Martin Liška [this message]
2021-11-09 13:33 ` Martin Liška
2021-11-09 17:49 ` Mark Wielaard
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=64e5109f-1515-c0d1-88e1-7cbc963a0e75@suse.cz \
--to=mliska@suse.cz \
--cc=elfutils-devel@sourceware.org \
--cc=ldv@altlinux.org \
--cc=mark@klomp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).