summaryrefslogtreecommitdiff
path: root/src/itree.c
diff options
context:
space:
mode:
authorMatt Armstrong <matt@rfc20.org>2022-10-10 10:45:05 -0700
committerMatt Armstrong <matt@rfc20.org>2022-10-10 19:37:51 -0700
commitda0387f0fe79f577fae6d5453c758f600e1ae495 (patch)
tree12aad28099e8718644f7d831202df266306f92fd /src/itree.c
parenta154259bfacf7f1406794a952e80a8197b9a83fb (diff)
downloademacs-da0387f0fe79f577fae6d5453c758f600e1ae495.tar.gz
Stop reading and writing the itree_null.parent field entirely.
With this change all fields in the itree_null sentinel are read only. This makes accessing itree_null thread safe in an obvious way. Because it took two commits from two peole to get this right, I think we can call this design fragile and difficult to reason about. Another benefit of this commit is as preparation for removing sentinel node completely, and just using NULL. * src/itree.c (itree_null): Statically initialize itree_null.parent to NULL. It is never accessed. (null_is_sane): Assert parent == NULL. (interval_tree_remove_fix): Remove unecessary assignments to parent from node->parent. These were the last places itree_null.parent were read. (interval_tree_remove): Avoid an assignment to itree_null.parent through min->right->parent. (interval_tree_transplant): Avoid an assignment to itree_null.parent through source->parent.
Diffstat (limited to 'src/itree.c')
-rw-r--r--src/itree.c20
1 files changed, 7 insertions, 13 deletions
diff --git a/src/itree.c b/src/itree.c
index d9f9ec8cd67..9c5d8ce1426 100644
--- a/src/itree.c
+++ b/src/itree.c
@@ -146,7 +146,7 @@ static void interval_tree_insert (struct interval_tree *, struct interval_node *
/* The sentinel node, the null node. */
struct interval_node itree_null = {
- .parent = &itree_null,
+ .parent = NULL, /* never accessed */
.left = &itree_null,
.right = &itree_null,
.begin = PTRDIFF_MIN,
@@ -162,12 +162,8 @@ struct interval_node itree_null = {
static bool
null_is_sane (void)
{
- /* The sentinel node has most of its fields read-only.
-
- FIXME: PARENT is still read/write. It is written to
- ininterval_tree_transplant, and later read. --matt
- */
- /* eassert (itree_null.parent == &itree_null); */
+ /* All sentinel node fields are read-only. */
+ eassert (itree_null.parent == NULL);
eassert (itree_null.left == &itree_null);
eassert (itree_null.right == &itree_null);
eassert (itree_null.begin == PTRDIFF_MIN);
@@ -742,7 +738,6 @@ interval_tree_remove_fix (struct interval_tree *tree,
other->red = false;
parent->red = true;
interval_tree_rotate_left (tree, parent);
- parent = node->parent;
other = parent->right;
}
@@ -761,7 +756,6 @@ interval_tree_remove_fix (struct interval_tree *tree,
other->left->red = false;
other->red = true;
interval_tree_rotate_right (tree, other);
- parent = node->parent;
other = parent->right;
}
other->red = parent->red; /* 4.a */
@@ -781,7 +775,6 @@ interval_tree_remove_fix (struct interval_tree *tree,
other->red = false;
parent->red = true;
interval_tree_rotate_right (tree, parent);
- parent = node->parent;
other = parent->left;
}
@@ -800,7 +793,6 @@ interval_tree_remove_fix (struct interval_tree *tree,
other->right->red = false;
other->red = true;
interval_tree_rotate_left (tree, other);
- parent = node->parent;
other = parent->left;
}
@@ -881,7 +873,8 @@ interval_tree_remove (struct interval_tree *tree, struct interval_node *node)
interval_tree_transplant (tree, min, node);
/* We set min->right->parent after `interval_tree_transplant` so
that calls to `itree_total_offset` don't get stuck in an inf-loop. */
- min->right->parent = min;
+ if (min->right != ITREE_NULL)
+ min->right->parent = min;
interval_tree_update_limit (min);
/* This call "belongs" with the first `interval_tree_transplant`
(of `min_right`, done earlier in the `if`) but we prefer to do it
@@ -1508,7 +1501,8 @@ interval_tree_transplant (struct interval_tree *tree, struct interval_node *sour
else
dest->parent->right = source;
- source->parent = dest->parent;
+ if (source != ITREE_NULL)
+ source->parent = dest->parent;
}