summaryrefslogtreecommitdiff
path: root/ecomp-c/README
diff options
context:
space:
mode:
authorAndreas Baumann <mail@andreasbaumann.cc>2020-03-03 18:53:27 +0100
committerAndreas Baumann <mail@andreasbaumann.cc>2020-03-03 18:53:27 +0100
commita5f2e4e1539dc31c9aedbe34d447e8730ecae7ac (patch)
tree144e1b2c6ff736812a9008320eac3b98d67afeae /ecomp-c/README
parent99b589de384fe5c64f7baae30f3d56bb985c342f (diff)
downloadcompilertests-a5f2e4e1539dc31c9aedbe34d447e8730ecae7ac.tar.gz
compilertests-a5f2e4e1539dc31c9aedbe34d447e8730ecae7ac.tar.bz2
very primitive detection whether variables are initialized properly
Diffstat (limited to 'ecomp-c/README')
-rw-r--r--ecomp-c/README7
1 files changed, 7 insertions, 0 deletions
diff --git a/ecomp-c/README b/ecomp-c/README
index ab3da67..d317cd4 100644
--- a/ecomp-c/README
+++ b/ecomp-c/README
@@ -83,3 +83,10 @@ type
integer32 : ARRAY[PLATFORM_BITS] OF BIT;
there are henn-and-egg dragons here!
+
+detection of uninitialized variables
+------------------------------------
+
+this might be very hard and heuristical (and the depend on the compiler
+optimization level). Simple flows can be statically analyzed, what
+to do when conditions, loops and complex data structures come into place?