public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Jan Hubicka <hubicka@kam.mff.cuni.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Improve -fprofile-report
Date: Thu, 9 Dec 2021 11:01:10 +0100	[thread overview]
Message-ID: <868f53a9-7b52-fb67-2684-5c9d4879746b@suse.cz> (raw)
In-Reply-To: <20211203092851.GC97801@kam.mff.cuni.cz>

On 12/3/21 10:28, Jan Hubicka wrote:
> |Do you know how to get that name? With the numbers it is not too hard to find the dump, but I do not mind having it either way.|

Hello.

Let's keep the names as they are. I've just added the tracking to all LNT instances.

Cheers,
Martin

  reply	other threads:[~2021-12-09 10:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-27 15:56 Jan Hubicka
2021-11-29  9:11 ` Martin Liška
2021-12-03  9:28   ` Jan Hubicka
2021-12-09 10:01     ` Martin Liška [this message]
2021-12-03  8:37 ` Bernhard Reutner-Fischer

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=868f53a9-7b52-fb67-2684-5c9d4879746b@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@kam.mff.cuni.cz \
    /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).