Mike Vermeulen, AMDMichiel.Vermeulen@amd.com

What and How can the Open64 community collaborate more closely?

| Open64 Developer Forum | August 2010 | |2

What – can the community collaborate more closely? – look for common user requirements.

• Survey of x86 Open64 users

38%

42%

20%

How would you rate the run-time performance of Open64

as compared against your primary compiler?

Open64 is generally fasterOpen64 performs equallyOpen64 is generally slower

24%

54%

23%

How would you compare re-liability of Open64 vs. your

primary compiler?

Open64 is more re-liableOpen64 is equally re-liableOpen64 is less re-liable

| Open64 Developer Forum | August 2010 | |3

What – can the community collaborate more closely? - five areas from user feedback

CompatibilityMessage: what builds w/gcc should build with open64

(1) gcc front end update

Performance

WindowsMessage: Port version

for Windows (2) windows target in

open64.net, consis-tent with design

Linux distrosMessage: We’d like open64 with

debian / ubuntu/fedora (3) Enable builds for Linux dis-

tros

Reliability

Language featuresMessage: Support Fortran 2003/8, OpenMP 3.0, C+

+000x when in other compilers

(4) Collaboration on upgrades

Integration w/tools

Build issues

GPU computingMessage: OpenCL

and other interfaces to enable GPGPU

(5) Collaboration on open64 GPU support

Usability

Documentation

Other

| Open64 Developer Forum | August 2010 | |4

How can the community collaborate more closely?

1. Submit code changes to open64.net

2. Incremental improvements in community processes to support shared development. Pick the next ones…

Design reviews, gatekeepers, check-in policies

Releases (4.2.3 March 2010) and release processes

Roadmaps, planning

Shared builds

Performance and Quality runs off shared builds

Bug management

3. Continue to re-factor code consistent with original design as further changes are made, e.g. #ifdef cleanups