summaryrefslogtreecommitdiffstats
path: root/llvm/lib/System/Unix
diff options
context:
space:
mode:
authorDuncan Sands <baldrick@free.fr>2008-02-04 09:29:17 +0000
committerDuncan Sands <baldrick@free.fr>2008-02-04 09:29:17 +0000
commit354e353220c1aabe340c9c2ffbc155d29e74c48f (patch)
treeea3dabc5c96a6979716efe1d39b6ab96de074f08 /llvm/lib/System/Unix
parente146c0e3fda28afc013523fef4c152cede9f4e41 (diff)
downloadbcm5719-llvm-354e353220c1aabe340c9c2ffbc155d29e74c48f.tar.gz
bcm5719-llvm-354e353220c1aabe340c9c2ffbc155d29e74c48f.zip
I don't see how NodeUpdated can be called with a
ReadyToProcess node - add an assertion to check this. Add an assertion to NodeDeleted that checks that processed/ready nodes are indeed not deleted. It is because they are never deleted that none of the maps can have a deleted node as the source of a mapping. It does however seem to be possible in theory to have a deleted value as the target of a mapping, however this has not yet been spotted in the wild. Still mulling on what to do about this. [The theoretical situation is this: a node A is expanded/promoted/whatever to a newly created node B. Thus A->B is added to a map. When the subtree rooted at B is legalized it is conceivable that B is deleted due to RAUW on a node somewhere above it]. llvm-svn: 46705
Diffstat (limited to 'llvm/lib/System/Unix')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud