[Open64-devel] r3928 - trunk/osprey/be/opt

2012-05-30 Thread svn
Author: meiye Date: 2012-05-30 19:04:01 -0400 (Wed, 30 May 2012) New Revision: 3928 Modified: trunk/osprey/be/opt/opt_cfg_trans.cxx trunk/osprey/be/opt/opt_proactive.cxx trunk/osprey/be/opt/opt_proactive.h trunk/osprey/be/opt/opt_wn.cxx Log: Cosmetic changes to add trace/dump/assert an

[Open64-devel] r3929 - trunk/osprey/be/opt

2012-05-30 Thread svn
Author: meiye Date: 2012-05-30 19:19:51 -0400 (Wed, 30 May 2012) New Revision: 3929 Modified: trunk/osprey/be/opt/opt_cfg_trans.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/opt/opt_wn.h Log: Re-implement

Re: [Open64-devel] r3928 - trunk/osprey/be/opt

2012-05-30 Thread Sun Chan
Mei, I have a question, why is there need for "compiler generated temps"? What is that? Compiler generated temps should be PREGs that has no "storage" requirements (to me, temps has storage allocation associated) Sun On Wed, May 30, 2012 at 4:04 PM, wrote: > Author: meiye > Date: 2012-05-30 19:0

Re: [Open64-devel] r3928 - trunk/osprey/be/opt

2012-05-30 Thread Ye, Mei
I mean the temps used to store values of intermediate expressions, not PREGs. -Mei From: Sun Chan [mailto:sun.c...@gmail.com] Sent: Wednesday, May 30, 2012 4:50 PM To: open64-devel@lists.sourceforge.net Subject: Re: [Open64-devel] r3928 - trunk/osprey/be/opt Mei, I have a question, why is there