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

 
 

bug #10898: MultiPatch decomposition is too early

Submitter:  Richard Biener <richi>
Submitted:  Wed 03 Nov 2004 10:19:54 PM UTC
 
Category:  Enhancement request Severity:  2 - Minor
Status:  None Assigned to:  None
Open/Closed:  Open
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       No canned response available

 

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 Biener <richi>
Project Administrator

 

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

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

 

 

 

No changes have been made to this item

Back to the top


Powered by Savane 3.9