bugFreePOOMA - Bugs: bug #10898, MultiPatch decomposition is too...

 
 

bug #10898: MultiPatch decomposition is too early

Submitted by:  Richard Guenther <richi>
Submitted on:  Wed 03 Nov 2004 10:19:54 PM UTC  
 
Category: Enhancement requestSeverity: 2 - Minor
Status: NoneAssigned to: None
Open/Closed: Open

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Wed 03 Nov 2004 10:19:54 PM UTC, original submission:

The decomposition of expressions into per-patch iterates is too early. We loose possibilties to easily optimize internal and external guard updating scheme, like re-scheduling of the guard updating or computing the guards themselves.

Solution:
- do a two-level data-flow analysis and scheduling:
1. on the expression level schedule optimizing for
avoiding communication and minimizing latency
(partial internal guard updating). This is
static scheduling.
2. on the patch level schedule optimizing for cache
locality and (dynamically) for latency. This is
partly static (cache locality) and dynamic (latency)
scheduling.

Richard Guenther <richi>
Project Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

No Changes Have Been Made to This Item

Back to the top


Powered by Savane 3.1-cleanup