aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@home.osdl.org>2003-08-02 20:46:00 -0700
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-04-07 21:01:01 -0700
commitf02b6adcd05720e8655b8b0fd64f81791e63f987 (patch)
tree11ef0426ec456395fb3af93ffc8166deb10d84f9 /README
parentUpdate copyright notices to reflect the fact that Transmeta (diff)
downloadsparse-f02b6adcd05720e8655b8b0fd64f81791e63f987.tar.gz
sparse-f02b6adcd05720e8655b8b0fd64f81791e63f987.tar.bz2
sparse-f02b6adcd05720e8655b8b0fd64f81791e63f987.zip
Add a note in the readme about the fact that we now do a five-
phase parse: the last phase is the inline function expansion and the tree simplification.
Diffstat (limited to 'README')
-rw-r--r--README3
1 files changed, 2 insertions, 1 deletions
diff --git a/README b/README
index a30ebe0..6b1034b 100644
--- a/README
+++ b/README
@@ -26,13 +26,14 @@ And no, it doesn't use lex and yacc (or flex and bison). In my personal
opinion, the result of using lex/yacc tends to end up just having to
fight the assumptions the tools make.
-The parsing is done in four phases:
+The parsing is done in five phases:
- full-file tokenization
- pre-processing (which can cause another tokenization phase of another
file)
- semantic parsing.
- lazy type evaluation
+ - inline function expansion and tree simplification
Note the "full file" part. Partly for efficiency, but mostly for ease of
use, there are no "partial results". The library completely parses one