-CIL Limitations -

From 93d89c2b5e8497365be152fb53cb6cd4c5764d34 Mon Sep 17 00:00:00 2001 From: xleroy Date: Wed, 3 Mar 2010 10:25:25 +0000 Subject: Getting rid of CIL git-svn-id: https://yquem.inria.fr/compcert/svn/compcert/trunk@1270 fca1b0fc-160b-0410-b1d3-a4f43f01ea2e --- cil/doc/cil011.html | 53 ----------------------------------------------------- 1 file changed, 53 deletions(-) delete mode 100644 cil/doc/cil011.html (limited to 'cil/doc/cil011.html') diff --git a/cil/doc/cil011.html b/cil/doc/cil011.html deleted file mode 100644 index 975c8dd8..00000000 --- a/cil/doc/cil011.html +++ /dev/null @@ -1,53 +0,0 @@ - - - - - - - - - - - - - -CIL Limitations - - - -

- -

11 CIL Limitations

-There are several implementation details of CIL that might make it unusable - or less than ideal for certain tasks: -

-CIL operates after preprocessing. If you need to see comments, for -example, you cannot use CIL. But you can use attributes and pragmas instead. -And there is some support to help you patch the include files before they are -seen by the preprocessor. For example, this is how we turn some -#defines that we don't like into function calls.
-
-
CIL does transform the code in a non-trivial way. This is done in order -to make most analyses easier. But if you want to see the code e1, e2++ -exactly as it appears in the code, then you should not use CIL.
-
-
CIL removes all local scopes and moves all variables to function -scope. It also separates a declaration with an initializer into a declaration -plus an assignment. The unfortunate effect of this transformation is that -local variables cannot have the const qualifier.

- - -- cgit