public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/109361] RFE: SARIF output could contain timing/profile information
Date: Fri, 31 Mar 2023 20:45:25 +0000 [thread overview]
Message-ID: <bug-109361-4-vAD0AwG4Zm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109361-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109361
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-03-31
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #0)
> My integration tests for -fanalyzer don't yet track how long the analyzer
> takes on the real-world cases.
Filed as
https://github.com/davidmalcolm/gcc-analyzer-integration-tests/issues/5
> It would be nice for the .sarif files generated by
> -fdiagnostics-format=sarif-file to contain profiling or timing information.
I'm testing an implementation of this, which puts the -ftime-report data into a
property bag of the "invocation" object.
next prev parent reply other threads:[~2023-03-31 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 13:09 [Bug analyzer/109361] New: " dmalcolm at gcc dot gnu.org
2023-03-31 13:16 ` [Bug analyzer/109361] " dmalcolm at gcc dot gnu.org
2023-03-31 20:45 ` dmalcolm at gcc dot gnu.org [this message]
2023-04-03 15:31 ` dmalcolm at gcc dot gnu.org
2023-07-28 20:37 ` dmalcolm at gcc dot gnu.org
2023-07-31 15:28 ` cvs-commit at gcc dot gnu.org
2023-07-31 15:30 ` dmalcolm at gcc dot gnu.org
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-109361-4-vAD0AwG4Zm@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).