[Bug debuginfod/25448] Extend debuginfod metrics

2020-03-27 Thread marxin.liska at gmail dot com via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=25448

--- Comment #2 from Martin Liška  ---
I like the suggested patch!

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

[Bug general/24498] 0.176: isn't LTO ready

2020-04-14 Thread marxin.liska at gmail dot com via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=24498

--- Comment #9 from Martin Liška  ---
(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.

> 
> But I haven't tried to build all of elfutils with LTO enabled yet.
> How do you configure elfutils to enable LTO?

I would add a configure option --enable-lto that will append -flto to
{C,LD}FLAGS.

Thanks for working on that.

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

[Bug general/24498] 0.176: isn't LTO ready

2020-04-15 Thread marxin.liska at gmail dot com via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=24498

--- Comment #11 from Martin Liška  ---
(In reply to kloczek from comment #10)
> > I would add a configure option --enable-lto that will append -flto to 
> > {C,LD}FLAGS.
> 
> Please don't do that.
> 
> LTO can be driven using only env variable.
> 
> % CFLAGS="" LDFLAGS="" ./configure

Works for me.

> 
> Please use KISS principle and do not implement something which can be
> already done other way *without* touching existing code.
> 
> PS. Changing {C,LD}FLAGS is not only part of using LTO. You need to pass NM,
> RANLIB and AR env variables.

Not necessarily. Typical Linux systems, like openSUSE, utilize auto-loading
mechanism of LTO plugins:

$ strace -f -s512 nm foo.o 2>&1 | grep plugin
...
openat(AT_FDCWD, "/usr/bin/../bin/../lib/bfd-plugins/liblto_plugin.so.0.0.0",
O_RDONLY|O_CLOEXEC) = 5

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