AMD CodeXL 1.1 GA Release Notes

Thank you for using CodeXL. We appreciate any feedback you have! Please use our 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:

 CodeXL Visual Studio 2012 and 2010 packages and Standalone application, for 32-bit and 64-bit Windows platforms  CodeXL for 64-bit Linux platforms  Kernel Analyzer v2 for both Windows and Linux platforms

Note about 32-bit Windows CodeXL 1.1 Upgrade Error On 32-bit Windows platforms, upgrading from previous version of CodeXL using the CodeXL 1.1 installer will remove the previous version and then display an error message without installing CodeXL 1.1.

The recommended method is to uninstall previous CodeXL before installing CodeXL 1.1.

If you ran the 1.1 installer to upgrade a previous installation and encountered the error mentioned above, ignore the error and run the installer again to install CodeXL 1.1.

Note about installing CodeAnalyst after installing CodeXL for Windows CodeXL can be safely installed on a Windows station where AMD CodeAnalyst is already installed. However, do not install CodeAnalyst 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 5xxx or newer) or APU is required o The AMD Catalyst Driver must be installed, release 12.8 or later. Catalyst 13.1 is the recommended version.  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. On Windows 8, only AMD CPUs/APUs are supported. o The Event Based Profiling (EBP) and Instruction Based Sampling (IBS) session types require an AMD CPU or APU processor.

Supported platforms:

 Windows platforms o Windows 7 32-bit and 64-bit, Beta support for Windows 8 32-bit and 64-bit o Visual Studio 2010/2012 must be installed on the station before the CodeXL Visual Studio 2010/2012 Package is installed, respectively.  Linux platforms o Red Hat EL 6 u2 64-bit o Ubuntu 12.04 64-bit

New in this version The following items are new in this version:

 Beta support for Windows 8, 32 and 64 bit.  Visual Studio 2012 integration  Support for KDE desktop environment on supported Linux distributions  OpenCL/OpenGL Debugger and Profiler Support for AMD’s Sea Island family of GPUs.  CPU Profiler support-ready for AMD’s Kabini APUs  User experience enhancements: o Mode Specific layouts display a sub-set of CodeXL views and toolbars that match the current mode – Debug or Profile. o Profile Session Explorer Tree and Debug Explorer Tree views are merged into a single view named CodeXL Explorer. o New design for Automatic Updates dialog  Installation is now enabled for Windows platforms that are not formally supported. CodeXL may be installed on Windows Vista and Windows Server 2008 or later, although its function has not been verified on these platforms. Fixed Issues The following fixes were not part of the 1.0 release and are new to this version:

 Incorrect step-in order when debugging APP SDK MatrixMulImage sample (345842) – fixed in Catalyst 13.3  CodeXL crashes if you set a breakpoint at glUniformMatrix4fv (364063)  When running CodeXL remotely on a Trinity platform with Ubuntu using putty/xming a segmentation fault is thrown (367512) – fixed in Catalyst 13.3  On Ubuntu systems, CodeXL may throw a segmentation fault while debugging the Teapot sample. (366589)  CPU Profiler on RHEL6 U2, PERF has a known issue with Call Stack Ssampling (CSS) data on Time Based Profile run i.e. CSS data is not correctly shown for Time based profile run on RHEL6 U2. (355108, 359033)  CodeXL crashes when debugging APP SDK sample MatrixTranspose on a FirePro W8000 or FirePro W9000 card (368026) – fixed in Catalyst 13.3  GPU Debugger - using certain OpenGL pixel formats for textures could cause crashes when viewing the texture images.  GPU Profiler Performance Counters - Complete path and Fast path always report 0 on Caicos (352444)  Global memory cannot be accessed by debugger when using Evergreen/Northern Islands and Catalyst 12.9 or later (370182) – fixed in Catalyst 13.1.  GPU Profiler unresponsive during post-profile processing (343672)  ‘Stop debugging’ button in toolbar is disabled after breakpoint hit in Visual Studio (352398)  Drag&Drop is active while profiling/debugging in progress (353077)  "Home Page | Recent projects" lists Teapot sample twice on Linux (354076)  Two .cxl files are created when you open the Teapot example on Linux (354917)  Log Files & image dir changes to "tmp" once you close Options window on Linux (355244)  On Linux, CPU Profiler cannot start profile on invalid session import; Re-running CodeXL works (355804)  CodeXL Customize tool bar Options shows Control names prefixed "cmdid" (356138)  Floating point precision option should not contain 0 as list item on Linux (356155)  Teapot sample loads for profiling session even if Debug mode is selected (356156)  GPU Profiling BasicCompute11 sample won’t generate DirectX ASM (356471)  Chars not allowed in filenames should not be in CodeXL project name (357501)  The menu command ‘Profile Mode’ is not updated with session type in Visual Studio (357505)  Toolbars embedded within views should be updated when mode changes (359173)  CPU Profiler shows huge number of timer samples for shell script used to run FORTRAN app (361568)  Cannot delete breakpoint set in code from Breakpoints window, after the debug session ends (362458)  Breakpoints list in the Breakpoints dialog does not get updated on adding breakpoint from Function Call History view (362669)  Step In after "glBindBuffers" breakpoint results in Catalyst Control Center crash (363176)  "Show detailed batch statistics" button is always enabled (363463)  Exported CSV file does not have column headings (363612)  You should not be allowed to open a project while another project is being debug (364158)  GPU Profiling options break after several profile sessions on Linux (366547)  Incorrect directory structure in tarball prevents loading Teapot sources on Linux (368943)  Profiling Teapot sample with Performance Counters using Catalyst 12.10 causes crash (369572) – fixed in Catalyst 13.1.  Function Call History view shows only first letter of glStringMarkerGREMEDY arg (370015)  KernelAnalyzer crashes on clicking "Build->Options" on a system with no discrete GPU installed (371005)  CPU Profiler displays "unknown" column on Ubuntu Time based profile run (371373)  GPU Debugger cannot evaluate value of a array element in watch (371502)  Multiwatch view is broken if variable value active range is too large (371522)  Shortcut F5 won't work when Execution Toolbar is hidden (371820)  CPU Profiler "% of total session samples" data always shown wrong in module data view (372074)  Installer displays "This action is only valid for products..." error after installation (372323)  Observed Blue-Screen-Of-Death couple of times on windows7 32-bit machine while rebooting (372833)  OpenGL function calls logging field in options window is not functional (372834) Known Issues  CPU Profiling is disabled on Windows 8 and Windows Server 2012 platforms running on non- AMD CPUs. (385105)  ‘Navigation to Source Code’ option is disabled for GPU Profiling Application Trace on Tahiti GPUs on Linux platforms. (376736)  On Linux platforms with Cayman GPUs, if the screen saver locks the station after inactivity timeout during GPU Profiling Application Trace with ‘Enable Navigation to Source Code’ checked, the system cannot be unlocked. (376736)  Debugging OpenCL kernels that use read-modify-write atomic operations is not supported.  GPU Debugging on OpenCL Static C++ Kernels is not supported. (345852)  __read_only and __write_only Image variables are not shown in locals during GPU Debugging. (345852)  OpenCL 1.2 keyword printf is not supported during kernel debugging.  Building kernels with OpenCL 1.2 clCreateProgramWithBinaries and clLinkProgram API prevents debugging these kernels. (369183)  CPU profiling for managed code (OpenCL, OpenGL, Java, .Net …) is not supported. Module/Source information will not be available for managed code.  Running CpuProfiling with Call-Stack Sampling (CSS) enabled, on systems with discrete graphics card (5000, 6000, 7000 series), may result in Linux kernel panic. This kernel panic does not occur with Linux kernel version 3.2 onwards.  CPU Profiling on Linux platforms – Limitations of PERF o CPU profiling uses PERF which requires kernel 2.6.32 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.

 Call Stack data collection may result in kernel panic on Ubuntu with kernel version 3.0 or lower. Workaround: Upgrade the Ubuntu kernel to 3.2 or above. (352399)  PERF call chain which contains call stack across modules has shown to be truncated. This results in inaccurate "Deep Samples", "Downstream Samples", and "call path" analysis.  Importing a thread based session generated from CodeAnalyst sometimes results in CodeXL crash. (356479)  if gDEBugger is installed, mouse click doesn’t start text fields editing in CodeXL Visual Studio Extension. Workaround: Navigate to the text fields using TAB. (344811)  Menu items are present but not visible after a minimization of CodeXL in Ubuntu system using Unity. Workaround: Use Unity 2D instead of Unity. (353082)  Teapot sample may exhibit crash while debugging OpenCL kernel after multiple step in operations (45 or more) and Info level log or lower. (357741)  The variable type displayed for ‘int4’ variables appears as an unnamed struct. (362152)  APP SDK QuasiRandomSequence reports 0 for all performance counters on Cape Verde platforms (357699)  CodeXL points to incorrect source line on first step into kernel (370960)  Program crashes at clBuildProgram when compiling a IL program used in CodeXL on Windows 8- 32 bit. (382266)  For an application that performs simultaneous asynchronous data transfer and kernel execution, the timeline shown in the Application Trace session view will not show these operations being overlapped. This is because the driver and hardware force these operations to be synchronous while profiling. (333981)  CPU Profiling on Win8 shows two target applications in Profile Overview. The conhost.exe is a completely legitimate 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 Unicode characters, profiling does not work (365118).  Step-in operations on a kernel with a struct variable may exhibit wrong line order. (384976)  GPU Profiler Performance Counters show wrong values for DirectX samples on Intel Platform. (378477)  On Red Hat EL 6 U2 systems, CodeXL may throw a segmentation fault when the application is being closed. (366197)  GPU Debugger Locals view shows constant numeric value 0x0000 for local memory variables although viewing local memory variables is unsupported (332624)  Although support has been added to CodeXL for collecting GPU Performance Counters on Sea Islands (Radeon HD8000 series) GPUs, this support requires actual Sea Islands hardware and a Catalyst driver with this support enabled, neither of which are publically available as of the release of CodeXL 1.1. Once both the hardware and the official driver are available, CodeXL 1.1 should be able to collect and display the GPU Performance counters, though there may be unexpected issues that arise that cause this support to not function correctly.

Support Please use our CodeXL Forum to request support and our development team will contact you.