Mei, I read through your changes, and did not see any blocking issues.
However, here are some minor comments from Sun Chan and me, for your future
consideration:
1. You may want to add more assertions.
2. I see that you already did some minor reorganization of your code; in
the fut
Michael and Sun,
Thanks for your comments. With regard to (2), I made an attempt to separate
proactive-opt out, please refer to a driver routine "Proactive_Optimizer" in
"opt_main.cxx".
Proactive-opt is based on CFG, so LNO is not a good place for it.
"Proactive_Optimizer" was meant to build
Thanks Mei. Please go ahead with your check-in.
Michael
From: Ye, Mei
Sent: Wednesday, February 01, 2012 11:37 AM
To: Lai, Michael; 'open64-devel@lists.sourceforge.net'
Subject: RE: [Open64-devel] code review (WOPT)
Michael and Sun,
Thanks for your comments. With regard to (2), I made an att
Author: meiye
Date: 2012-02-01 15:15:09 -0500 (Wed, 01 Feb 2012)
New Revision: 3865
Modified:
trunk/osprey/be/opt/opt_bb.cxx
trunk/osprey/be/opt/opt_proactive.cxx
trunk/osprey/be/opt/opt_proactive.h
trunk/osprey/be/opt/opt_wn.cxx
trunk/osprey/be/vho/vho_lower.cxx
trunk/osprey/com
Sun,
I have a new compile-time testing for whole kernel build, this time
we build on a new machine
with
Intel(R) Xeon(R) CPU E5310 @ 1.60GHz, 32190M Memory
Linux pluto 2.6.16.60-0.21-smp #1 SMP Tue May 6 12:41:02 UTC 2008 x86_64
x86_64 x86_64 GNU/Linux
opt build compiler, single
