AMD CodeXL 1.7 GA Release Notes

Transcription

1 AMD CodeXL 1.7 GA Release Notes Thank you for using CodeXL. We appreciate any feedback you have! Please use the CodeXL Forum to provide your feedback. You can also check out the Getting Started guide on the CodeXL Web Page and the latest CodeXL blog at AMD Developer Central - Blogs This version contains: For 64-bit Windows platforms o CodeXL Standalone application o CodeXL Microsoft Visual Studio 2010 extension o CodeXL Microsoft Visual Studio 2012 extension o CodeXL Microsoft Visual Studio 2013 extension o CodeXL Remote Agent For 64-bit Linux platforms o CodeXL Standalone application o CodeXL Remote Agent Note about installing CodeAnalyst after installing CodeXL for Windows AMD CodeAnalyst has reached End-of-Life status and has been replaced by AMD CodeXL. CodeXL installer will refuse to install on a Windows station where AMD CodeAnalyst is already installed. Nevertheless, if you would like to install CodeAnalyst, do not install it on a Windows station already installed with CodeXL. Uninstall CodeXL first, and then install CodeAnalyst. System Requirements CodeXL contains a host of development features with varying system requirements: GPU Profiling and OpenCL Kernel Debugging o An AMD GPU (Radeon HD 5000 series or newer, desktop or mobile version) or APU is required. o The AMD Catalyst Driver must be installed, release or later. Catalyst (driver ) is the recommended version. See "Getting the latest Catalyst release" section below. For GPU API-Level Debugging, a working OpenCL/OpenGL configuration is required (AMD or other). CPU Profiling o Time-Based Profiling can be performed on any x86 or AMD64 (x86-64) CPU/APU.

2 o The Event-Based Profiling (EBP) and Instruction-Based Sampling (IBS) session types require an AMD CPU or APU processor. Power Profiling o Supported on Carrizo, Kaveri, Mullins and Temash APUs. Supported platforms: Windows platforms o Windows 7 64-bit and bit o Note: For the CodeXL Visual Studio 2010/2012/2013 Package, the station must be installed with Visual Studio 2010/2012/2013, respectively. However, the CodeXL Standalone Application does not require Visual Studio to be installed. Linux platforms o Red Hat EL 7 64-bit o Ubuntu bit Getting the latest Catalyst release The way to get the latest beta driver is to use the links "Latest Windows Beta Driver" and "Latest Linux Beta Driver" on the Graphics Drivers support page: New in this version The following items are new in this version: Beta-level support for Windows 10 TP2. Static Analyzer o Build and analyze of DirectX shaders in the GUI application/vs extension Power Profiler o Remote Power Profiling o Support for Carrizo APUs GPU Profiler o Specify which kernels to profile CPU Profiler o C++ inline functions are now included in the call-graph view Examples applications o Teapot modified for compatibility with Red Hat 7 o Added Matrix Multiplication example for CPU Profiling UI enhancements o New Search toolbar - search is enabled for most of the textual views o Many improvements to Power Profiler UI o Static Analyzer - added syntax highlighting for IL display o Double clicking on build errors in output pane jumps to the relevant source code line o The System Information dialog details both 32 and 64-bit OpenCL runtimes Installation length of the CodeXL Visual Studio Extension is much shorter and doesn t include a launch of devenv.exe /setup in the background.

3 Fixed Issues The following are the major fixes that were not part of the 1.6 release and are new to this version: GPU Debugging OpenGL apps on Ubuntu platforms with Northern Islands GPUs may cause system hang after several minutes. Fixed with Catalyst Omega and CodeXL 1.7 (454292) For CPU Profiler Cache Line Utilization sessions, profile counters are not shown for source code of C++ inline functions. (456796) C++ inline functions are not included in the CPU Profiler s Call Graph view and their samples are attributed to their parent functions. (456915) CPU Profiler fails to write profile data if custom profile includes Time Based Profiling, Event Based Profiling, Instruction Based Sampling, and Cache Line Utilization and the log mode is set to Extensive. (459690) The value of Const variables appears to change when the GPU Debugger steps through an if block. (459766) The Static Analyzer s Analysis view shows zero SGPRs in use although the runtime modified the SGPRs in use to non-zero. This happens with Catalyst Omega (driver ). (459915) On Ubuntu 14.04, symbol information may not be available when Cpu Profiling is performed on the local physical machine, but it works fine when run via ssh. (460036) CPU Profiler may not attribute samples correctly to nested inlined functions. (457173) CPU Profiler call graph view for 32-bit Windows applications may show bogus parents of functions. (451817, , , ) On Linux, CPU Profiling does not display C++ inline functions in the top 5 host functions table of the Overview view. (458261) On Red-Hat 7, the GPU Debugger fails to debug the Teapot sample. Workaround: Red-Hat 7 is missing some required modules. See the Download and Install CodeXL section in the CodeXl Quick Start Guide. (458271) The kernel execution time reported by the GPU Profiler may not be reliable when running on an APU with active power management. (413379) GPU Profiler Performance Counters shows wrong count of LDS instructions for RecursiveGaussian APP SDK sample. (459463) CPU Time-Based Profiling on AMD CPUs at 1ms intervals generates number of samples that varies by up to 5% from the expected quantity. (459322) Known Issues Debugging OpenCL kernels that use read-modify-write atomic operations is not supported. GPU Debugging on OpenCL Static C++ Kernels is not supported. (334415) OpenCL 1.2 keyword printf and barriers are not supported during kernel debugging. Building kernels with OpenCL 1.2 clcreateprogramwithbinaries and cllinkprogram API prevents the display of source code when debugging these kernels. (369171) Performing CPU Profiling with Call-Stack Sampling (CSS) enabled, on systems with discrete graphics card (Radeon HD 5000, 6000 or 7000 series) and Linux kernel version 3.0 or lower, may result in Linux kernel panic. This kernel panic does not occur with Linux kernel version 3.2 onwards. (352399) CPU Profiling is disabled on Windows 8 and 8.1 if Hyper-V is enabled. (438549) o Note that installing Microsoft Windows Phone 8.0 SDK activates Hyper-V. CPU Profiling on Linux platforms - Limitations of PERF

4 o CPU profiling uses PERF which requires kernel or later. CPU Profiling with Call Stack Sampling requires Linux kernel 3.0 or later. However, we recommend using kernel 3.2 and above which has shown to be more stable. o Call chain analysis on Linux currently depends on the call chain information provided by Linux PERF. This requires the profiled binaries to have stack frame pointer. (i.e. compiled with -fno-omit-frame-pointer). o For non-root users to run CodeXL CPU profiling, "/proc/sys/kernel/perf_event_paranoid" needs to be set to "-1". o Instruction-Based Profiling on Linux requires Linux kernel 3.5 and above, and must be used with system-wide profiling. o Call chain information (stack trace) for inline functions is not available. PERF call chains which contain call stacks across modules have shown to be truncated. This results in inaccurate "Deep Samples", "Downstream Samples", and "Call Path" analysis. If gdebugger 6.x is installed on the machine, mouse click doesn't start text fields editing in CodeXL Visual Studio Extension. Workaround: Navigate to the text fields using TAB or uninstall gdebugger before installing CodeXL. (344811) Menu items are present but not visible after minimization and restore of CodeXL in Ubuntu system using Unity theme. Workaround: Use Unity 2D theme instead of Unity theme. (353082) AMDTTeapot sample may crash while debugging OpenCL kernels after multiple step operations (45 or more). (357741) CPU Profiling on Windows 8 shows two target applications in Profile Overview. The conhost.exe process is an actual executable. This process fixes a fundamental problem in the way previous versions of Windows handled console windows, which broke drag & drop in Vista. If CodeXL is installed in path that includes non-ascii Unicode characters, profiling does not work (365118). The GPU Debugger can't step into a kernel if blocks that contain a return statement. (422699) CPU Profiling multiple processes with call stack collection may result in call graph view displaying addresses instead of function names for functions used by more than one process. (441541) Static Analysis runs out of memory and crashes while building and analyzing a CL file with over a hundred kernels that use OpenCL C++ templates. (443221) CPU Profiler runs out of memory and closes down while performing post-processing of a systemwide profile session that combines IBS, CLU and Time-based sampling for over 5 minutes. (451815) Performing 2 GPU Profiling sessions concurrently - Timeline Application Trace and Performance Counters - on a Red Hat Linux System may cause a system hang after several minutes. (452889) On Linux, the GPU Profiler displays empty Kernel Occupancy view if the occupancy percentage link is clicked twice. (455109) GPU Debugger will not debug individual kernels included in programs whose total LDS usage exceeds 32KB. (455672) In Analyze Mode, building a CL file with over 100 kernels succeeds but statistics and analysis are not displayed. (455401) On Linux, Analyze Mode GUI displays incorrect IL and ISA instructions if locale is not "en_us.utf-8". (452765) On Linux, CodeXL Teapot sample crashes when running on AMD Devastator GPUs with driver

5 On Linux, GPU Profiling Performance Counters of OpenGL applications running on AMD Devastator GPUs with driver causes a system hang. On Linux, if CodeXL is launched via SSH and X-forwarding first in usermode and then in root mode, CodeXL aborts. (459248) On Linux, GPU Profiling Performance Counters of an OpenGL application may cause a system hang after a few seconds. (460162) GPU Debugger does not stop at breakpoints inside kernels that take a very long time to execute and cause a driver TDR. (456504) On Red-Hat 7, GPU Profiling Performance Counters of APP SDK samples SoAversusAoS, TransferOverlap and TransferOverlapCPP generates empty sessions. (459457) On Red-Hat 7, the Kernel Occupancy column is not shown in GPU Profiling Performance Counters of APP SDK sample AsyncDataTransfer. (459459) If the profiled station goes into Sleep/Hibernate state during a Power Profiling session, only data collected before hibernation is displayed, and the navigation slider does not respond. (459572, ) The Call-graph view for CPU Profiling with callstack collection of 32-bit applications may show two separate paths for a function that has a single path. (459702) With driver Catalyst Omega , performing multiple GPU Profiler sessions result show large variance of values for VALUUtilization% and VFetchSize. (459892) On Red-Hat 7 with Catalyst Omega 14.12, GPU Profiling Performance Counters of the APP SDK NBody sample may crash and exit. (458426) In Power Profile sessions on machines without Catalyst installed, igpu Frequency is constantly shown as 100MHz. If Catalyst is installed, then CodeXL reports the proper integrated-gpu frequency. (459364) Support Please use our CodeXL Forum for support requests and our development team will contact you.