diff options
Diffstat (limited to 'gcc/ada')
| -rw-r--r-- | gcc/ada/exp_ch7.ads | 4 | ||||
| -rw-r--r-- | gcc/ada/gnat_rm.texi | 132 | ||||
| -rw-r--r-- | gcc/ada/gnat_ugn.texi | 256 | ||||
| -rw-r--r-- | gcc/ada/system-mingw.ads | 33 | ||||
| -rw-r--r-- | gcc/ada/types.ads | 5 |
5 files changed, 311 insertions, 119 deletions
diff --git a/gcc/ada/exp_ch7.ads b/gcc/ada/exp_ch7.ads index eb17fe0..125d9ea 100644 --- a/gcc/ada/exp_ch7.ads +++ b/gcc/ada/exp_ch7.ads @@ -115,7 +115,9 @@ package Exp_Ch7 is -- type (Is_Controlled) or a type with controlled components -- (Has_Controlled). With_Attach is an integer expression representing -- the level of attachment, see Attach_To_Final_List's Nb_Link param - -- documentation in s-finimp.ads. + -- documentation in s-finimp.ads. Note: if Typ is Finalize_Storage_Only + -- and the object is at library level, then With_Attach will be ignored, + -- and a zero link level will be passed to Attach_To_Final_List. -- -- This function will generate the appropriate calls to make -- sure that the objects referenced by Ref are adjusted. The generated diff --git a/gcc/ada/gnat_rm.texi b/gcc/ada/gnat_rm.texi index 9baa081..8a2ad45 100644 --- a/gcc/ada/gnat_rm.texi +++ b/gcc/ada/gnat_rm.texi @@ -110,6 +110,7 @@ Implementation Defined Pragmas * Pragma Comment:: * Pragma Common_Object:: * Pragma Compile_Time_Warning:: +* Pragma Complete_Representation:: * Pragma Complex_Representation:: * Pragma Component_Alignment:: * Pragma Convention_Identifier:: @@ -281,6 +282,11 @@ The GNAT Library * Ada.Text_IO.C_Streams (a-tiocst.ads):: * Ada.Wide_Text_IO.C_Streams (a-wtcstr.ads):: * Ada.Wide_Wide_Text_IO.C_Streams (a-ztcstr.ads):: +* GNAT.Altivec (g-altive.ads):: +* GNAT.Altivec.Conversions (g-altcon.ads):: +* GNAT.Altivec.Vector_Operations (g-alveop.ads):: +* GNAT.Altivec.Vector_Types (g-alvety.ads):: +* GNAT.Altivec.Vector_Views (g-alvevi.ads):: * GNAT.Array_Split (g-arrspl.ads):: * GNAT.AWK (g-awk.ads):: * GNAT.Bounded_Buffers (g-boubuf.ads):: @@ -644,6 +650,7 @@ consideration, the use of these pragmas should be minimized. * Pragma Comment:: * Pragma Common_Object:: * Pragma Compile_Time_Warning:: +* Pragma Complete_Representation:: * Pragma Complex_Representation:: * Pragma Component_Alignment:: * Pragma Convention_Identifier:: @@ -1039,6 +1046,25 @@ If these conditions are met, a warning message is generated using the value given as the second argument. This string value may contain embedded ASCII.LF characters to break the message into multiple lines. +@node Pragma Complete_Representation +@unnumberedsec Pragma Complete_Representation +@findex Complete_Representation +@noindent +Syntax: + +@smallexample @c ada +pragma Complete_Representation; +@end smallexample + +@noindent +This pragma must appear immediately within a record representation +clause. Typical placements are before the first component clause +or after the last component clause. The effect is to give an error +message if any component is missing a component clause. This pragma +may be used to ensure that a record representation clause is +complete, and that this invariant is maintained if fields are +added to the record in the future. + @node Pragma Complex_Representation @unnumberedsec Pragma Complex_Representation @findex Complex_Representation @@ -1356,7 +1382,7 @@ See @ref{Interfacing to C++} for related information. Syntax: @smallexample @c ada -pragma Debug (PROCEDURE_CALL_WITHOUT_SEMICOLON); +pragma Debug ([CONDITION, ]PROCEDURE_CALL_WITHOUT_SEMICOLON); PROCEDURE_CALL_WITHOUT_SEMICOLON ::= PROCEDURE_NAME @@ -1364,18 +1390,17 @@ PROCEDURE_CALL_WITHOUT_SEMICOLON ::= @end smallexample @noindent -The argument has the syntactic form of an expression, meeting the -syntactic requirements for pragmas. - -If debug pragmas are not enabled, this pragma has no -effect. If debug pragmas are enabled, the semantics of the pragma is exactly -equivalent to the procedure call statement corresponding to the argument -with a terminating semicolon. Pragmas are permitted in sequences of -declarations, so you can use pragma @code{Debug} to intersperse calls to -debug procedures in the middle of declarations. Debug pragmas can be -enabled either by use of the command line switch @code{-gnata} or by use -of the configuration pragma @code{Debug_Policy}. +The procedure call argument has the syntactic form of an expression, meeting +the syntactic requirements for pragmas. +If debug pragmas are not enabled or if the condition is present and evaluates +to False, this pragma has no effect. If debug pragmas are enabled, the +semantics of the pragma is exactly equivalent to the procedure call statement +corresponding to the argument with a terminating semicolon. Pragmas are +permitted in sequences of declarations, so you can use pragma @code{Debug} to +intersperse calls to debug procedures in the middle of declarations. Debug +pragmas can be enabled either by use of the command line switch @code{-gnata} +or by use of the configuration pragma @code{Debug_Policy}. @node Pragma Debug_Policy @unnumberedsec Pragma Debug_Policy @@ -1393,20 +1418,6 @@ If the argument is @code{IGNORE}, then pragma @code{DEBUG} is ignored. This pragma overrides the effect of the @code{-gnata} switch on the command line. -If debug pragmas are not enabled, this pragma has no -effect. If debug pragmas are enabled, the semantics of the pragma is exactly -equivalent to the procedure call statement corresponding to the argument -with a terminating semicolon. Pragmas are permitted in sequences of -declarations, so you can use pragma @code{Debug} to intersperse calls to -debug procedures in the middle of declarations. Debug pragmas can be -enabled either by use of the command line switch @code{-gnata} or by use -of the configuration pragma @code{Debug_Policy}. - - - - - - @node Pragma Detect_Blocking @unnumberedsec Pragma Detect_Blocking @findex Detect_Blocking @@ -7257,7 +7268,7 @@ See the definition and documentation in file @file{s-maccod.ads}. @end cartouche @noindent Unchecked conversion between types of the same size -and results in an uninterpreted transmission of the bits from one type +results in an uninterpreted transmission of the bits from one type to the other. If the types are of unequal sizes, then in the case of discrete types, a shorter source is first zero or sign extended as necessary, and a shorter target is simply truncated on the left. @@ -7265,7 +7276,10 @@ For all non-discrete types, the source is first copied if necessary to ensure that the alignment requirements of the target are met, then a pointer is constructed to the source value, and the result is obtained by dereferencing this pointer after converting it to be a pointer to the -target type. +target type. Unchecked conversions where the target subtype is an +unconstrained array are not permitted. If the target alignment is +greater than the source alignment, then a copy of the result is +made with appropriate alignment @sp 1 @cartouche @@ -8079,7 +8093,7 @@ of delay expirations for lower priority tasks. @noindent @c SGI info: @ignore -Tasks map to IRIX threads, and the dispatching policy is as defied by +Tasks map to IRIX threads, and the dispatching policy is as defined by the IRIX implementation of threads. @end ignore The policy is the same as that of the underlying threads implementation. @@ -11078,9 +11092,9 @@ streams by mixed language programs. Note though that system level buffering is explictly enabled at elaboration of the standard I/O packages and that can have an impact on mixed language programs, in particular those using I/O before calling the Ada elaboration routine (e.g. adainit). It is recommended to call -the Ada elaboration routine before performing any I/O or when impractical, flush -the common I/O streams and in particular Standard_Output before elaborating the -Ada code. +the Ada elaboration routine before performing any I/O or when impractical, +flush the common I/O streams and in particular Standard_Output before +elaborating the Ada code. @node FORM Strings @section FORM Strings @@ -12154,6 +12168,11 @@ of GNAT, and will generate a warning message. * Ada.Text_IO.C_Streams (a-tiocst.ads):: * Ada.Wide_Text_IO.C_Streams (a-wtcstr.ads):: * Ada.Wide_Wide_Text_IO.C_Streams (a-ztcstr.ads):: +* GNAT.Altivec (g-altive.ads):: +* GNAT.Altivec.Conversions (g-altcon.ads):: +* GNAT.Altivec.Vector_Operations (g-alveop.ads):: +* GNAT.Altivec.Vector_Types (g-alvety.ads):: +* GNAT.Altivec.Vector_Views (g-alvevi.ads):: * GNAT.Array_Split (g-arrspl.ads):: * GNAT.AWK (g-awk.ads):: * GNAT.Bounded_Buffers (g-boubuf.ads):: @@ -12451,6 +12470,55 @@ C streams and @code{Wide_Wide_Text_IO}. The stream identifier can be extracted from a file opened on the Ada side, and an Ada file can be constructed from a stream opened on the C side. +@node GNAT.Altivec (g-altive.ads) +@section @code{GNAT.Altivec} (@file{g-altive.ads}) +@cindex @code{GNAT.Altivec} (@file{g-altive.ads}) +@cindex AltiVec + +@noindent +This is the root package of the GNAT AltiVec binding. It provides +definitions of constants and types common to all the versions of the +binding. + +@node GNAT.Altivec.Conversions (g-altcon.ads) +@section @code{GNAT.Altivec.Conversions} (@file{g-altcon.ads}) +@cindex @code{GNAT.Altivec.Conversions} (@file{g-altcon.ads}) +@cindex AltiVec + +@noindent +This package provides the Vector/View conversion routines. + +@node GNAT.Altivec.Vector_Operations (g-alveop.ads) +@section @code{GNAT.Altivec.Vector_Operations} (@file{g-alveop.ads}) +@cindex @code{GNAT.Altivec.Vector_Operations} (@file{g-alveop.ads}) +@cindex AltiVec + +@noindent +This package exposes the Ada interface to the AltiVec operations on +vector objects. A soft emulation is included by default in the GNAT +library. The hard binding is provided as a separate package. This unit +is common to both bindings. + +@node GNAT.Altivec.Vector_Types (g-alvety.ads) +@section @code{GNAT.Altivec.Vector_Types} (@file{g-alvety.ads}) +@cindex @code{GNAT.Altivec.Vector_Types} (@file{g-alvety.ads}) +@cindex AltiVec + +@noindent +This package exposes the various vector types part of the Ada binding +to AltiVec facilities. + +@node GNAT.Altivec.Vector_Views (g-alvevi.ads) +@section @code{GNAT.Altivec.Vector_Views} (@file{g-alvevi.ads}) +@cindex @code{GNAT.Altivec.Vector_Views} (@file{g-alvevi.ads}) +@cindex AltiVec + +@noindent +This package provides public 'View' data types from/to which private +vector representations can be converted via +GNAT.Altivec.Conversions. This allows convenient access to individual +vector elements and provides a simple way to initialize vector +objects. @node GNAT.Array_Split (g-arrspl.ads) @section @code{GNAT.Array_Split} (@file{g-arrspl.ads}) diff --git a/gcc/ada/gnat_ugn.texi b/gcc/ada/gnat_ugn.texi index 4f4e585..c49473b 100644 --- a/gcc/ada/gnat_ugn.texi +++ b/gcc/ada/gnat_ugn.texi @@ -191,6 +191,7 @@ AdaCore@* * Using the GNU make Utility:: @end ifclear * Memory Management Issues:: +* Stack Related Tools:: * Creating Sample Bodies Using gnatstub:: * Other Utility Programs:: * Running and Debugging Ada Programs:: @@ -272,7 +273,6 @@ Switches for gcc * Validity Checking:: * Style Checking:: * Run-Time Checks:: -* Stack Overflow Checking:: * Using gcc for Syntax Checking:: * Using gcc for Semantic Checking:: * Compiling Different Versions of Ada:: @@ -461,6 +461,12 @@ Memory Management Issues * The gnatmem Tool:: @end ifclear +Stack Related Tools + +* Stack Overflow Checking:: +* Static Stack Usage Analysis:: +* Dynamic Stack Usage Analysis:: + Some Useful Memory Pools The GNAT Debug Pool Facility @@ -784,6 +790,10 @@ allocation and deallocation and helps detect ``memory leaks''. @end ifclear @item +@ref{Stack Related Tools}, describes some useful tools associated to stack. +In particular, dynamic and statick usage measurements. + +@item @ref{Creating Sample Bodies Using gnatstub}, discusses @code{gnatstub}, a utility that generates empty but compilable bodies for library units. @@ -3653,7 +3663,6 @@ compilation units. * Validity Checking:: * Style Checking:: * Run-Time Checks:: -* Stack Overflow Checking:: * Using gcc for Syntax Checking:: * Using gcc for Semantic Checking:: * Compiling Different Versions of Ada:: @@ -5552,7 +5561,7 @@ a single character (however many bytes are needed in the encoding). @emph{Set maximum line length.} If the sequence ^M^MAX_LENGTH=^nnn, where nnn is a decimal number, appears in the string after @option{-gnaty} then the length of lines must not exceed the -given value. +given value. The maximum value that can be specified is 32767. @item ^n^STANDARD_CASING^ @emph{Check casing of entities in Standard.} @@ -5841,62 +5850,6 @@ checks. You may modify them using either @code{Suppress} (to remove checks) or @code{Unsuppress} (to add back suppressed checks) pragmas in the program source. -@node Stack Overflow Checking -@subsection Stack Overflow Checking -@cindex Stack Overflow Checking -@cindex -fstack-check - -@noindent -For most operating systems, @command{gcc} does not perform stack overflow -checking by default. This means that if the main environment task or -some other task exceeds the available stack space, then unpredictable -behavior will occur. - -To activate stack checking, compile all units with the gcc option -@option{-fstack-check}. For example: - -@smallexample -gcc -c -fstack-check package1.adb -@end smallexample - -@noindent -Units compiled with this option will generate extra instructions to check -that any use of the stack (for procedure calls or for declaring local -variables in declare blocks) do not exceed the available stack space. -If the space is exceeded, then a @code{Storage_Error} exception is raised. - -For declared tasks, the stack size is always controlled by the size -given in an applicable @code{Storage_Size} pragma (or is set to -the default size if no pragma is used. - -For the environment task, the stack size depends on -system defaults and is unknown to the compiler. The stack -may even dynamically grow on some systems, precluding the -normal Ada semantics for stack overflow. In the worst case, -unbounded stack usage, causes unbounded stack expansion -resulting in the system running out of virtual memory. - -The stack checking may still work correctly if a fixed -size stack is allocated, but this cannot be guaranteed. -To ensure that a clean exception is signalled for stack -overflow, set the environment variable -@code{GNAT_STACK_LIMIT} to indicate the maximum -stack area that can be used, as in: -@cindex GNAT_STACK_LIMIT - -@smallexample -SET GNAT_STACK_LIMIT 1600 -@end smallexample - -@noindent -The limit is given in kilobytes, so the above declaration would -set the stack limit of the environment task to 1.6 megabytes. -Note that the only purpose of this usage is to limit the amount -of stack used by the environment task. If it is necessary to -increase the amount of stack for the environment task, then this -is an operating systems issue, and must be addressed with the -appropriate operating systems commands. - @node Using gcc for Syntax Checking @subsection Using @command{gcc} for Syntax Checking @table @option @@ -6339,6 +6292,10 @@ integers without any kind of scaling. @item free @var{expr} [storage_pool = @var{xxx}] Shows the storage pool associated with a @code{free} statement. +@item [subtype or type declaration] +Used to list an equivalent declaration for an internally generated +type that is referenced elsewhere in the listing. + @item freeze @var{typename} [@var{actions}] Shows the point at which @var{typename} is frozen, with possible associated actions to be performed at the freeze point. @@ -7124,6 +7081,27 @@ Check only, no generation of binder output file. @cindex @option{^-C^/BIND_FILE=C^} (@command{gnatbind}) Generate binder program in C +@item ^-D^/DEFAULT_SECONDARY_STACK_SIZE=nnnnn^ +@cindex @option{^-D^/DEFAULT_SECONDARY_STACK_SIZE=nnnnn^} (@command{gnatbind}) +This switch can be used to change the default secondary stack size value +to a specified size, where nnnnn is the size in bytes. + +The secondary stack is used to deal with functions that return a variable +sized result, for example a function returning an unconstrained +String. There are two ways in which this secondary stack is allocated. + +For most targets, the secondary stack is allocated as a chain of blocks +in the heap, and in this case the size of the chunk allocated is the minimum +of the default secondary stack size value, +and the actual size needed for the current allocation request. + +For certain targets, notably bare board targets and the VxWorks 653 target, +the secondary stack is allocated by carving off a fixed ratio chunk of the +primary task stack. For such targets, the environment task is special, and +in this case the default value is used to carve out a section of the +environment task stack. + + @item ^-e^/ELABORATION_DEPENDENCIES^ @cindex @option{^-e^/ELABORATION_DEPENDENCIES^} (@command{gnatbind}) Output complete list of elaboration-order dependencies. @@ -10182,10 +10160,12 @@ recognized by @code{GNAT}: External_Name_Casing Float_Representation Initialize_Scalars + Interrupt_State License Locking_Policy Long_Float Normalize_Scalars + Persistent_BSS Polling Profile Profile_Warnings @@ -18657,6 +18637,164 @@ and #3 thanks to the more precise associated backtrace. @end ifclear +@node Stack Related Tools +@chapter Stack Related Tools + +@noindent +This chapter describes some useful tools associated to stack. In +particular, dynamic and static usage measurements. + +@menu +* Stack Overflow Checking:: +* Static Stack Usage Analysis:: +* Dynamic Stack Usage Analysis:: +@end menu + +@node Stack Overflow Checking +@section Stack Overflow Checking +@cindex Stack Overflow Checking +@cindex -fstack-check + +@noindent +For most operating systems, @command{gcc} does not perform stack overflow +checking by default. This means that if the main environment task or +some other task exceeds the available stack space, then unpredictable +behavior will occur. + +To activate stack checking, compile all units with the gcc option +@option{-fstack-check}. For example: + +@smallexample +gcc -c -fstack-check package1.adb +@end smallexample + +@noindent +Units compiled with this option will generate extra instructions to check +that any use of the stack (for procedure calls or for declaring local +variables in declare blocks) do not exceed the available stack space. +If the space is exceeded, then a @code{Storage_Error} exception is raised. + +For declared tasks, the stack size is always controlled by the size +given in an applicable @code{Storage_Size} pragma (or is set to +the default size if no pragma is used. + +For the environment task, the stack size depends on +system defaults and is unknown to the compiler. The stack +may even dynamically grow on some systems, precluding the +normal Ada semantics for stack overflow. In the worst case, +unbounded stack usage, causes unbounded stack expansion +resulting in the system running out of virtual memory. + +The stack checking may still work correctly if a fixed +size stack is allocated, but this cannot be guaranteed. +To ensure that a clean exception is signalled for stack +overflow, set the environment variable +@code{GNAT_STACK_LIMIT} to indicate the maximum +stack area that can be used, as in: +@cindex GNAT_STACK_LIMIT + +@smallexample +SET GNAT_STACK_LIMIT 1600 +@end smallexample + +@noindent +The limit is given in kilobytes, so the above declaration would +set the stack limit of the environment task to 1.6 megabytes. +Note that the only purpose of this usage is to limit the amount +of stack used by the environment task. If it is necessary to +increase the amount of stack for the environment task, then this +is an operating systems issue, and must be addressed with the +appropriate operating systems commands. + +@node Static Stack Usage Analysis +@section Static Stack Usage Analysis +@cindex Static Stack Usage Analysis +@cindex -fstack-usage + +@noindent +Units compiled with -fstack-usage will generate an extra file containing +the maximum amount of stack used on a per-function basis. The filename for +the dump is made by appending +@file{.su} to the AUXNAME. AUXNAME is generated from the name of +the output file, if explicitly specified and it is not an executable, +otherwise it is the basename of the source file. An entry is made up +of three fields: + +@itemize +@item +The name of the function. +@item +A number of bytes. +@item +One or more qualifiers: @code{static}, @code{dynamic}, @code{bounded}. +@end itemize + +The qualifier @code{static} means that the function manipulates the stack +statically: a fixed number of bytes are allocated for the frame on function +entry and released on function exit; no stack adjustments are otherwise made +in the function. The second field is this fixed number of bytes. + +The qualifier @code{dynamic} means that the function manipulates the stack +dynamically: in addition to the static allocation described above, stack +adjustments are made in the body of the function, for example to push/pop +arguments around function calls. If the qualifier @code{bounded} is also +present, the amount of these adjustments is bounded at compile-time and +the second field is an upper bound of the total amount of stack used by +the function. If it is not present, the amount of these adjustments is +not bounded at compile-time and the second field only represents the +bounded part. + +@node Dynamic Stack Usage Analysis +@section Dynamic Stack Usage Analysis + +@noindent +It is possible to measure the maximum amount of stack used by a task, by +adding a switch to @command{gnatbind}, as: + +@smallexample +$ gnatbind -u0 file +@end smallexample + +@noindent +Here, as soon as a task ends, its stack usage will be printed on stderr. It's +also possible to store a certain number of results to display them only at the +end of the execution. The following command will display the 100 first results +at the end of the programm, and others on the fly: + +@smallexample +$ gnatbind -u100 file +@end smallexample + +@noindent +Results are displayed in the folowing format: + +@noindent +INDEX | TASK NAME | STACK SIZE | MAX USAGE + +@noindent +where: + +@table @emph +@item INDEX +is a number associated with each task. Numbers before n parameter given +with -u flag correspond to stored results. + +@item TASK NAME +is the name of the task analyzed. + +@item STACK SIZE +is the maximum size for the stack. In order to prevent overflowed, +this value is a little smaller than the real limit. + +@item MAX USAGE +is the measure done by the stack analyzer. + +@end table + +@noindent +The environment task stack, e.g. the stack that contains the main unit, is +only processed when the environment variable GNAT_STACK_LIMIT is set. + @node Creating Sample Bodies Using gnatstub @chapter Creating Sample Bodies Using @command{gnatstub} @findex gnatstub diff --git a/gcc/ada/system-mingw.ads b/gcc/ada/system-mingw.ads index 5924fc8..24ed0b4 100644 --- a/gcc/ada/system-mingw.ads +++ b/gcc/ada/system-mingw.ads @@ -167,39 +167,22 @@ private pragma Suppress_Initialization (Priorities_Mapping); -- Suppress initialization in case gnat.adc specifies Normalize_Scalars - -- On NT, the default mapping preserves the standard 31 priorities - -- of the Ada model, but maps them using compression onto the 7 - -- priority levels available in NT. - - -- To replace the default values of the Underlying_Priorities mapping, - -- copy this source file into your build directory, edit the file to - -- reflect your desired behavior, and recompile with the command: - - -- $ gcc -c -O3 -gnatpgn system.ads - - -- then recompile the run-time parts that depend on this package: - - -- $ gnatmake -a -gnatn -O3 <your application> - - -- then force rebuilding your application if you need different options: - - -- $ gnatmake -f <your options> <your application> - Underlying_Priorities : constant Priorities_Mapping := - (Priority'First .. 1 => -15, - 2 .. Default_Priority - 2 => -2, - Default_Priority - 1 => -1, - Default_Priority => 0, - Default_Priority + 1 .. 19 => 1, - 20 .. Priority'Last => 2, - Interrupt_Priority => 15); + -- On NT, the default mapping preserves the standard 31 priorities + -- of the Ada model, but maps them using compression onto the 7 + -- priority levels available in NT. + + -- To replace the default values of the Underlying_Priorities mapping, + -- copy this source file into your build directory, edit the file to + -- reflect your desired behavior, and recompile using Makefile.adalib + -- which can be found under the adalib directory of your gnat installation pragma Linker_Options ("-Wl,--stack=0x2000000"); -- This is used to change the default stack (32 MB) size for non tasking diff --git a/gcc/ada/types.ads b/gcc/ada/types.ads index 2367a91..a2a9927 100644 --- a/gcc/ada/types.ads +++ b/gcc/ada/types.ads @@ -172,8 +172,9 @@ package Types is type Column_Number is range 0 .. 32767; for Column_Number'Size use 16; - -- Column number (assume that 2**15 is large enough, see declaration of - -- Hostparm.Max_Line_Length, and also processing for -gnatyM in Stylesw) + -- Column number (assume that 2**15 - 1 is large enough). The range for + -- this type is used to compute Hostparm.Max_Line_Length. See also the + -- processing for -gnatyM in Stylesw). No_Column_Number : constant Column_Number := 0; -- Special value used to indicate no column number |