Hello,
> An important missing piece is correction of exported information for
> loop unrolling. As far as I can tell, for loop unrolled by factor N we
> need to clone MEM_ORIG_EXPRs and datarefs for newly-created MEMs, create
> no-dependence DDRs for those pairs, for which original DDR was
> no-d
Hello,
> Testing on tree-vectorizer testsuite and some of the GCC source files
> showed that frequent source of apparent loss of exported information
> were passes that performed basic block reordering or jump threading.
> The verifier asserted that number of loops was constant and the order
> the
(Zdenek, I CC'ed you because I need some clarification regarding your
loop-structures-preserving project; please see below)
Hello,
I'd like to provide an update on the ddg-exporting project and request
some more comments. Ian, thanks for your feedback and for catching
redundant code.
Testing o
Hello Ian,
Tuesday, July 3, 2007, 6:23:02 PM, you wrote:
> Adding a new field to mem_attrs could be a problem. You'll have to
> measure to see how much the memory usage changes.
We have tested that previously with alias-export patch, which uses the
same mechanism for saving original exprs for r
"Alexander Monakov" <[EMAIL PROTECTED]> writes:
> The implementation follows the outline presented in my initial message
> on the project, here: http://gcc.gnu.org/ml/gcc/2007-03/msg00900.html
> . Data references and data dependency relations obtained via
> compute_dependencies_for_loop are copie
Hello,
The attached patch implements (partially) the first part of proposed
work: exporting and verification of data dependence information.
The implementation follows the outline presented in my initial message
on the project, here: http://gcc.gnu.org/ml/gcc/2007-03/msg00900.html
. Data refere
