From 99597067357dc1275845cf1cbd3e7e8bd242a7f3 Mon Sep 17 00:00:00 2001 From: Nick Lewycky Date: Mon, 3 Jan 2011 06:16:07 +0000 Subject: Further expand what a call graph pass may do. The rationale is that after analyzing a function in the SCC, we may want to modify it in a way that requires us to update its uses (f.e. to replace the call with a constant) or its users (f.e. to call it with fewer arguments). git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@122739 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/WritingAnLLVMPass.html | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) (limited to 'docs') diff --git a/docs/WritingAnLLVMPass.html b/docs/WritingAnLLVMPass.html index 357b585b51..10668b365f 100644 --- a/docs/WritingAnLLVMPass.html +++ b/docs/WritingAnLLVMPass.html @@ -559,11 +559,9 @@ href="#BasicBlockPass">BasicBlockPass, you should derive from
    -
  1. ... not allowed to modify any Functions that are not in -the current SCC.
  2. - -
  3. ... not allowed to inspect any Functions other than those -in the current SCC and the direct callers and direct callees of the SCC.
  4. +
  5. ... not allowed to inspect or modify any Functions other +than those in the current SCC and the direct callers and direct callees of the +SCC.
  6. ... required to preserve the current CallGraph object, updating it to reflect any changes made to the program.
  7. -- cgit v1.2.3