Update README.md

Rebase

README.md

@@ -1,3 +1,73 @@
+
+# AMD ROCm™ v4.3.1 Point Release Notes 
+
+This document describes the features, fixed issues, and information about downloading and installing the AMD ROCm™ software.
+
+It also covers known issues in this release.
+
+## List of Supported Operating Systems
+
+The AMD ROCm platform supports the following operating systems:
+
+![Screenshot](https://github.com/RadeonOpenCompute/ROCm/blob/master/images/SuppEnv.PNG)
+
+
+## What\'s New in This Release
+
+The ROCm v4.3.1 release consists of the following enhancements:
+
+### Support for RHEL V8.4
+
+This release extends support for RHEL v8.4.
+
+### Support for SLES V15 Service Pack 3
+
+This release extends support for SLES v15 SP3.
+
+### Pass Manager Update 
+
+In the AMD ROCm 4.3.1 release, the ROCm compiler uses the legacy pass manager, by default, to provide a better performance experience with some workloads. 
+
+Previously, in ROCm v4.3, the default choice for the ROCm compiler was the new pass manager. 
+
+For more information about legacy and new pass managers, see http://llvm.org.
+
+
+## Known Issues in This Release
+
+### General Userspace and Application Freeze on MI25
+
+For some workloads on MI25, general user space and application freeze are observed, and the GPU resets intermittently. Note, the freeze may take hours to reproduce.
+
+This issue is under active investigation, and no workarounds are available currently.
+
+### hipRTC - File Not Found Error
+
+hipRTC may fail, and users may encounter the following error:
+
+
+		<built-in>:1:10: fatal error: '__clang_hip_runtime_wrapper.h' file not found
+		#include "__clang_hip_runtime_wrapper.h"
+
+
+
+#### Suggested Workarounds
+
+* Set LLVM_PATH in the environment to <path to ROCm llvm>/llvm. Note, if ROCm is installed at the default location, then LLVM_PATH must be set to /opt/rocm/llvm. 
+	
+* Add “-I <path to ROCm>/llvm/lib/clang/13.0.0/include/” to compiler options in the call to hiprtcCompileProgram (). Note, this workaround requires the following changes in the code:
+
+	
+		// set NUM_OPTIONS to one more than the number of options that was previously required
+		const char* options[NUM_OPTIONS];
+		// fill other options[] here
+		std::string sarg = "-I/opt/rocm/llvm/lib/clang/13.0.0/include/";
+		options[NUM_OPTIONS - 1] = sarg.c_str();
+		hiprtcResult compileResult{hiprtcCompileProgram(prog, NUM_OPTIONS, options)};"
+
+
+
+
 # AMD ROCm™ v4.3 Release Notes 
 
 This document describes the features, fixed issues, and information about downloading and installing the AMD ROCm™ software. It also covers known issues and deprecations in this release.
@@ -31,7 +101,7 @@ This document describes the features, fixed issues, and information about downlo
 
 The AMD ROCm platform is designed to support the following operating systems:
 
-![Screenshot](https://github.com/Rmalavally/ROCm/blob/master/images/OSKernel.PNG)
+![Screenshot](https://github.com/RadeonOpenCompute/ROCm/blob/master/images/OSKernelupdated.PNG)
 
 
 ### Fresh Installation of AMD ROCM V4.3 Recommended
@@ -569,7 +639,7 @@ From a user perspective, this new execution mode requires:
 	
 1. Generation of trace data per MPI (or process) rank.
 	
-2. Use of a new "merge_traces.sh" utility script (see: <insert link here>) to combine traces from multiple processes into a unified trace for profiling.
+2. Use of a new ["merge_traces.sh" utility script](https://github.com/ROCm-Developer-Tools/rocprofiler/blob/rocm-4.3.x/bin/merge_traces.sh) to combine traces from multiple processes into a unified trace for profiling.
 	
 For example, to accomplish step #1, ROCm provides a simple bash wrapper that demonstrates how to generate a unique output directory per process:
 	
@@ -577,11 +647,11 @@ For example, to accomplish step #1, ROCm provides a simple bash wrapper that dem
 	$ cat wrapper.sh
 	#! /usr/bin/env bash
 	if [[ -n ${OMPI_COMM_WORLD_RANK+z} ]]; then
- 	 # mpich
-  	export MPI_RANK=${OMPI_COMM_WORLD_RANK}
+ 	  # mpich
+  	  export MPI_RANK=${OMPI_COMM_WORLD_RANK}
 	elif [[ -n ${MV2_COMM_WORLD_RANK+z} ]]; then
-  	# ompi
-  	export MPI_RANK=${MV2_COMM_WORLD_RANK}
+  	  # ompi
+  	  export MPI_RANK=${MV2_COMM_WORLD_RANK}
 	fi
 	args="$*"
 	pid="$$"
@@ -612,7 +682,7 @@ This generates an output directory for each used MPI rank. For example,
 	4096 rank_513556_1
 ```	
 	
-Finally, these traces may be combined using the merge traces script (<insert link here>). For example, 
+Finally, these traces may be combined using the [merge traces script](https://github.com/ROCm-Developer-Tools/rocprofiler/blob/rocm-4.3.x/bin/merge_traces.sh). For example, 
 
 ```
 	$  ./merge_traces.sh -h
@@ -628,7 +698,7 @@ Use the following input arguments to the merge_traces.sh script to control which
 	
 * <*inputdir*>... - space-separated list of rocprofiler directories. If not specified, CWD is used.
 
-The file 'unified/results.json' is generated,  and the resulting unified/results.json file contains trace data from both MPI ranks. 
+For example, if an output directory named "unified" was supplied to the `merge_traces.sh` script, the file 'unified/results.json' will be generated, and the contains trace data from both MPI ranks. 
 
 Known issue for ROCProfiler
 	

default.xml

@@ -12,7 +12,7 @@ fetch="https://github.com/GPUOpen-ProfessionalCompute-Libraries/" />
 fetch="https://github.com/GPUOpen-Tools/" />
     <remote name="KhronosGroup"
 fetch="https://github.com/KhronosGroup/" />
-    <default revision="refs/tags/rocm-4.3.0"
+    <default revision="refs/tags/rocm-4.3.1"
      remote="roc-github"
      sync-c="true"
      sync-j="4" />