From 39dcddf827324cf2042b5089c4d53d09626cc00f Mon Sep 17 00:00:00 2001
From: Misha Brukman
-LLVM test suite provides a framework to test optimizer's handling of -debugging information. It can be run like this:
+LLVM test suite provides a +framework to test optimizer's handling of debugging information. It can be run +like this:
@@ -222,8 +222,8 @@ debugging information. It can be run like this:This will test impact of debugging information on optimization passes. If debugging information influences optimization passes then it will be reported -as a failure. See TestingGuide -for more information on LLVM test infratsture and how to run various tests. +as a failure. See TestingGuide +for more information on LLVM test infrastructure and how to run various tests.
The type encoding provides the details of the type. The values are typically -one of the following;
+one of the following:DW_ATE_address = 1 @@ -540,7 +540,7 @@ one of the following;These descriptors are used to define types derived from other types. The value of the tag varies depending on the meaning. The following are possible -tag values;
+tag values:DW_TAG_formal_parameter = 5 @@ -604,7 +604,7 @@ NULL derived type.These descriptors are used to define types that are composed of 0 or more elements. The value of the tag varies depending on the meaning. The following -are possible tag values;
+are possible tag values:DW_TAG_array_type = 1 @@ -721,7 +721,7 @@ value.These descriptors are used to define variables local to a sub program. The -value of the tag depends on the usage of the variable;
+value of the tag depends on the usage of the variable:DW_TAG_auto_variable = 256 @@ -1054,7 +1054,7 @@ debug information that would best describe those constructs.Given the source files "MySource.cpp" and "MyHeader.h" located in the -directory "/Users/mine/sources", the following code;
+directory "/Users/mine/sources", the following code:#include "MyHeader.h" @@ -1064,7 +1064,7 @@ int main(int argc, char *argv[]) { }-a C/C++ front-end would generate the following descriptors;
+a C/C++ front-end would generate the following descriptors:
... @@ -1125,13 +1125,13 @@ int main(int argc, char *argv[]) {-Given an integer global variable declared as follows;
+Given an integer global variable declared as follows:
int MyGlobal = 100;-a C/C++ front-end would generate the following descriptors;
+a C/C++ front-end would generate the following descriptors:
;; @@ -1205,7 +1205,7 @@ int MyGlobal = 100;-Given a function declared as follows;
+Given a function declared as follows:
int main(int argc, char *argv[]) { @@ -1213,7 +1213,7 @@ int main(int argc, char *argv[]) { }-a C/C++ front-end would generate the following descriptors;
+a C/C++ front-end would generate the following descriptors:
;; @@ -1270,7 +1270,7 @@ int %main(int %argc, sbyte** %argv) {-@@ -1534,13 +1534,13 @@ int %main(int %argc, sbyte** %argv) {The following are the basic type descriptors for C/C++ core types;
+The following are the basic type descriptors for C/C++ core types:
-Given the following as an example of C/C++ derived type;
+Given the following as an example of C/C++ derived type:
typedef const int *IntPtr;-a C/C++ front-end would generate the following descriptors;
+a C/C++ front-end would generate the following descriptors:
;; @@ -1611,7 +1611,7 @@ typedef const int *IntPtr;-Given the following as an example of C/C++ struct type;
+Given the following as an example of C/C++ struct type:
struct Color { @@ -1621,7 +1621,7 @@ struct Color { };-a C/C++ front-end would generate the following descriptors;
+a C/C++ front-end would generate the following descriptors:
;; @@ -1718,7 +1718,7 @@ struct Color {-Given the following as an example of C/C++ enumeration type;
+Given the following as an example of C/C++ enumeration type:
enum Trees { @@ -1728,7 +1728,7 @@ enum Trees { };-a C/C++ front-end would generate the following descriptors;
+a C/C++ front-end would generate the following descriptors:
;;