../_images/amdblack1.jpg

AMD ROCm™ Release Notes v4.5

October, 2021

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.

List of Supported Operating Systems

The AMD ROCm platform supports the following operating systems:

OS

Kernel

SLES15 SP3

5.3.18-24.49

RHEL 7.9

3.10.0-1160.6.1.el7

CentOS 7.9

3.10.0-1127

RHEL 8.4

4.18.0-193.1.1.el8

CentOS 8.3

4.18.0-193.el8

Ubuntu 18.04.5

5.4.0-71-generic

Ubuntu 20.04.3HWE

5.8.0-48-generic

Enhanced Installation Process for ROCm v4.5

In addition to the installation method using the native Package Manager, AMD ROCm v4.5 introduces added methods to install ROCm. With this release, the ROCm installation uses the amdgpu-install and amdgpu-uninstall scripts.

The amdgpu-install script streamlines the installation process by:

  • Abstracting the distribution-specific package installation logic

  • Performing the repository set-up

  • Allowing user to specify the use case and automating the installation of all the required packages,

  • Performing post-install checks to verify whether the installation was performed successfully

  • Installing the uninstallation script

The amdgpu-uninstall script allows the removal of the entire ROCm stack by using a single command.

Some of the ROCm-specific use cases that the installer currently supports are:

  • OpenCL (ROCr/KFD based) runtime

  • HIP runtimes

  • ROCm libraries and applications

  • ROCm Compiler and device libraries

  • ROCr runtime and thunk

For more information, refer to the Installation Methods section in this guide.

Note: Graphics use cases are not supported in this release.

For more details, refer to the AMD ROCm Installation Guide v4.5 at,

https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation_new.html

AMD ROCm v4.5 Documentation Updates

AMD ROCm Installation Guide

The AMD ROCm Installation Guide in this release includes the following updates:

AMD Instinct™ High Performance Computing and Tuning

System Management Interface

OpenMP Documentation

What's New in This Release

HIP Enhancements

The ROCm v4.5 release consists of the following HIP enhancements:

HIP Direct Dispatch

The conventional producer-consumer model where the host thread(producer) enqueues commands to a command queue (per stream), which is then processed by a separate, per-stream worker thread (consumer) created by the runtime, is no longer applicable.

In this release, for Direct Dispatch, the runtime directly queues a packet to the AQL queue (user mode queue to GPU) in Dispatch and some of the synchronization. This new functionality indicates the total latency of the HIP Dispatch API and the latency to launch the first wave on the GPU.

In addition, eliminating the threads in runtime has reduced the variance in the dispatch numbers as the thread scheduling delays and atomics/locks synchronization latencies are reduced.

This feature can be disabled by setting the following environment variable,

AMD_DIRECT_DISPATCH=0

Support for HIP Graph

ROCm v4.5 extends support for HIP Graph. For details, refer to the HIP API Guide at,

https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD-HIP-API-4.5.pdf

Enhanced launch_bounds Check Error Log Message

When a kernel is launched with HIP APIs, for example, hipModuleLaunchKernel(), HIP validates to check that input kernel dimension size is not larger than specified launch_bounds.

If exceeded, HIP returns launch failure if AMD_LOG_LEVEL is set with the proper value. Users can find more information in the error log message, including launch parameters of kernel dim size, launch bounds, and the name of the faulting kernel. It is helpful to figure out the faulting kernel. Besides, the kernel dim size and launch bounds values will also assist in debugging such failures.

For more details, refer to the HIP Programming Guide at

https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_HIP_Programming_Guide.pdf

HIP Runtime Compilation

HIP now supports runtime compilation (hipRTC), the usage of which will provide the possibility of optimizations and performance improvement compared with other APIs via regular offline static compilation.

hipRTC APIs accept HIP source files in character string format as input parameters and create handles of programs by compiling the HIP source files without spawning separate processes.

For more details on hipRTC APIs, refer to the HIP API Guide at

https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD-HIP-API-4.5.pdf

New Flag for Backwards Compatibility on float/double atomicAdd Function

In the ROCm4.5 release, a new compilation flag is introduced as an option in the CMAKE file. This flag ensures backwards compatibility in float/double atomicAdd functions.

\__HIP_USE_CMPXCHG_FOR_FP_ATOMICS

This compilation flag is not set (“0”) by default, so the HIP runtime uses the current float/double atomicAdd functions.

If this compilation flag is set to “1” with the CMAKE option, the existing float/double atomicAdd functions is used for compatibility with compilers that do not support floating point atomics.

D__HIP_USE_CMPXCHG_FOR_FP_ATOMICS=1

For details on how to build the HIP runtime, refer to the HIP Programming Guide at

https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_HIP_Programming_Guide.pdf

Updated HIP Version Definition

The HIP version definition is updated as follows:

HIP_VERSION=HIP_VERSION_MAJOR * 10000000 + HIP_VERSION_MINOR * 100000
+ HIP_VERSION_PATCH)

The HIP version can be queried from the following HIP API call,

hipRuntimeGetVersion(&runtimeVersion);

The version returned is always greater than the versions in the previous ROCm releases.

Note: The version definition of the HIP runtime is different from that of CUDA. The function returns the HIP runtime version on the AMD platform, while on the NVIDIA platform, it returns the CUDA runtime version. There is no mapping or a correlation between the HIP and CUDA versions.

Planned HIP Enhancements and Fixes

Changes to hiprtc implementation to match nvrtc behavior

In this release, there are changes to the hiprtc implementation to match the nvrtc behavior.

Impact: Applications can no longer explicitly include HIP runtime header files. Minor code changes are required to remove the HIP runtime header files.

HIP device attribute enumeration

In a future release, there will be a breaking change in the HIP device attribute enumeration. Enum values are being rearranged to accommodate future enhancements and additions.

Impact: This will require users to rebuild their applications. No code changes are required.

Changes to behavior of hipGetLastError() and hipPeekAtLastError() to match CUDA behavior available

In a later release, changes to behavior of hipGetLastError() and hipPeekAtLastError() to match CUDA behavior will be available.

Impact: Applications relying on the previous behavior will be impacted and may require some code changes.

Unified Memory Support in ROCm

Unified memory allows applications to map and migrate data between CPU and GPU seamlessly without explicitly copying it between different allocations. This enables a more complete implementation of hipMallocManaged, hipMemAdvise, hipMemPrefetchAsync and related APIs. Without unified memory, these APIs only support system memory. With unified memory, the driver can automatically migrate such memory to GPU memory for faster access.

Supported Operating Systems and Versions

This feature is only supported on recent Linux kernels. Currently, it works on Ubuntu versions with 5.6 or newer kernels and the DKMS driver from ROCm. Current releases of RHEL and SLES do not support this feature yet. Future releases of those distributions will add support for this. The unified memory feature is also supported in the KFD driver included with upstream kernels starting from Linux 5.14.

Unified memory only works on GFXv9 and later GPUs, including Vega10 and MI100. Fiji, Polaris and older GPUs are not supported. To check whether unified memory is enabled, look in the kernel log for this message:

$ dmesg \| grep "HMM registered"

If unified memory is enabled, there should be a “message like registered xyzMB device memory”. If unified memory is not supported on your GPU or kernel version, this message is missing.

Unified Memory Support and XNACK

Unified memory support comes in two flavours, XNACK-enabled and XNACK-disabled. XNACK refers to the ability of the GPU to handle page faults gracefully and retry a memory access. In XNACK-enabled mode, the GPU can handle retry after page-faults, which enables mapping and migrating data on demand, as well as memory overcommitment. In XNACK-disabled mode, all memory must be resident and mapped in the GPU page tables when the GPU is executing application code. Any migrations involve temporary preemption of the GPU queues by the driver. Both page fault handling and preemptions, happen automatically and are transparent to the applications.

XNACK-enabled mode only has experimental support. XNACK-enabled mode requires compiling shader code differently. By default, the ROCm compiler builds code that works in both modes. Code can be optimized for one specific mode with compiler options:

OpenCL:

clang ... -mcpu=gfx908:xnack+:sramecc- ... // xnack on, sramecc
off
clang ... -mcpu=gfx908:xnack-:sramecc+ ... // xnack off, sramecc
 on

HIP:

clang ... --cuda-gpu-arch=gfx906:xnack+ ... // xnack on
clang ... --cuda-gpu-arch=gfx906:xnack- ... // xnack off

Not all the math libraries included in ROCm support XNACK-enabled mode on current hardware. Applications will fail to run if their shaders are compiled in the incorrect mode.

On the current hardware, the XNACK mode can be chosen at boot-time by a module parameter amdgpu.noretry. The default is XNACK-disabled (amdgpu.noretry=1).

System Management Interface

Enhanced ROCm SMI setpoweroverdrive Functionality

The ROCm System Management Interface (SMI) -setpoweroverdrive functionality is used to lower the power cap on a device without needing to enable the OverDrive functionality in the driver. Similarly, even with the OverDrive driver functionality enabled, it is possible to request a lower power cap than the card’s default.

Currently, any use of the -setpoweroverdrive functionality in rocm-smi prints an out-of-spec warning to the screen and requires the user to agree that using this functionality potentially voids their warranty. However, this warning should only be printed when users are trying to set the power cap to higher than the card’s default, which requires the OverDrive driver functionality to be enabled.

For example:

The default power cap is 225.0W before any changes.

[atitest@rhel85 smi]$ ./rocm_smi.py -resetpoweroverdrive

======================= ROCm System Management Interface
========================================================

========================== Reset GPU Power OverDrive
====================================================

GPU[0] : Successfully reset Power OverDrive to: 225W

============================ End of ROCm SMI Log
================================================

Now, after using -setpoweroverdrive to lower the power cap to 123 watts:

[atitest@rhel85 smi]$ ./rocm_smi.py -setpoweroverdrive 123

.. _rocm-system-management-interface-1:

======================= ROCm System Management Interface
========================================================

=========================== Set GPU Power OverDrive
===================================================

GPU[0] : Successfully set power to: 123W

.. _end-of-rocm-smi-log-1:

======================= End of ROCm SMI Log
===========================================

Setting a power cap lower than the default of 225.0W (in this case,
123W) does not give a warning.

To verify that the power is set to the correct value:

[atitest@rhel85 smi]$ ./rocm_smi.py -showmaxpower

.. _rocm-system-management-interface-2:

======================= ROCm System Management Interface
========================================================

======================== Power Cap ===================================

GPU[0] : Max Graphics Package Power (W): 123.0

.. _end-of-rocm-smi-log-2:

========================End of ROCm SMI Log
===========================================

OpenMP Enhancements

The ROCm installation includes an LLVM-based implementation, which fully supports OpenMP 4.5 standard and a subset of the OpenMP 5.0 standard. Fortran and C/C++ compilers and corresponding runtime libraries are included. Along with host APIs, the OpenMP compilers support offloading code and data onto GPU devices.

For more information, refer to

https://rocmdocs.amd.com/en/latest/Programming_Guides/openmp_support.html

ROCm Math and Communication Libraries

In this release, ROCm Math and Communication Libraries consists of the following enhancements and fixes:

Library

Changes

rocBLAS

Optimizations

  • Improved performance of non-batched and batched syr for all sizes and data types

  • Improved performance of non-batched and batched hemv for all sizes and data types

  • Improved performance of non-batched and batched symv for all sizes and data types

  • Improved memory utilization in rocblas-bench, rocblas-test gemm functions, increasing possible runtime sizes.

Changes

  • Update from C++14 to C++17.

  • Packaging split into a runtime package (called rocblas) and a development package (called rocblas-dev for .deb packages, and rocblas-devel for .rpm packages). The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The ‘suggests’ feature in packaging is a transitional feature and will be removed in a future ROCm release.

Fixed

  • For function geam avoid overflow in offset calculation.

  • For function syr avoid overflow in offset calculation.

  • For function gemv (Transpose-case) avoid overflow in offset calculation.

  • For functions ssyrk and dsyrk, allow conjugate-transpose case to match legacy BLAS. Behavior is the same as the transpose case.

hipBLAS

Added

  • More support for hipblas-bench

Fixed

  • Avoid large offset overflow for gemv and hemv in hipblas-test

Changed

  • Packaging split into a runtime package called hipblas and a development package called hipblas-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The ‘suggests’ feature in packaging is a transitional feature and will be removed in a future rocm release.

rocFFT

Optimizations

  • Optimized SBCC kernels of length 52, 60, 72, 80, 84, 96, 104, 108, 112, 160, 168, 208, 216, 224, 240 with new kernel generator.

Added

  • Split 2D device code into separate libraries.

Changed

  • Packaging split into a runtime package called rocfft and a development package called rocfft-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The suggests feature in packaging is a transitional feature and will be removed in a future rocm release.

Fixed

  • Fixed a few validation failures of even-length R2C inplace. 2D, 3D cubics sizes such as 100^2 (or ^3), 200^2 (or ^3), 256^2 (or ^3)…etc. We don’t combine the three kernels (stockham-r2c-transpose). We only combine two kernels (r2c-transpose) instead.

hipFFT

Changed

  • Packaging split into a runtime package called hipfft and a development package called hipfft-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The ‘suggests’ feature in packaging is a tranistional feature and will be removed in a future rocm release.

rocSPARSE

Added

  • Triangular solve for multiple right-hand sides using BSR format

  • SpMV for BSRX format

  • SpMM in CSR format enhanced to work with transposed A

  • Matrix coloring for CSR matrices

  • Added batched tridiagonal solve (gtsv_strided_batch)

Improved

  • Fixed a bug with gemvi on Navi21

  • Optimization for pivot based gtsv

hipSPARSE

Added

  • Triangular solve for multiple right-hand sides using BSR format

  • SpMV for BSRX format

  • SpMM in CSR format enhanced to work with transposed A

  • Matrix coloring for CSR matrices

  • Added batched tridiagonal solve (gtsv_strided_batch)

Improved

  • Fixed a bug with gemvi on Navi21

  • Optimization for pivot based gtsv

r ocALUTION

Changed

  • Packaging split into a runtime package called rocalution and a development package called rocalution-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The ‘suggests’ feature in packaging is a transitional feature and will be removed in a future rocm release.

Improved

  • (A)MG solving phase optimization

rocTHRUST

Changed

  • Packaging changed to a development package (called rocthrust-dev for .deb packages, and rocthrust-devel for .rpm packages). As rocThrust is a header-only library, there is no runtime package. To aid in the transition, the development package sets the “provides” field to provide the package rocthrust, so that existing packages depending on rocthrust can continue to work. This provides feature is introduced as a deprecated feature and will be removed in a future ROCm release.

rocSOLVER

Added

  • RQ factorization routines:

  • GERQ2, GERQF (with batched and strided_batched versions)

  • Linear solvers for general square systems:

  • GESV (with batched and strided_batched versions)

  • Linear solvers for symmetric/hermitian positive definite systems:

  • POTRS (with batched and strided_batched versions)

  • POSV (with batched and strided_batched versions)

  • Inverse of symmetric/hermitian positive definite matrices:

  • POTRI (with batched and strided_batched versions)

  • General matrix inversion without pivoting:

  • GETRI_NPVT (with batched and strided_batched versions)

  • GETRI_NPVT_OUTOFPLACE (with batched and strided_batched versions)

Optimized

  • Improved performance of LU factorization (especially for large matrix sizes)

  • Changed

  • Raised reference LAPACK version used for rocSOLVER test and benchmark clients to v3.9.1

  • Minor CMake improvements for users building from source without install.sh:

  • Removed fmt::fmt from rocsolver’s public usage requirements

  • Enabled small-size optimizations by default

  • Split packaging into a runtime package (‘rocsolver’) and a development package (‘rocsolver-devel’). The development package depends on the runtime package. To aid in the transition, the runtime package suggests the development package (except on CentOS 7). This use of the ‘suggests’ feature is deprecated and will be removed in a future ROCm release.

Fixed

  • Use of the GCC / Clang __attribute__((deprecated(…))) extension is now guarded by compiler detection macros.

hipSOLVER

The following functions were added in this release:

  • gesv

    • hipsolverSSgesv_bufferSize, hipsolverDDgesv_bufferSize, hipsolverCCgesv_bufferSize, hipsolverZZgesv_bufferSize

    • hipsolverSSgesv, hipsolverDDgesv, hipsolverCCgesv, hipsolverZZgesv

  • potrs

    • hipsolverSpotrs_bufferSize, hipsolverDpotrs_bufferSize, hipsolverCpotrs_bufferSize, hipsolverZpotrs_bufferSize

    • hipsolverSpotrs, hipsolverDpotrs, hipsolverCpotrs, hipsolverZpotrs

  • potrsBatched

    • hipsolverSpotrsBatched_bufferSize, hipsolverDpotrsBatched_bufferSize, hipsolverCpotrsBatched_bufferSize, hipsolverZpotrsBatched_bufferSize

    • hipsolverSpotrsBatched, hipsolverDpotrsBatched, hipsolverCpotrsBatched, hipsolverZpotrsBatched

  • potri

    • hipsolverSpotri_bufferSize, hipsolverDpotri_bufferSize, hipsolverCpotri_bufferSize, hipsolverZpotri_bufferSize

    • hipsolverSpotri, hipsolverDpotri, hipsolverCpotri, hipsolverZpotri

RCCL

Added

  • Compatibility with NCCL 2.9.9

Changed

  • Packaging split into a runtime package called rccl and a development package called rccl-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The suggests feature in packaging is a transitional feature and will be removed in a future rocm release.

hipCUB

Changed

  • Packaging changed to a development package (called hipcub-dev for .deb packages, and hipcub-devel for .rpm packages). As hipCUB is a header-only library, there is no runtime package. To aid in the transition, the development package sets the “provides” field to provide the package hipcub, so that existing packages depending on hipcub can continue to work. This provides feature is introduced as a deprecated feature and will be removed in a future ROCm release.

rocPRIM

Added

  • bfloat16 support added.

Changed

  • Packaging split into a runtime package called rocprim and a development package called rocprim-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The suggests feature in packaging is a transitional feature and will be removed in a future rocm release.

  • As rocPRIM is a header-only library, the runtime package is an empty placeholder used to aid in the transition. This package is also a deprecated feature and will be removed in a future rocm release.

Deprecated

  • The warp_size() function is now deprecated; please switch to host_warp_size() and device_warp_size() for host and device references respectively.

rocRAND

Changed

  • Packaging split into a runtime package called rocrand and a development package called rocrand-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The ‘suggests’ feature in packaging is a transitional feature and will be removed in a future rocm release.

Fixed

  • Fix for mrg_uniform_distribution_double generating incorrect range of values

  • Fix for order of state calls for log_normal, normal, and uniform

Known issues

  • kernel_xorwow test is failing for certain GPU architectures.

For more information about ROCm Libraries, refer to the documentation at

https://rocmdocs.amd.com/en/latest/ROCm_Libraries/ROCm_Libraries.html

Known Issues in This Release

The following are the known issues in this release.

Cache Issues with ROCProfiler

When the same kernel is launched back-to-back multiple times on a GPU, a cache flush is executed each time the kernel finishes when profiler data is collected. The cache flush is inserted by ROCprofiler for each kernel. This prevents kernel from being cached, instead it is being read each time it is launched. As a result the cache hit rate from rocprofiler is reported as 0% or very low.

This issue is under investigation and will be fixed in a future release.

Compiler Support for Function Pointers and Virtual Functions

A known issue in the compiler support for function pointers and virtual functions on the GPU may cause undefined behavior due to register corruption.

A temporary workaround is to compile the affected application with

-mllvm -amdgpu-fixed-function-abi=1 option

Note: This is an internal compiler flag and may be removed without notice once the issue is addressed in a future release.

Debugger Process Exit May Cause ROCgdb Internal Error

If the debugger process exits during debugging, ROCgdb may report internal errors. This issue occurs as it attempts to access the AMD GPU state for the exited process. To recover, users must restart ROCgdb.

As a workaround, users can set breakpoints to prevent the debugged process from exiting. For example, users can set breakpoints at the last statement of the main function and in the abort() and exit() functions. This temporary solution allows the application to be re-run without restarting ROCgdb.

This issue is currently under investigation and will be fixed in a future release.

For more information, refer to the ROCgdb User Guide at,

https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_ROCDebugger_User_Guide.pdf

clinfo and rocminfo Do Not Display Marketing Name

clinfo and rocminfo display a blank field for Marketing Name.

This is due to a missing package that is not yet available from ROCm. This package will be distributed in future ROCm releases.

Stability Issue on LAMMPS-KOKKOS Applications

On mGPU machines, lammps-kokkos applications experience a stability issue (AMD Instinct MI100™).

As a workaround, perform a Translation LookAside Buffer (TLB) flush.

The issue is under active investigation and will be resolved in a future release.

Deprecations

AMD Instinct MI25 End of Life

ROCm release v4.5 is the final release to support AMD Instinct MI25. AMD Instinct MI25 has reached End of Life (EOL). ROCm 4.5 represents the last certified release for software and driver support. AMD will continue to provide technical support and issue resolution for AMD Instinct MI25 on ROCm v4.5 for a period of 12 months from the software GA date.

Planned Deprecation for Code Object Versions 2 AND 3

With the ROCm v4.5 release, the generation of code object versions 2 and 3 is being deprecated and may be removed in a future release. This deprecation notice does not impact support for the execution of AMD GPU code object versions.

The -mcode-object-version Clang option can be used to instruct the compiler to generate a specific AMD GPU code object version. In ROCm v4.5, the compiler can generate AMD GPU code object version 2, 3, and 4, with version 4 being the default if not specified.

Hardware and Software Support Information

DISCLAIMER

The information presented in this document is for informational purposes only and may contain technical inaccuracies, omissions, and typographical errors. The information contained herein is subject to change and may be rendered inaccurate for many reasons, including but not limited to product and roadmap changes, component and motherboard versionchanges, new model and/or product releases, product differences between differing manufacturers, software changes, BIOS flashes, firmware upgrades, or the like. Any computer system has risks of security vulnerabilities that cannot be completely prevented or mitigated.AMD assumes no obligation to update or otherwise correct or revise this information. However, AMD reserves the right to revise this information and to make changes from time to time to the content hereof without obligation of AMD to notify any person of such revisions or changes.THIS INFORMATION IS PROVIDED ‘AS IS.” AMD MAKES NO REPRESENTATIONS OR WARRANTIES WITH RESPECT TO THE CONTENTS HEREOF AND ASSUMES NO RESPONSIBILITY FOR ANY INACCURACIES, ERRORS, OR OMISSIONS THAT MAY APPEAR IN THIS INFORMATION. AMD SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AMD BE LIABLE TO ANY PERSON FOR ANY RELIANCE, DIRECT, INDIRECT, SPECIAL, OR OTHER CONSEQUENTIAL DAMAGES ARISING FROM THE USE OF ANY INFORMATION CONTAINED HEREIN, EVEN IF AMD IS EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.AMD, the AMD Arrow logo,and combinations thereof are trademarks of Advanced Micro Devices, Inc.Other product names used in this publication are for identification purposes only and may be trademarks of their respective companies.©[2021]Advanced Micro Devices, Inc.All rights reserved.

Third-party Disclaimer

Third-party content is licensed to you directly by the third party that owns the content and is not licensed to you by AMD. ALL LINKED THIRD-PARTY CONTENT IS PROVIDED “AS IS” WITHOUT A WARRANTY OF ANY KIND. USE OF SUCH THIRD-PARTY CONTENT IS DONE AT YOUR SOLE DISCRETION AND UNDER NO CIRCUMSTANCES WILL AMD BE LIABLE TO YOU FOR ANY THIRD-PARTY CONTENT. YOU ASSUME ALL RISK AND ARE SOLELY RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOUR USE OF THIRD-PARTY CONTENT.