[clang] [analyzer][docs] Mention perfetto for visualizing trace JSONs (PR #145500)

[Balázs Benics via cfe-commits]

https://github.com/balazs-benics-sonarsource created https://github.com/llvm/llvm-project/pull/145500

None

>From 274a38f83b2c5c81968de865403cf114fc9550c0 Mon Sep 17 00:00:00 2001
From: Balazs Benics <balazs.benics at sonarsource.com>
Date: Tue, 24 Jun 2025 13:42:42 +0200
Subject: [PATCH] [analyzer][docs] Mention perfetto for visualizing trace JSONs

---
 clang/docs/analyzer/developer-docs/PerformanceInvestigation.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/clang/docs/analyzer/developer-docs/PerformanceInvestigation.rst b/clang/docs/analyzer/developer-docs/PerformanceInvestigation.rst
index ca3a56828209b..5d662cfb65be2 100644
--- a/clang/docs/analyzer/developer-docs/PerformanceInvestigation.rst
+++ b/clang/docs/analyzer/developer-docs/PerformanceInvestigation.rst
@@ -10,7 +10,7 @@ Performance analysis using ``-ftime-trace``
 
 You can add the ``-ftime-trace=file.json`` option to break down the analysis time into individual entry points and steps within each entry point.
 You can explore the generated JSON file in a Chromium browser using the ``chrome://tracing`` URL,
-or using `speedscope <https://speedscope.app>`_.
+or using `perfetto <https://ui.perfetto.dev>`_ or `speedscope <https://speedscope.app>`_.
 Once you narrow down to specific analysis steps you are interested in, you can more effectively employ heavier profilers,
 such as `Perf <https://perfwiki.github.io/main/>`_ and `Callgrind <https://valgrind.org/docs/manual/cl-manual.html>`_.