Lines Matching refs:example

119 * C Example::			A simple example in C source
120 * Assembly Code::		The simple example at the assembly level
165 @example
170 @end example
200 @example
202 @end example
207 example, @samp{:t10=*2} defines type 10 as a pointer to type 2, but does
311 @example
316 @end example
326 This simple ``hello world'' example demonstrates several of the stab
329 @example
382 @end example
453 Some compilers (for example, GCC2 and SunOS4 @file{/bin/cc}) also
461 For example:
463 @example
468 @end example
627 passed, before any conversions might take place.  For example, if a C
659 The following example shows a stab for a function @code{main} which
664 @example
666 @end example
695 containing scope is specified.  For example, this code:
697 @example
711 @end example
716 @example
720 @end example
884 For example, the following C code:
886 @example
892 @end example
896 @example
901 @end example
918 For example, the following source code:
920 @example
922 @end example
927 @example
933 @end example
937 from the external symbol for the global variable.  In the example above,
967 @example
969 @end example
1029 For example, the source lines:
1031 @example
1035 @end example
1040 @example
1046 @end example
1085 For example, the Fortran declarations
1087 @example
1092 @end example
1096 @example
1100 @end example
1102 In this example, @code{real} is type 6 and type 3 is an integral type
1110 So in the above example, the value of the @code{foo} stab is the address
1133 As a simple example, the code:
1135 @example
1139 @end example
1143 @example
1147 @end example
1158 @example
1162 @end example
1177 @example
1180 @end example
1231 the prologue (for example, the parameter is declared as a @code{float},
1236 has after the prologue.  For example, suppose the following C code
1239 @example
1244 @end example
1249 @example
1252 @end example
1271 has printed because each one has a stab.  For example, in 
1273 @example
1277 @end example
1286 actual type as passed (for example, @code{double} not @code{float} if it
1376 fit within an @code{int}, then they are given normally.  For example:
1378 @example
1381 @end example
1385 @example
1387 @end example
1394 @example
1396 @end example
1406 proper size for these types.  As an example of octal bounds, the string
1410 @example
1413 @end example
1434 @example
1437 @end example
1442 @example
1444 @end example
1452 @example
1454 @end example
1471 integral type from a character type of the same size, for example it
1476 objects stored in larger ones, for example a @code{short} in an
1532 @example
1534 @end example
1552 One is the size of the type.  A builtin type (for example the C types
1563 like AIX dbx or GDB).  For example,
1565 @example
1567 @end example
1571 @example
1573 @end example
1585 Another example is that the interpretation of whether a boolean is true
1594 will see for example separate @code{int} and @code{integer*4} types
1597 defining a new type with a new name.  For example:
1599 @example
1601 @end example
1763 repetitions of @var{type-information}, for example @code{character*3} is
1795 For example, the following C declarations:
1797 @example
1800 @end example
1805 @example
1807 @end example
1810 machines GCC does not use it.  I believe that for the above example it
1866 (for example, if it is a type reference), there does not
1889 array.  In the example below, the range @samp{r1;0;2;} defines an index
1894 For example, the definition:
1896 @example
1898 @end example
1903 @example
1911 @end example
1915 example, an array of 3-byte objects might, if unpacked, have each
1929 @example
1931 @end example
1942 @example
1944 @end example
1994 @example
1996 @end example
2001 @example
2003 @end example
2024 above example), and even though these symbols are visible in the file as
2030 @samp{t} symbol descriptor (the above example fulfills this
2037 The encoding of structures in stabs can be shown with an example.
2048 @example
2057 @end example
2071 @c FIXME: phony line break.  Can probably be fixed by using an example
2073 @example
2077 @end example
2079 In this example, the first two structure elements are previously defined
2105 For example,
2107 @example
2109 @end example
2133 @example
2139 @end example
2154 @c FIXME: phony line break.  Can probably be fixed by using an example
2172 @example
2174 @end example
2206 For example, this variable definition:
2208 @example
2210 @end example
2215 @example
2218 @end example
2246 @example
2254 @end example
2258 by a NUL character.  If the stab lacks a string (for example, it was
2303 @example
2305 @end example
2310 @example
2312 @end example
2318 @example
2320 @end example
2326 @example
2328 @end example
2337 @example
2339 @end example
2344 @example
2346 @end example
2356 @example
2359 @end example
2365 @example
2369 @end example
2379 The following example is for a stab whose value is an address is
2381 example, if the source line
2383 @example
2385 @end example
2390 @example
2398 @end example
2403 @example
2406 @end example
2410 @example
2413 @end example
2447 For example, the C@t{++} code
2449 @example
2451 @end example
2455 @example
2458 @end example
2462 @example
2464 @end example
2470 @c FIXME: Needs example.
2479 For example, if the string for a stab is @samp{foo::bar::baz:t5=*6},
2523 @example
2525 @end example
2538 @example
2544 @end example
2561 In this simple example the field part of the C@t{++} class stab
2593 in C@t{++} name mangling.  In this example an @code{int} and a @code{char}
2633 @example
2637 @end example
2647 @example
2649 @end example
2657 @example
2663 @end example
2682 @example
2687 @end example
2697 @example
2703 @end example
2710 @example
2715 @end example
2772 functions were publicly accessible.  The example that follows
2790 @example
2799 @end example
2804 @example
2807 @end example
2821 @example
2830 @end example
2858 In the class example described above all the methods have the normal
2865 @example
2872 @end example
2887 @example
2890 @end example
2902 @example
2908 @end example
2919 type reference to the class it is part of.  In this example the type
2974 @example
2977 @end example
3017 @example
3044 @end example
3049 @c FIXME!!! the linebreaks in the following example probably make the
3094 rule is for virtual inheritance.  In the example above, class @code{D}
3109 Since the type id for @code{B} in this example is 25, the vbase pointer name
3125 @example
3127 @end example
3651 @c FIXME: This appendix should go away; see N_PSYM or N_SO for an example.
3696 @example
3699 @end example
3741 @example
3746 @end example
3858 @example
3864 @end example
4018 there should be, see below).  For an example of how these symbols work,
4043 in the stabs (for example, if the file name is @file{../../gdb/main.c},