From e275a63c4b69e474704ccb87aa5cc5e0628d2f1c Mon Sep 17 00:00:00 2001 From: Dan Carpenter Date: Tue, 15 Jan 2013 10:35:09 +0300 Subject: [PATCH] equiv: update some comments Signed-off-by: Dan Carpenter --- smatch_equiv.c | 24 +++++------------------- 1 file changed, 5 insertions(+), 19 deletions(-) diff --git a/smatch_equiv.c b/smatch_equiv.c index bfb732f0..e0cad5e2 100644 --- a/smatch_equiv.c +++ b/smatch_equiv.c @@ -1,5 +1,5 @@ /* - * sparse/smatch_constraints.c + * sparse/smatch_equiv.c * * Copyright (C) 2010 Dan Carpenter. * @@ -8,28 +8,14 @@ */ /* - * smatch_constraints.c is for tracking how variables are related + * smatch_equiv.c is for tracking how variables are the same * * if (a == b) { - * if (a > b) { - * if (a != b) { - * - * This is stored in a field in the smatch_extra dinfo. - * - * Normally the way that variables become related is through a - * condition and you say: add_constraint_expr(left, '<', right); - * The other way it can happen is if you have an assignment: - * set_equiv(left, right); - * - * One two variables "a" and "b" are related if then if we find - * that "a" is greater than 0 we need to update "b". + * Or + * x = y; * * When a variable gets modified all the old relationships are - * deleted. remove_contraints(expr); - * - * Also we need an is_true_constraint(left, '<', right) and - * is_false_constraint (left, '<', right). This is used by - * smatch_implied. + * deleted. remove_equiv(expr); * */ -- 2.11.4.GIT