public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/25549] Systemtap unable to find many probe points available in code compiled with LTO enable
Date: Fri, 08 May 2020 14:02:13 +0000	[thread overview]
Message-ID: <bug-25549-6586-N18eG0TYDU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25549-6586@http.sourceware.org/bugzilla/>

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

--- Comment #11 from William Cohen <wcohen at redhat dot com> ---
I have put the f30 ld binary and associated debuginfo file in 

http://people.redhat.com/wcohen/pr25549/ld/

The ld built with lto and its debuginfo file is in:

http://people.redhat.com/wcohen/pr25549/ld.lto/

With LTO would expect that some functions and statements get eliminated if they
are unused.  However, 90% reduction of the statement probe points seems
unreasonably good considering that the binary is only 50% smaller and the text
sections are not that much smaller:

[wcohen@cervelo BUILDROOT]$ eu-readelf -S
binutils-2.31.1-29.fc30_gcc_o2__g_.x86_64/usr/bin/ld |grep text
[15] .text                PROGBITS     0000000000037410 00037410 0018fd45  0 AX
    0   0 16
[wcohen@cervelo BUILDROOT]$ eu-readelf -S
binutils-2.31.1-29.fc30_gcc_o2_lto_g_.x86_64/usr/bin/ld |grep text
[13] .text                PROGBITS     00000000000329a0 000329a0 00156535  0 AX
    0   0 16

As far as probe points there are probe points missing for entire files (ignore
the '-./' at the beginning the - is from the diff and the "./" was substitution
to make the remove to original full path to make comparing things from build
directories more comparable):

-./adler32.c
-./aligned_buffer.h
-./allocator.h
-./alloc_traits.h
-./argv.c
-./basic_ios.h
-./binary.h
-./char_traits.h
-./compress.c
-./copy-relocs.h
-./cp-demangle.c
-./cp-demint.c
-./cplus-dem.c
-./crc32.c
-./d-demangle.c
-./debug.h
-./deflate.c
-./defstd.cc
-./../elfcpp/elfcpp_file.h
-./../elfcpp/elfcpp.h
-./../elfcpp/elfcpp_swap.h
-./errors.h
-./fcntl2.h
-./filename_cmp.c
-./fileread.h
-./freebsd.h
-./fstream
-./functional_hash.h
-./gc.cc
-./hex.c
-./inffast.c
-./inflate.c
-./inftrees.c
-./ios_base.h
-./istream
-./lbasename.c
-./list.tcc
-./locale_facets.h
-./lrealpath.c
-./md5.c
-./move.h
-./new_allocator.h
-./predefined_ops.h
-./reloc.h
-./reloc-types.h
-./rust-demangle.c
-./script-sections.h
-./sha1.c
-./stat.h
-./stdio2.h
-./stdlib.h
-./stl_construct.h
-./stl_function.h
-./stl_iterator_base_funcs.h
-./stl_set.h
-./stl_tempbuf.h
-./stl_uninitialized.h
-./streambuf
-./string_fortified.h
-./string.h
-./stringpool.h
-./tls.h
-./trees.c
-./unistd.h
-./unlink-if-ordinary.c
-./utility
-./xexit.c
-./xmalloc.c
-./xmemdup.c
-./xstrdup.c
-./zutil.c

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2020-05-08 14:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 15:40 [Bug translator/25549] New: " wcohen at redhat dot com
2020-05-01 18:31 ` [Bug translator/25549] " wcohen at redhat dot com
2020-05-04 20:18 ` wcohen at redhat dot com
2020-05-05 15:41 ` wcohen at redhat dot com
2020-05-05 20:49 ` woodard at redhat dot com
2020-05-07  2:06 ` fche at redhat dot com
2020-05-07  3:26 ` mark at klomp dot org
2020-05-07 10:27 ` fche at redhat dot com
2020-05-07 10:28 ` fche at redhat dot com
2020-05-07 11:36 ` mark at klomp dot org
2020-05-07 13:58 ` wcohen at redhat dot com
2020-05-07 17:55 ` wcohen at redhat dot com
2020-05-08 10:15 ` mark at klomp dot org
2020-05-08 14:02 ` wcohen at redhat dot com [this message]
2020-05-08 17:25 ` mark at klomp dot org
2020-05-08 20:07 ` wcohen at redhat dot com
2020-07-10  3:00 ` fche at redhat dot com

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-25549-6586-N18eG0TYDU@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@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).