bugFreePOOMA - Bugs: bug #10897, Don't handle up-to-date-ness of...


bug #10897: Don't handle up-to-date-ness of internal/external guards differently

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

Add a New Comment Rich Markup

Wed 03 Nov 2004 10:15:43 PM UTC, original submission:  

The way external guards are updated (for Fields only!) sucks.  Using relations for this is the wrong way.  It does not permit optimizing the updates as we can with the internal guards.

  - Unify dirty handling of internal/external guards. For this
    to work we need to move guard dirty handling from the
    MultiPatch engine down to the Brick (and similar)    engine.
    We get handling of external guards for free, then.
  - We can still use the relation infrastructure to implement
    BCs - just the trigger needs to be elsewhere.  We can
    use a different mechanism to allow BCs for Array, too.

Richard Biener <richi>
Group administrator


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

Attach Files:

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.12