Move reference/env_variables folder under docs/reference

Update conf.py

Update exclude_patterns in conf.py for relocated env_variables include files
Update debugging.rst

Correct include-table for ./reference/env_variables/debug_hip_env.rst
Update memory_management_hip_env.rst

replace hip:hip-memory-coherence-table with coheence-control

Author: randyh62

docs/conf.py

@@ -54,12 +54,12 @@
 numfig = False
 
 exclude_patterns = [
-    "doxygen/mainpage.md",
-    "understand/glossary.md",
-    'how-to/debugging_env.rst',
-    "data/reference/env_variables"
+    "./doxygen/mainpage.md",
+    "./understand/glossary.md",
+    './how-to/debugging_env.rst',
+    "./reference/env_variables"
 ]
 
 git_url = subprocess.check_output(['git', 'config', '--get', 'remote.origin.url']).strip().decode('ascii')
 if git_url.find("git:") != -1:
-    html_theme_options = {"repository_url": "https://github.com/ROCm/hip"}
+    html_theme_options = {"repository_url": "https://github.com/ROCm/hip"}

docs/faq.rst

@@ -40,10 +40,10 @@ for the full list.
 What NVIDIA CUDA features does HIP support?
 -------------------------------------------
 
-The :doc:`NVIDIA CUDA runtime API supported by HIP<hipify:tables/CUDA_Runtime_API_functions_supported_by_HIP>`
-and :doc:`NVIDIA CUDA driver API supported by HIP<hipify:tables/CUDA_Driver_API_functions_supported_by_HIP>`
+The :doc:`NVIDIA CUDA runtime API supported by HIP<hipify:reference/tables/CUDA_Runtime_API_functions_supported_by_HIP>`
+and :doc:`NVIDIA CUDA driver API supported by HIP<hipify:reference/tables/CUDA_Driver_API_functions_supported_by_HIP>`
 pages describe which NVIDIA CUDA APIs are supported and what the equivalents are.
-The :doc:`HIP API documentation <reference/hip_runtime_api_reference>` describes each API and
+The :ref:`HIP runtime API reference<runtime_api_reference>` describes each API and
 its limitations, if any, compared with the equivalent CUDA API.
 
 The kernel language features are documented in the

docs/how-to/debugging.rst

@@ -273,7 +273,7 @@ HIP environment variable summary
 
 Here are some of the more commonly used environment variables:
 
-.. include-table:: data/reference/env_variables/debug_hip_env.rst
+.. include-table:: ./reference/env_variables/debug_hip_env.rst
     :table: hip-env-debug
 
 General debugging tips

docs/how-to/hip_porting_guide.rst

@@ -46,16 +46,16 @@ HIPIFY
 translate CUDA to HIP code. There are two flavours available, ``hipfiy-clang``
 and ``hipify-perl``.
 
-:doc:`hipify-clang <hipify:hipify-clang>` is, as the name implies, a Clang-based
+:doc:`hipify-clang <hipify:how-to/hipify-clang>` is, as the name implies, a Clang-based
 tool, and actually parses the code, translates it into an Abstract Syntax Tree,
 from which it then generates the HIP source. For this, ``hipify-clang`` needs to
 be able to actually compile the code, so the CUDA code needs to be correct, and
 a CUDA install with all necessary headers must be provided.
 
-:doc:`hipify-perl <hipify:hipify-perl>` uses pattern matching, to translate the
+:doc:`hipify-perl <hipify:how-to/hipify-perl>` uses pattern matching, to translate the
 CUDA code to HIP. It does not require a working CUDA installation, and can also
 convert CUDA code, that is not syntactically correct. It is therefore easier to
-set up and use, but is not as powerful as ``hipfiy-clang``.
+set up and use, but is not as powerful as ``hipify-clang``.
 
 Scanning existing CUDA code to scope the porting effort
 --------------------------------------------------------------------------------

docs/how-to/hip_runtime_api/asynchronous.rst

@@ -88,7 +88,7 @@ developer may have to reduce the block size of the kernels. The kernel runtimes
 can be misleading for concurrent kernel runs, that is why during optimization
 it is a good practice to check the trace files, to see if one kernel is blocking
 another kernel, while they are running in parallel. For more information about
-the application tracing, check::doc:`rocprofiler:/how-to/using-rocprof`.
+application tracing, see :doc:`rocprofiler:how-to/using-rocprof`.
 
 When running kernels in parallel, the execution time can increase due to
 contention for shared resources. This is because multiple kernels may attempt

docs/reference/env_variables.rst

@@ -12,24 +12,24 @@ on AMD platform, which are grouped by functionality.
 GPU isolation variables
 ================================================================================
 
-.. include:: ../data/reference/env_variables/gpu_isolation_hip_env.rst
+.. include:: ./env_variables/gpu_isolation_hip_env.rst
 
 Profiling variables
 ================================================================================
 
-.. include:: ../data/reference/env_variables/profiling_hip_env.rst
+.. include:: ./env_variables/profiling_hip_env.rst
 
 Debug variables
 ================================================================================
 
-.. include:: ../data/reference/env_variables/debug_hip_env.rst
+.. include:: ./env_variables/debug_hip_env.rst
 
 Memory management related variables
 ================================================================================
 
-.. include:: ../data/reference/env_variables/memory_management_hip_env.rst
+.. include:: ./env_variables/memory_management_hip_env.rst
 
 Other useful variables
 ================================================================================
 
-.. include:: ../data/reference/env_variables/miscellaneous_hip_env.rst
+.. include:: ./env_variables/miscellaneous_hip_env.rst

docs/data/reference/env_variables/debug_hip_env.rst renamed to docs/reference/env_variables/debug_hip_env.rst

@@ -2,9 +2,9 @@ The memory management related environment variables in HIP are collected in the
 following table. The ``HIP_HOST_COHERENT`` variable linked at the following
 pages:
 
-- :ref:`Coherence control <hip:hip-memory-coherence-table>`
+- :ref:`Coherence control <coherence_control>`
 
-- :ref:`Memory allocation flags <hip:memory_allocation_flags>`
+- :ref:`Memory allocation flags <memory_allocation_flags>`
 
 .. _hip-env-memory:
 .. list-table::