CodeXL 1.4 Released!

Happy day today – the latest release of CodeXL just cleared QA testing and was published.

Here’s what’s new in this release:

  • Visual Studio 2013 CodeXL Extension
    Adopters of Visual Studio’s most recent release can now use CodeXL directly from the Visual Studio IDE.
  • New Shader Analyzer included in CodeXLAnalyzer command line tool (Windows only)
    Back by popular demand, the formerly named GPU Shader Analyzer (GSA) which was frozen for over 2 years is now a part of CodeXL’s command line tool. The renewed tool uses a live-driver model, i.e. utilizes the compilers of the DirectX runtime and AMD driver installed on the local station for analysis of HLSL shaders.
  • Support for Volcanic Islands family GPUs – debugging, profiling and analyzing.
  • Enhanced Analyze Mode
    CodeXL 1.3 introduced the Analyze mode as a replacement for the legacy APP KernelAnalyzer2 tool. We got a lot of feedback about this new feature from users. Here’s the Analyze mode news:

    • Streamlined Analyze Mode for quick creation and editing of CL files
      Prominent among the user feedback was the request to simplify the usage and reduce the number of clicks between launching the tool and starting to edit OpenCL™ code, without fumbling through project creation. We did just that. Drag and drop an OpenCL™ file onto CodeXL or click the Play toolbar button and select Create New OpenCL™ File to start editing. Project creation is automatically handled for you.
    • New Build Options node in the Project Settings tree for easy control and visibility of offline OpenCL™ build settings
    • Analysis table displays separate clocks count for single Work Item and for the total workload
    • User Experience improvements
      • New ‘No Project Loaded’ dialog for quickly creating a project and setting the relevant mode
      • Re-designed ‘Project Settings’
        With a lot of functionality come a lot of configuration options. We redesigned the Project Settings as a tree with several levels of configuration options.
      • GPU Debugger’s Locals view displays work group dimensions and properties during kernel debugging
      • GPU Profiler timeline modifications
        • User markers wrap API calls as expandable tree nodes
        • New columns in the API Trace table
        • The Properties View shows the properties of the selected timeline item
        • Application Trace session type has been renamed to Application Timeline Trace
  • Deletion of multiple profiler sessions is now available from the explorer tree’s context menu
  • CL files Drag n’ Drop automatically adds the file to the CodeXL project
  • CPU Profiling enhancements
    • Added support for Kaveri and Mullins APUs
    • New capability: Attach To Process
      Attach the profiler to a process that is already running so its symbols info and Callstack data will be included in the profiling session.
    • New capability: unbound system-wide profiling
      Profile all the processes that are currently running without tying the session to a specific process.
    • Callstack collection now collects code executed in kernel-mode in addition to user-mode code that was collected by previous CodeXL releases. This is perfect for profiling drivers.
    • Call graph view – simplified the Parents and Children table and corrected the display
    • Automatic fetching of disassembly blocks when scrolling through CPU Profiling source code/disassembly view
    • Display indication of symbols loaded per module
    • CLPerfMarker library replaced by a new generic logging API library AMDTActivityLogger
    • OpenCL™ is no longer a prerequisite for doing OpenGL debugging
    • Over a hundred bug fixes!
      We made increased quality a goal of this release. This is the most stable and robust release of CodeXL!

CodeXL is available for download at

Please use our CodeXL Forum to provide feedback about CodeXL and for support requests.

Happy development!

– Doron Ofek

Doron Ofek is a manager at AMD Developer Tools group and leads CodeXL development. His postings are his own opinions and may not represent AMD’s positions, strategies or opinions. Links to third party sites and references to third party trademarks, are provided for convenience and illustrative purposes only. Unless explicitly stated, AMD is not responsible for the contents of such links, and no third party endorsement of AMD or any of its products is implied.

Comments are closed.