A branch has been created for the 4.2.4 release. (branches/open64-4.2.4).
After a quick round of testing, the 4.2.4 binary and source packages will
be posted on the open64.net site, hopefully within a few days.
The trunk is now open for active development for the next release. Please
go ahead with
Thank you Jian-Xin and Ravi for the testing reports for IA64 and x86
respectively.
I think we are ready to create a branch for the 4.2.4 release at this point and
open the trunk for development for the next release. Please hold off your
checkins till you see the announcement that this has happened
Hi Suneel,
We tested the SVN rev 3520 on IA-64.
The suites:
Perennial, Modena, Plumhall, GSA, Unicomp, CRI, CPU2000, CPU2006.
The opt flags:
-O0, -O2, -O3, -O3 -ipa
We found a bug #746 and we are fixing it now.
https://bugs.open64.net/show_bug.cgi?id=746
Regards,
Jian-Xin
2011/2/25 Suneel Ja
oticed when compared with 4.2.3 results.
Regards,
--Ravi
From: Prasad KSV [mailto:prasadv...@gmail.com]
Sent: Friday, February 25, 2011 3:39 PM
To: Suneel Jain
Cc: open64-devel
Subject: Re: [Open64-devel] Planning for 4.2.4 Release in March 2011
Hi Suneel,
At AMD, we intend, to pick up one of the
Thanks for the numerous defect fixes that have come in.
I think we are ready to move to the phase of validating the
quality of the trunk with lots of test suites.
Prasad from AMD sent email on Feb 25 listing a number of test
suites he is planning to validate with. I think now is a good time
to do
Hi Suneel,
At AMD, we intend, to pick up one of the newer SVN revision from the trunk
and test
*using the following apps*
blastcblastcpp-2.2.19
charm CLHEP-2.0.3.2
fftw-2.1.5
fftw-3.1.2
Update on the 4.2.4 release planned for end of March 2011:
- We entered stage 2 (bug fixes only) on Feb 1. There have been
a lot of defects fixed since then. I would like to thank everyone
who has checked in defect fixes so far and helped close out many
defects. If there are specific def
In my role as the release manager for the next Open64 compiler release,
I would like to communicate the current plan. This was discussed and
approved in the last meeting of the Open64 Steering Group. There has
been significant new functionality, performance improvements, defect
fixes and infrastruc
