Hi All,
The problem of using -OPT:alias=nystrom is
1. Nystrom is not intuitive for open64 user to know what this alias option
really means.
It's not a common alias terminology.
What is this alias analysis's capabitlity?
If used in CPU2006 SPEC report later, it's not clear and may be treated
as a hack option.
2. It use Nystrom's last name without his permission?
-OPT:alias=xxx is designed for implement different alias analysis algorithm
using same Alias_Analyzer interface.
Till now Nystrom_Alias_Analyzer is the only implementation.
Plan is use a more meaningful name for this alias analyzer.
Nystrom is designed to be field_sensitive, inclusion based and context
sensitive.
Now its major different with default alias is field_sensitive, inclusion
based and heap sensitive.
In order to let new alias be clearer to open64 user, new alias need use a
more intuitive name.
I plan to use -OPT:alias=field_sensitive to indicate using new alias.
This is common alias terminology and illustrate important feature of new
alias.
The only change is option name, internal data sturcut and class name doesn't
chagne.
Any comments are welcome!
Thanks in advance.
Regards
Shi Hui
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Open64-devel mailing list
Open64-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open64-devel
