From: NightStrike <nightstrike@gmail.com>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: khareshivansh03@gmail.com, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC -ftime-trace
Date: Mon, 13 Feb 2023 11:44:34 -0500 [thread overview]
Message-ID: <CAF1jjLtYOTASyUs-qUg2iNcOca7j=2wPEwFVeHnM6FTT7di+cQ@mail.gmail.com> (raw)
In-Reply-To: <06594032-1183-8c05-2e03-0c8c37f3106c@starynkevitch.net>
[-- Attachment #1: Type: text/plain, Size: 406 bytes --]
On Sat, Feb 11, 2023, 14:37 Basile Starynkevitch <basile@starynkevitch.net>
wrote:
> Modifying the pass manager
> https://gcc.gnu.org/onlinedocs/gccint/Pass-manager.html#Pass-manager to
> use clock_gettime system call. See
> https://man7.org/linux/man-pages/man2/clock_gettime.2.html
Since we can now use c++11, std::chrono::high_resolution_clock::now() would
call that without being platform specific.
prev parent reply other threads:[~2023-02-13 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 19:36 Basile Starynkevitch
2023-02-13 8:14 ` Richard Biener
2023-02-13 16:44 ` NightStrike [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='CAF1jjLtYOTASyUs-qUg2iNcOca7j=2wPEwFVeHnM6FTT7di+cQ@mail.gmail.com' \
--to=nightstrike@gmail.com \
--cc=basile@starynkevitch.net \
--cc=gcc@gcc.gnu.org \
--cc=khareshivansh03@gmail.com \
/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).