From: Jeff Law <jeffreyalaw@gmail.com>
To: Rasmus Villemoes <rv@rasmusvillemoes.dk>, gcc-patches@gcc.gnu.org
Cc: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Subject: Re: [PATCH] apply debug-remap to file names in .su files
Date: Sat, 29 Apr 2023 23:10:50 -0600 [thread overview]
Message-ID: <29821cec-b45b-749f-818b-33a7c8ffc267@gmail.com> (raw)
In-Reply-To: <20230213192700.2013187-1-rasmus.villemoes@prevas.dk>
On 2/13/23 12:27, Rasmus Villemoes wrote:
> The .su files generated with -fstack-usage are arguably debug info. In
> order to make builds more reproducible, apply the same remapping logic
> to the recorded file names as for when producing the debug info
> embedded in the object files.
>
> To this end, teach print_decl_identifier() a new
> PRINT_DECL_REMAP_DEBUG flag and use that from output_stack_usage_1().
>
> gcc/ChangeLog:
>
> * print-tree.h (PRINT_DECL_REMAP_DEBUG): New flag.
> * print-tree.cc (print_decl_identifier): Implement it.
> * toplev.cc (output_stack_usage_1): Use it.
OK for the trunk.
jeff
prev parent reply other threads:[~2023-04-30 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 19:27 Rasmus Villemoes
2023-03-03 12:49 ` Rasmus Villemoes
2023-04-30 5:10 ` Jeff Law [this message]
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=29821cec-b45b-749f-818b-33a7c8ffc267@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rasmus.villemoes@prevas.dk \
--cc=rv@rasmusvillemoes.dk \
/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).