doc: update IDE coverage support statement for LLVM/Clang gcov format

Update profiling documentation to reflect that Nuclei Studio IDE now
supports both GCC and LLVM/Clang gcov format coverage visualization(tested).

Previously the documentation incorrectly stated LLVM/Clang format
was not supported in the IDE.

Signed-off-by: Huaqi Fang <578567190@qq.com>

Author: fanghuaqi

Components/profiling/README.md

@@ -46,13 +46,15 @@ This profiling component now supports both **GCC** and **LLVM/Clang** toolchains
 >   - For LLVM/Clang-compiled code: use `llvm-cov gcov` to parse coverage information
 >
 > **Nuclei Studio IDE Coverage Support:**
->   - The IDE currently supports GCC gcov format coverage data visualization
->   - **LLVM/Clang gcov format is NOT yet supported in Nuclei Studio IDE**
->   - For LLVM/Clang coverage analysis, you must use the command-line tool:
+>   - Nuclei Studio IDE supports both GCC and LLVM/Clang gcov format coverage data visualization
+>   - For command-line analysis, use the corresponding gcov tool for your toolchain:
 >     ```bash
+>     # For GCC toolchain
+>     riscv64-unknown-elf-gcov <your-compiled-file>.gcda
+>
+>     # For LLVM/Clang toolchain
 >     llvm-cov gcov <your-compiled-file>.gcda
 >     ```
->   - GCC coverage data can still be viewed directly in the IDE's Coverage view
 
 In this directory, we provide utils source code to do profiling and coverage using gcov and gprof
 technology.

doc/source/changelog.rst

@@ -89,6 +89,7 @@ This is release version of ``0.9.0`` of Nuclei SDK, which is still under develop
   - Update :ref:`design_app_demo_profiling` to demonstrate the usage of ``APPDIRS`` variable for application-specific compilation flags.
   - Update :ref:`design_app_demo_profiling` documentation to include command-line usage instructions for profiling and code coverage, GCC version compatibility notes, and recommended lcov-based workflow.
   - Update :ref:`design_app_demo_profiling` Makefile to add local documentation reference comments pointing to ``doc/source/design/app.rst#demo_profiling`` and ``Components/profiling/README.md``
+  - Fix documentation to correctly state that Nuclei Studio IDE supports both GCC and LLVM/Clang gcov format coverage visualization
   - Remove ``nuclei_cache`` npk configuration from ``demo_cache``, ``demo_cidu``, ``demo_ecc``, ``demo_pma``, ``demo_smpcc``, and ``smphello`` applications ``npk.yml`` since it is now deprecated
   - Add ``get_cpu_feature`` in ``cpuinfo`` to list CPU features for the future hardware ci testing.
 
@@ -171,7 +172,7 @@ This is release version of ``0.9.0`` of Nuclei SDK, which is still under develop
   - Update the expected output of ``cpuinfo`` in ``app.rst``
   - Update documentation about n100 with eclic is now supported in Nuclei SDK
   - Add ``demo_smpcc`` and ``demo_ecc`` application documentation in ``app.rst``
-  - Update :ref:`design_app_demo_profiling` documentation in ``app.rst`` with detailed GCC and LLVM/Clang toolchain-specific instructions for profiling and coverage analysis, IDE limitations for LLVM/Clang gcov format, and command-line workflows using ``lcov``
+  - Update :ref:`design_app_demo_profiling` documentation in ``app.rst`` with detailed GCC and LLVM/Clang toolchain-specific instructions for profiling and coverage analysis, and command-line workflows using ``lcov``
   - Add warning note in :ref:`develop_buildsystem_var_semihost` about heap and stack collision risk when using semihosting with ``malloc``, due to newlib semihost ``_sbrk`` implementation assumes unlimited heap size
 
 * Tools

doc/source/design/app.rst

@@ -1993,9 +1993,10 @@ console when main part code is executed.
       a slight increase in the program's memory footprint compared to its uninstrumented counterpart.
     * Please check ``README.md`` about gcov and gprof support in https://github.com/Nuclei-Software/nuclei-sdk/tree/master/Components/profiling
     * **Toolchain Compatibility**: Both GCC and LLVM/Clang toolchains support ``-pg`` and ``-coverage`` options,
-      but they generate **incompatible gcov data formats**. Nuclei Studio IDE currently **only supports
-      GCC gcov format coverage visualization**. For detailed toolchain-specific analysis instructions,
-      see the IDE configuration steps below and :ref:`demo_profiling_cmdline_usage`.
+      but they generate **incompatible gcov data formats**. You must use the corresponding gcov tool for analysis.
+      Nuclei Studio IDE supports coverage visualization for both GCC and LLVM/Clang gcov formats.
+      For detailed toolchain-specific command-line analysis instructions, see the IDE configuration steps below
+      and :ref:`demo_profiling_cmdline_usage`.
 
 Import or download Nuclei SDK 0.6.0 or later release NPK in Nuclei Studio, and then create a
 project called ``demo_profiling`` based on ``app-nsdk_demo_profiling`` using
@@ -2017,10 +2018,10 @@ it is the core algorithm of this example, then you just need to do the following
 
   .. note::
 
-     Nuclei Studio IDE currently only supports GCC gcov format coverage visualization.
-     If you use LLVM/Clang toolchain (``TOOLCHAIN=nuclei_llvm``), you must analyze coverage data
-     using command-line tools (``llvm-cov gcov``) instead of the IDE's Coverage view.
-     For IDE coverage visualization, use GCC toolchain (``TOOLCHAIN=nuclei_gnu``).
+     Both GCC and LLVM/Clang toolchains are supported for coverage analysis.
+     Nuclei Studio IDE supports coverage visualization for both GCC and LLVM/Clang gcov formats.
+     For command-line analysis, use the corresponding gcov tool:
+     ``riscv64-unknown-elf-gcov`` for GCC or ``llvm-cov gcov`` for LLVM/Clang.
 - Open ``main.c``, and find ``TODO`` item, and comment ``gprof_collect(2);`` or ``gcov_collect(2);`` based on
   gprof or gcov you want to collect.
 - If you want to collect gprof data, you also need to modify ``nuclei_sdk/Components/profiling/gprof_stub.c``,
@@ -2178,8 +2179,10 @@ To use the profiling and code coverage features from the command line:
 
       - To use the lcov approach, you need to install lcov from: https://github.com/linux-test-project/lcov
 
-      - **Format Incompatibility**: GCC and LLVM/Clang generate incompatible ``.gcda`` files.
-        Always use the corresponding toolchain's gcov tool for analysis.
+      - **Toolchain Correspondence**: GCC and LLVM/Clang generate incompatible ``.gcda`` files.
+        Always use the corresponding toolchain's gcov tool for command-line analysis:
+        ``riscv64-unknown-elf-gcov`` for GCC and ``llvm-cov gcov`` for LLVM/Clang.
+        Nuclei Studio IDE supports coverage visualization for both formats.
 
 
 .. _design_app_demo_pmp:

doc/source/develop/buildsystem.rst

@@ -1211,9 +1211,9 @@ You can easily find the available middleware components in the **<NUCLEI_SDK_ROO
 
 Currently we provide the following middlewares:
 
-* **profiling**: This middleware is not expected to use in Makefile based build system, you need to use it in
-  Nuclei Studio, it is used to provide code coverage via gcov and profiling via gprof, for details, please refer
-  to the ``README.md`` in this folder.
+* **profiling**: This middleware can be used both in Nuclei Studio IDE and command-line build system.
+  It provides code coverage via gcov and profiling via gprof. For details, please refer to the
+  ``README.md`` in this folder and :ref:`design_app_demo_profiling`.
 
 .. _develop_buildsystem_var_nmsis_lib: