From: Dan Kegel <dank@kegel.com>
To: Visda.Vokhshoori@microchip.com
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: The linker map file and LTO
Date: Fri, 16 Oct 2020 07:12:29 -0700 [thread overview]
Message-ID: <CAPF-yOagHX6gUkuF-9fNvOZ3=yjnsR8JtLii7X+KiUn3wEz5mA@mail.gmail.com> (raw)
In-Reply-To: <3AF28CAB-EFAE-4637-B53E-4D85FCC458DC@microchip.com>
Is this related to the -g trouble with lto?
https://stackoverflow.com/questions/40743372/gcc-lto-appears-to-strip-debugging-symbols
Visda Vokhshoori via Gcc-help <gcc-help@gcc.gnu.org> schrieb am Do., 15.
Okt. 2020, 19:04:
> Hello,
>
> I have an application that is being compiled and linked with LTO option
> and –param lto-partition=1. The .text section of the map file only
> provides size. It doesn’t provide the content of the .text section, ie
> function names.
>
> Is this by design? Is there a way to force the content to be printed to
> the .text section in the map file?
>
> Thanks,
> Visda
>
next prev parent reply other threads:[~2020-10-16 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 2:03 Visda.Vokhshoori
2020-10-16 14:12 ` Dan Kegel [this message]
2020-10-16 14:18 ` Visda.Vokhshoori
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='CAPF-yOagHX6gUkuF-9fNvOZ3=yjnsR8JtLii7X+KiUn3wEz5mA@mail.gmail.com' \
--to=dank@kegel.com \
--cc=Visda.Vokhshoori@microchip.com \
--cc=gcc-help@gcc.gnu.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).