public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
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, 15 Apr 2020 12:50:15 +0000	[thread overview]
Message-ID: <bug-24498-10460-rEh75PkAek@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24498-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24498

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #12 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Martin Liška from comment #9)
> (In reply to Mark Wielaard from comment #8)
> > I proposed a patch to use the new gcc 10 symver attribute to define symbol
> > versioning:
> > 
> > https://sourceware.org/pipermail/elfutils-devel/2020q2/002606.html
> > 
> > This should help with using LTO since it makes the function symbols and
> > versions visible to the compiler (before they were "hidden" inside asm
> > statements).
> 
> There's an ongoing effort that will extend .symver GAS syntax:
> https://sourceware.org/bugzilla/show_bug.cgi?id=25295
> 
> Later then, the GCC will utilize the new syntax.

Interesting, thanks for the reference. I also added a comment to the GCC bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48200#c43 because the current
syntax (not supporting triple @ variant) makes things a bit cumbersome.

This is partly because the interaction between linker version script and
assembler .symver isn't really documented fully. The assembler .symver should
override what is in the linker version script, but it doesn't fully. In
particular, as shown by this hack, the linker might still add a (default)
version to a symbol, even if the assembler already added a version.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-04-15 12:50 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 [this message]
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
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-rEh75PkAek@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).