1. CodeAnalyst application runs as a native 64-bit application on 64-bit Windows OS flavors.

2. We have made several optimizations to help improve overall CodeAnalyst experience a pleasant one.

3. We have fixed quite a lot of bugs to help improve overall stability of CodeAnalyst.

We hope that this release helps you with your work efficiently and pleasantly. If you encounter across any bugs or see where AMD CodeAnalyst could be improved, please reach us through our forums or by replying this blog page.

OpenCL and the OpenCL logo are trademarks of Apple Inc. used with permission by Khronos.

As part of AMD’s commitment to developer tools for heterogeneous compute platforms, I am excited to introduce you to gDEBugger 6.2.

gDEBugger 6.2 is a key milestone that adds Linux® support and a new standalone user interface that is available for both Linux® and Windows®. The major highlights of this release are:

• Support for Red Hat®, Ubuntu® and OpenSUSE™ Linux® distributions
• New standalone user interface with enhanced GUI for ease of use and better navigation
• Support for OpenCL™ kernel and API level debugging on AMD Radeon HD 7000 series graphics cards
• Support for OpenCL™ 1.2 beta drivers
• Stability and feature enhancements along with updated Microsoft® Visual Studio® Plugin

You can visit gDEBugger landing page to get more details and download it.

We value your input. If you have suggestions on how to improve our tools or if you experience any issues, let us know through our forums or comments to this blog.

Milind Kukanur is a Sr. Manager, Product Management at AMD. 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.

AMD’s second generation architecture of  core processors  codenamed “Bulldozer” was released in 2011 (products included  AMD Opteron™ 6200, AMD Opteron 4200 and FX  Processors).  These processors include a more advanced hardware prefetcher which is able to pick up more varied data access patterns than previous generation processors. 

Oracle JVMs by default use software prefetch instructions to prefetch heap memory when allocating new objects on the heap. (Java applications tend to do a lot of heap allocations).  Sometimes the software and hardware prefetching can get in each other’s way. We discovered that for most Java workloads the best performance on Bulldozer family processors could be achieved by just using the hardware prefetcher and disabling  the software prefetching.

AMD worked with Oracle to get this no software prefetch strategy into the Java 7 release (released in July 2011) as the default for these Bulldozer processors.  For those still using Java 6 or earlier releases, the same effect can be achieved by explicitly using the following option on the java command line: –XX:AllocatePrefetchStyle=0.

Tom Deneau is a Senior Member Technical Staff in the Runtimes Team at AMD. 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.

The recent GCC release helps improve support for AMD Opteron™ 6200 series and AMD FX series processors, and adds support for upcoming AMD processors with the “Piledriver” core.  This is an important release for the developer community and brings significant performance improvements, new features and infrastructure enhancements over the previous versions.  A preview of the key highlights includes:

• Performance improvements  in the compiler option for maximum optimization level (-Ofast)
• ISA support including FMA3, F16C, TBM and BMI instruction sets (-m[no-]fma, -m[no-]f16c, -m[no-]tbm, -m[no-]bmi)
• Improved robustness, scalability, memory usage on link-time optimization (-flto).
• Support for OpenMP 3.1 (-fopenmp)
• Option to store local arrays on stack memory for FORTRAN (-fstack-arrays).
• Addition of C++ 11 (-std=c++11)

GCC now has optimized performance settings and compile flags for the AMD processors. These include:

• AMD processors with “Piledriver” core (options: -march=bdver2 and -mtune=bdver2)
• AMD Opteron™ and AMD FX series processors with “Bulldozer” processor core (options: -march=bdver1 and -mtune=bdver1) and
• AMD processors with “Bobcat” core (options: -march=btver1 and -mtune=btver1).

For a list of compiler options to use with AMD processors, check out our compiler quick reference guide.

Overall, GCC 4.7 runtime performance is designed to be faster than previous versions including GCC 4.6 or default versions that come with commercial Linux distributions (e.g. RHEL or SLES), such as GCC 4.4.6. If your application is sensitive to runtime performance then you might consider getting the latest version of GCC. Check out gcc.gnu.org to learn about the new updates and upgrade your compiler to the latest version.

GCC 4.7 release notes can be found here.

By the way, did I mention GNU Compiler Collection turned 25 this year… Happy anniversary GCC!

Milind Kukanur is a Sr. Manager, Product Management at AMD. 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.

We are excited to bring a guest presenter and well known GPGPU guru, Rob Farber, to deliver a series of three OpenCL webinars that accompany his 9 AMD sponsored OpenCL article series found below:

1.  April 10th, 10AM PDT, Introducing Portable Parallelism

• C and C++ APIs
• OpenCL Memory Spaces
• The OpenCL Execution Model
• Reference articles: 1, 2 and 3

 2.  April 24th, 10AM PDT, Coordinating OpenCL Computations on one more Heterogeneous Devices

• How to Concisely Utilize Multiple Command Queues and Coordinate Tasks Across Multiple Heterogeneous Devices such as two GPU + CPU
• Code Sample Discussion: Massively Parallel Random Number Test Framework
• Reference articles 4, 5 and 8

3.  May 1st, 10AM PDT, Accelerate Rendering by an Order of Magnitude with OpenCL, Plus a View to the Multi-core and Web-enabled Future

• How to use OpenCL to Provide High-Quality, Fast Rendering in Combination with Primitive Restart
• Device Fission, Partitioning Hardware Capabilities for Optimal Resource Usage
• Looking to the Future – WebCL
• Reference articles 6, 7 and 9

Registration is limited, don’t wait, register for all three today!

Who is Rob Farber you ask?

Rob Farber is a senior scientist and research consultant at the Irish Center for High-End Computing in Dublin, Ireland and Chief Scientist for BlackDog Endeavors, LLC in the US.  Previously, he has been on staff at several US national laboratories including Los Alamos National Laboratory, Lawrence Berkeley National Laboratory, and at Pacific Northwest National Laboratory. He also served as an external faculty member at the Santa Fe Institute, co-founded two successful start-ups, and has been a consultant to Fortune 100 companies. His articles have appeared in many venues including The Code Project, Doctor Dobb’s Journal, and Scientific Computing. Rob recently completed a book teaching massive parallel computing.

Sharon Troia is a Sr. Developer Relations Engineer in the Developer Outreach Group at AMD. Her postings are her 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.

The OpenCL  1.2 beta includes  the following OpenCL™ 1.2 functionality:

• Host access flags for memory objects enable more efficient buffer handling and provide added protection. For example, a buffer that is created as “write only” cannot be read from the host.
• Pattern based GPU buffer and image initialization can help eliminate need for certain buffer/image transfers
• Memory objects migration supports transfer of buffers prior to need
• New generalized image creation API
• Enhanced image/buffer map operations
• OpenCL 1.2 CPU device partition including partition of a CPU after addition to a context
• Generalized 1D and 2D images, image arrays,  and image<-> buffer interop
• Libraries support including the separation of compile and link phases and the ability to compile with external symbols
• Kernel reflection, the ability to query a kernel’s arguments
• Support for printf as a built in function

OpenCL™ 1.2 support is scheduled to  be included in our official AMD Catalyst™ driver releases in the coming months.

Mark Ireton is the Product Manager for Compute Solutions at AMD. 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.

Today marks the release of the Beta of Visual Studio 11, an exciting new version of Visual Studio that contains a number of enhancements and improvements over prior versions.  While I won’t get into a full feature breakdown (see my links to Microsoft blogs below for what’s new), there are a few specific areas that I’d like to touch on that I believe will help developers make the most of their AMD hardware platforms – across APU, CPU, and GPU.

C++ AMP

C++ AMP is new to Visual Studio and helps enable easy development of data parallel programs which are able to take advantage of underlying APU and GPU hardware that support DirectX 11.  C++ AMP consists of an extension to the C++ language in the form of a new keyword (restrict), infrastructure plumbing, and libraries.  By executing data parallel code directly on the APU/GPU – such as on an AMD A-Series APU or AMD Radeon™ HD 7970 GPU – performance and power savings are possible over code executing on the CPU alone (even SSE vectorized code).  The tight integration of C++ AMP as a C++ language extension and relative ease of use are key benefits that will help drive widespread adoption of heterogeneous computing and lower the barrier of entry for data-parallel computation.

Support for new instructions

Visual Studio 11 includes a number of new intrinsics to support AMD’s processors, including the upcoming 2nd generation APU codenamed “Trinity”.  The processor core in “Trinity” has new instructions for three-operand FMA, also known as FMA3, as well as instructions for bit manipulation (BMI and TBM) and half-float conversion (F16C), all of which are supported via C++ intrinsics in Visual Studio 11.  For more information on the new instructions, see the AMD Software Optimization Guide located here.

Auto-vectorization

Also new to C++ in Visual Studio 11 is an auto-vectorizer, which is on by default.  The compiler will vectorize loops where possible to improve performance using vector instructions on the processor (such as SSE2 and SSE4.x).  Take the following code snippet example:

float A[1000], B[1000], C[1000];

for (i = 0; i < 1000; i++) {

    A[i] = B[i] + C[i];

}

The C++ compiler can vectorize this loop in order to execute multiple iterations simultaneously, improving performance significantly with instructions available on modern processors.

In addition to the vectorizer, the auto-parallelizer will execute loops across multiple CPU processors in the system, getting better effective utilization out of the underlying hardware.  The parallelizer requires input from the programmer to indicate those loops that should be parallelized, and can also be used in conjunction with the auto-vectorizer.

Finally, the Visual C++ compiler includes targeted code generation improvements to help improve the overall performance of applications that are built with it.  For more on specific C++ improvements in Visual Studio 11, check out Diego Dagum’s blog.

Support for Windows 8 Metro-style applications

Of course, one of the significant highlights of Visual Studio 11 is support for Metro-style applications and WinRT.  With WinRT, developers can use C++, JavaScript, and managed languages (such as C# and VB) to build new Metro-style applications for Windows 8.  Metro-style applications are hardware accelerated and use the APU or GPU for rendering to enable a smooth user experience.  C++ AMP can also be used in a Metro-style application for even more performance benefits!

In short, Visual Studio 11 has a number of great features to get the most out of the underlying hardware.  This spans AMD’s product line – from APU to CPU to GPU.  We’re excited to see what kind of great new applications developers will build with Visual Studio 11!  To get started with Visual Studio 11, read about what’s new in Jason Zander’s blog, and download the beta.

Robin Maffeo is a Software Engineering Manager on the Microsoft team at AMD. 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.

Performance Challenge

The performance challenge definitely surprised us with how quickly developers learned how to implement advanced OpenCL™ techniques.  It only took two weeks for them to figure out all of the optimization techniques to help them get the best performance.  The majority of these participants were new to OpenCL technology, this quote from a challenge competitor summed up the typical contestant’s experience,

“Honestly, I am new to OpenCL, except having a look at couple of CUDA programs before and little experience with OpenMP… I thought I could do it. It turned out to be not much difficult.”

-Topcoder Member: Pratap, aka: supercharger

Innovation Challenge

The submissions for this challenge were quite innovative in just about every category I could imagine and more.  People submitted OpenCL algorithms for games, financial modeling, video processing, image processing, artificial intelligence, gesture recognition, simulation, computer vision, robotics, and the list goes on.  Our engineers debated tirelessly over which entry should win and it took a while for us to close on a decision (as it should be, considering how significant the prizes were).

The Innovation Challenge prizes went to:

1. First Place: Went to the designer for an application that could enable the future of a more human like AI for video games.  This app “sees” what a human person would see when playing a first person shooter game, and can track features so as to move around in the game.  The idea is to have a computer competitor that doesn’t have “privileged” information. 
2. Second place:  Went to the designer of an application that used the Microsoft^® Kinect camera along with the AMD APU processor to do real-time video effects.
3. Third place:  Went to the designer of an application that takes adaptive shadow detection to the next level and has it “teach” itself.
4. Fourth place:  Went to the designer of a numerical simulation of an x-ray generator. 

The end result is that we got some amazing apps that took advantage of the very low overhead  between data transfers from the CPU and GPU with the AMD  APU architecture.  But, more importantly it showed how the low power, small form factor, AMD  APU has the power to be used like a personal and portable high performance computer. 

Visit the AMD OpenCL™ Competition webpage to learn more about the winning entries and watch video demos.

Sharon Troia is a Developer Relations Engineer at AMD. Her postings are her 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.

In Auto-Tuning mode, SlotMaximizer attempts many potential optimizations on kernels directed by the developer.  Each of the many optimizations of a given kernel are executed using the actual data being processed by the application, and performance statistics of the optimized kernels processing this data are provided to the developer to select the appropriate version to leverage.

In production code the original kernel is used, and the selected configuration for the preferred optimizations is indicated to the compiler using an attribute that is provided to the developer as part of the Auto-Tuning output data.

SlotMaximizer is already incorporated into the AMD Catalyst™ drivers as a preview and can be used by anyone developing applications using the APP SDK.  It will be turned on by default to support application execution on end-user systems later in the year.

Improvements continue to be made to SlotMaximizer, download the latest beta version from   here.  You will need to register on the Multicoreware web-site, but this will also give you access to report issues, ask questions, etc. using their forums.  The download will install over that included with your AMD Catalyst™ drivers, and includes documentation on use of SlotMaximizer.

Mark Ireton is the Product Manager for Compute Solutions at AMD. 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.

http://developer.amd.com/cpu/codeanalyst/codeanalystlinux

Last quarter, we saw lot of active users suggesting new enhancements, posting queries and bugs. You are helping us to make AMD CodeAnalyst better. Thank you very much for your feedback.

In the AMD CodeAnalyst 3.2 release, we have added support to profile Java inline methods. To profile Java inline methods, AMD CodeAnalyst requires JDK version 1.7 or higher. We have added support for the new Linux distributions RHEL 5 Update 7 and RHEL 6 Update 2.

Multiple bugs are fixed to increase the profiling experience of Java Applications. Incorrect block analysis in Disassembly and Module data views are fixed. Added support for nested java inline functions. Various GUI crashes in Module Data View were fixed.

Up until version 3.1, AMD CodeAnalyst was using Qt version 3.3. In this release we have migrated to Qt version 4.x. This would make us to use the new features of Qt to improve the user experience.

Apart from adding new features, we are also committed to make our product more robust by fixing more bugs. If you have any suggestion to improve the tool or whenever you experience any bug, please let us know, through our forums or comments to this blog.