Release Notes Compute Abstraction Layer (CAL) Stream Computing SDK New Features. 2 Resolved Issues. 3 Known Issues. 3.

Transcription

1 Release Notes Compute Abstraction Layer (CAL) Stream Computing SDK New Features 2 Resolved Issues 3 Known Issues 3.1 Link Issues Support for bilinear texture sampling. Support for FETCH4. Rebranded AMD Stream to ATI Stream. New CAL format types (explicit normalized vs unnormalized types, explicit bit-width specifiers). Added CAL D3D10 interoperability sample. Closing and opening CAL context without destroying CAL devices now works properly. Pixel shaders IL kernel invoked after compute shader execution now produces the correct results (Catalyst 9.3). Added calrescreate1d() and calrescreate2d() descriptions in the Stream Computing User Guide. Added more documentation about CAL extensions and extension functions. CAL samples now use the new supported format definitions in cal.h instead of the deprecated formats. Fixed several CAL samples so that output is suppressed when -q is specified. CAL now recognizes both GPUs when using a Radeon HD 4870X2. 32-bit CAL libraries now are installed with a 64-bit operating system by Catalyst. Engine and memory clocks are now set to high state when using a Radeon HD 4870X2 under Vista and Linux when running CAL. Fixed various issues with the use of local data share. Fixed the inf printing issue caused by some CAL samples due to insufficient timer precision. lds_read sample no longer causes a crash and reboot when using an M96 (Catalyst 9.3). As of ATI Stream SDK v1.2.1-beta, the Windows 64-bit versions of the CAL compiler and runtime libraries have changed. This change allows 32-bit and 64-bit CAL applications to run easily on the same system with no environment variable changes. Stream Computing SDK of 5

2 Any precompiled and linked CAL applications must be relinked to the new Windows 64-bit CAL compiler and runtime libraries. The Windows build scripts and commands must be updated to reflect the new library names. For 64-bit Windows systems, the DLL names have added 64 to the end. For example, if a DLL for 32-bit systems is aticalcl.dll, the 64-bit version is aticalcl64.dll. 3.2 Runtime Issues 3.3 Constant Buffers 3.4 Global (Linear) Buffers 3.5 Multi-GPU Issues Under Vista, the cached resource amount returned by caldevicegetattribs() may be incorrect. Under Linux, caldevicegetattribs() incorrectly reports the memory and engine clocks as 0MHz. CAL has a limit of 64 k memory handles. Once this limit is reached, the application must free a resource before allocating a new one. CAL expects that a declared constant buffer has memory assigned to it. If a constant buffer is not used, it must be removed from the program. Global (Linear) buffers are always padded to a 64-element boundary; however, the memexport instruction is not constrained by this, and the program can write into the pad area. During mapping, when copying from local to remote storage, data written to the pad area is not copied (it is lost). The hardware output paths are different when a buffer is attached as an export buffer rather than an output buffer. Ensure that the global buffer has a width that is a multiple of 64 elements. When entering a width that is not multiple of 64 and using the global buffer, calresalloclocal2d returns a warning. Users also can query the error message for this warning. When CrossFire is enabled, performance may vary depending on the order in which commands are submitted to the GPUs in the system. This will be resolved in a future release. The clocks on the Radeon HD 4870X2 may not get set to the high state when running a CAL program on Windows XP. This is a known issue and will be resolved in a future Catalyst driver release. For a multi-gpu configuration on Windows XP, when ATI CrossFire is enabled, the amount of local memory is reduced by half. See the CrossFire installation notes to learn how to disable it. When running under Linux or Windows Vista using CrossFire, only a single GPU is used. On these two operating systems, disable CrossFire. To use a GPU device, a display on the device must be enabled in Windows Display Properties. Devices used by CrossFire do not need to have their display enabled. 2 of 5 Stream Computing SDK 1.4

3 3.6 Long Running Compute Kernels 3.7 DirectX Interoperability 3.8 Building and Running Samples To avoid hanging your machine on Windows systems due to an extremely long-running stream computing program triggering the Windows WatchDog Timer (>10 seconds), disable VPU Recover via the Catalyst Control Panel. To disable VPU Recover on Windows XP (both 32 and 64): a. Open the Catalyst Control Panel. b. Select Advanced > Graphics Settings > VPU Recover. c. Unclick Enable VPU Recover. You also must set a Windows registry key for this to have any effect. Create the following REG_DWORD entry in the registry (using regedit.exe), and set its value to 1: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Watchdog\Display\DisableBugCheck Important: Microsoft highly discourages disabling this feature, and only recommends doing so for debugging purposes. Do this at your own risk. Note that this may be required for programs that run for longer than 10 seconds. DirectX9 interoperability is not supported by CAL running under Windows XP or Linux. It is supported under Windows Vista. For Windows XP and Vista systems, build and run samples using Visual Studio Solution 2005 (VC8). Visual Studio provides two configurations: Win32 and Win64 (x64). The installer sets up CALROOT to the default installation (in the system's environment variables) and adds the following into the user s PATH.: For XP32: <CALROOT>\lib\xp32 For XP64: <CALROOT>\lib\xp64 For Vista 32-bit: <CALROOT>\lib\LH32 For Vista 64-bit: <CALROOT>\lib\LH64 These variables are used while building samples. If the sample projects failed to load, verify that Visual Studio has correctly set CALROOT. To build samples on a Linux system: i. Use make to build the required samples from the installation directory. ii. Use make clobber to delete all temporary build files. Note that Makefile.common links the 64-bit libraries by default. This can be changed to use 32-bit libraries for building 32-bit programs. To run samples: For RHEL 32-bit systems, /usr/lib/ must be in your default library search path. For RHEL 64-bit systems, /usr/lib64/ must be in your default library search path. Stream Computing SDK of 5

4 3.9 Upgrading Catalyst For SLES 32-bit systems, /usr/x11r6/lib/ must be in your default library search path. For SLES 64-bit systems, /usr/x11r6/lib64/ must be in your default library search path. The 64-bit package installs both lib and lib64. To run 32-bit samples on 64-bit machines, change the system s PATH variable to point to /usr/lib/ for RHEL; it must point to /usr/x11r6/lib/ for SLES. Uninstall the previous version of Catalyst before installing a new version Compatibility with Previous Versions of the SDK CAL applications linked against a previous version of the SDK must be relinked against 1.4 CAL libraries due to rebranding library changes. 4 Installation Location of CAL Libraries The Catalyst driver installs the CAL DLL runtime in the following locations. OS XP 32-bit XP 64-bit Location %WINDIR%\system32\aticalcl.dll %WINDIR%\system32\aticalrt.dll %WINDIR%\system32\aticaldd.dll %WINDIR%\system32\aticalcl64.dll %WINDIR%\system32\aticalrt64.dll %WINDIR%\system32\aticaldd64.dll %WINDIR%\SysWoW64\aticalcl.dll %WINDIR%\SysWoW64\aticalrt.dll %WINDIR%\SysWoW64\aticaldd.dll OS Vista 32-bit Vista 64-bit Location %WINDIR%\system32\aticalcl.dll %WINDIR%\system32\aticalrt.dll %WINDIR%\system32\aticaldd.dll %WINDIR%\system32\aticalcl64.dll %WINDIR%\system32\aticalrt64.dll %WINDIR%\system32\aticaldd64.dll %WINDIR%\SysWoW64\aticalcl.dll %WINDIR%\SysWoW64\aticalrt.dll %WINDIR%\SysWoW64\aticaldd.dll RHEL 32-bit /usr/lib/libaticalcl.so /usr/lib/libaticalrt.so /usr/lib/libaticaldd.so 4 of 5 Stream Computing SDK 1.4

5 RHEL 64-bit /usr/lib/libaticalcl.so /usr/lib/libaticalrt.so /usr/lib/libaticaldd.so /usr/lib64/libaticalcl.so /usr/lib64/libaticalrt.so /usr/lib64/libaticaldd.so SLES 32-bit SLES 64-bit /usr/x11r6/lib/libaticalcl.so /usr/x11r6/lib/libaticalrt.so /usr/x11r6/lib/libaticaldd.so /usr/x11r6/lib/libaticalcl.so /usr/x11r6/lib/libaticalrt.so /usr/x11r6/lib/libaticaldd.so /usr/x11r6/lib64/libaticalcl.so /usr/x11r6/lib64/libaticalrt.so /usr/x11r6/lib64/libaticaldd.so 5 Required Catalyst Version This version of the ATI CAL SDK requires ATI Catalyst 9.2 or later. Contact Advanced Micro Devices, Inc. One AMD Place P.O. Box 3453 Sunnyvale, CA, Phone: For Stream Computing: URL: Questions: streamcomputing@amd.com Developing: streamdeveloper@amd.com Forum: The contents of this document are provided in connection with Advanced Micro Devices, Inc. ( AMD ) products. AMD makes no representations or warranties with respect to the accuracy or completeness of the contents of this publication and reserves the right to make changes to specifications and product descriptions at any time without notice. The information contained herein may be of a preliminary or advance nature and is subject to change without notice. No license, whether express, implied, arising by estoppel or otherwise, to any intellectual property rights is granted by this publication. Except as set forth in AMD s Standard Terms and Conditions of Sale, AMD assumes no liability whatsoever, and disclaims any express or implied warranty, relating to its products including, but not limited to, the implied warranty of merchantability, fitness for a particular purpose, or infringement of any intellectual property right. AMD s products are not designed, intended, authorized or warranted for use as components in systems intended for surgical implant into the body, or in other applications intended to support or sustain life, or in any other application in which the failure of AMD s product could create a situation where personal injury, death, or severe property or environmental damage may occur. AMD reserves the right to discontinue or make changes to its products at any time without notice. Copyright and Trademarks 2009 Advanced Micro Devices, Inc. All rights reserved. AMD, the AMD Arrow logo, ATI, the ATI logo, Radeon, FireStream, and combinations thereof are trademarks of Advanced Micro Devices, Inc. Other names are for informational purposes only and may be trademarks of their respective owners. 5 of 5 Stream Computing SDK 1.4