From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/24498] 0.176: isn't LTO ready
Date: Wed, 06 May 2020 16:10:25 +0000 [thread overview]
Message-ID: <bug-24498-10460-kVA5HEJCZz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24498-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24498
--- Comment #22 from Mark Wielaard <mark at klomp dot org> ---
kloczek, re comment #20 and comment #21, is that with the latest git master
sources? It looks like it is missing several code and testsuite fixes. In
particular are you sure you have the following patches:
commit e2fc0b737c1d55becda1f13dceec315a5589820a
Author: Mark Wielaard <mark@klomp.org>
Date: Thu Apr 16 18:48:58 2020 +0200
elflint: Allow SHF_EXCLUDE as generic section flag when --gnu is given.
commit d6185d33fb2a65b4c3cbc73c5529937debdd2568
Author: Mark Wielaard <mark@klomp.org>
Date: Fri Apr 17 11:31:40 2020 +0200
libdw, readelf: Handle GCC LTO .gnu.debuglto_ prefix.
commit 51cfbaabefd6d5ebdd7513b876daf78d07470f8c
Author: Mark Wielaard <mark@klomp.org>
Date: Fri Apr 17 12:21:46 2020 +0200
tests: Build test-nlist with minimal CFLAGS to guarantee symbol order.
commit 554352ded723042572a91200d05fdb075b1a1ea3
Author: Mark Wielaard <mark@klomp.org>
Date: Fri Apr 17 12:31:15 2020 +0200
tests: Run run-varlocs-self.sh for object files with --exprlocs.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-06 16:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 19:49 [Bug general/24498] New: " kloczko.tomasz at gmail dot com
2019-04-28 20:25 ` [Bug general/24498] " mark at klomp dot org
2019-04-28 20:25 ` mark at klomp dot org
2019-04-28 20:37 ` kloczko.tomasz at gmail dot com
2019-04-28 20:43 ` mark at klomp dot org
2019-09-15 13:57 ` kloczko.tomasz at gmail dot com
2019-10-04 7:39 ` mark at klomp dot org
2020-03-30 22:11 ` kloczko.tomasz at gmail dot com
2020-04-02 11:14 ` mark at klomp dot org
2020-04-10 19:47 ` mark at klomp dot org
2020-04-15 5:12 ` marxin.liska at gmail dot com
2020-04-15 7:03 ` kloczko.tomasz at gmail dot com
2020-04-15 7:07 ` marxin.liska at gmail dot com
2020-04-15 12:50 ` mark at klomp dot org
2020-04-15 13:56 ` mark at klomp dot org
2020-04-15 15:53 ` kloczko.tomasz at gmail dot com
2020-04-16 16:00 ` mark at klomp dot org
2020-04-16 17:04 ` mark at klomp dot org
2020-04-17 9:42 ` mark at klomp dot org
2020-04-17 10:36 ` mark at klomp dot org
2020-05-06 14:39 ` mark at klomp dot org
2020-05-06 15:23 ` kloczko.tomasz at gmail dot com
2020-05-06 15:25 ` kloczko.tomasz at gmail dot com
2020-05-06 16:10 ` mark at klomp dot org [this message]
2020-05-06 16:10 ` [Bug general/24498] 0.179: " mark at klomp dot org
2020-05-06 17:28 ` kloczko.tomasz at gmail dot com
2022-04-24 18:14 ` mark at klomp dot org
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=bug-24498-10460-kVA5HEJCZz@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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).