i386: Update INCOMING_FRAME_SP_OFFSET for exception handler
[official-gcc.git] / gcc / ada / types.ads
blobe0809f27037242c9ebf9b4358c1cdf13d50ff556
1 ------------------------------------------------------------------------------
2 -- --
3 -- GNAT COMPILER COMPONENTS --
4 -- --
5 -- T Y P E S --
6 -- --
7 -- S p e c --
8 -- --
9 -- Copyright (C) 1992-2017, Free Software Foundation, Inc. --
10 -- --
11 -- GNAT is free software; you can redistribute it and/or modify it under --
12 -- terms of the GNU General Public License as published by the Free Soft- --
13 -- ware Foundation; either version 3, or (at your option) any later ver- --
14 -- sion. GNAT is distributed in the hope that it will be useful, but WITH- --
15 -- OUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY --
16 -- or FITNESS FOR A PARTICULAR PURPOSE. --
17 -- --
18 -- As a special exception under Section 7 of GPL version 3, you are granted --
19 -- additional permissions described in the GCC Runtime Library Exception, --
20 -- version 3.1, as published by the Free Software Foundation. --
21 -- --
22 -- You should have received a copy of the GNU General Public License and --
23 -- a copy of the GCC Runtime Library Exception along with this program; --
24 -- see the files COPYING3 and COPYING.RUNTIME respectively. If not, see --
25 -- <http://www.gnu.org/licenses/>. --
26 -- --
27 -- GNAT was originally developed by the GNAT team at New York University. --
28 -- Extensive contributions were provided by Ada Core Technologies Inc. --
29 -- --
30 ------------------------------------------------------------------------------
32 -- This package contains host independent type definitions which are used
33 -- in more than one unit in the compiler. They are gathered here for easy
34 -- reference, although in some cases the full description is found in the
35 -- relevant module which implements the definition. The main reason that they
36 -- are not in their "natural" specs is that this would cause a lot of inter-
37 -- spec dependencies, and in particular some awkward circular dependencies
38 -- would have to be dealt with.
40 -- WARNING: There is a C version of this package. Any changes to this source
41 -- file must be properly reflected in the C header file types.h declarations.
43 -- Note: the declarations in this package reflect an expectation that the host
44 -- machine has an efficient integer base type with a range at least 32 bits
45 -- 2s-complement. If there are any machines for which this is not a correct
46 -- assumption, a significant number of changes will be required.
48 with System;
49 with Unchecked_Conversion;
50 with Unchecked_Deallocation;
52 package Types is
53 pragma Preelaborate;
55 -------------------------------
56 -- General Use Integer Types --
57 -------------------------------
59 type Int is range -2 ** 31 .. +2 ** 31 - 1;
60 -- Signed 32-bit integer
62 subtype Nat is Int range 0 .. Int'Last;
63 -- Non-negative Int values
65 subtype Pos is Int range 1 .. Int'Last;
66 -- Positive Int values
68 type Word is mod 2 ** 32;
69 -- Unsigned 32-bit integer
71 type Short is range -32768 .. +32767;
72 for Short'Size use 16;
73 -- 16-bit signed integer
75 type Byte is mod 2 ** 8;
76 for Byte'Size use 8;
77 -- 8-bit unsigned integer
79 type size_t is mod 2 ** Standard'Address_Size;
80 -- Memory size value, for use in calls to C routines
82 --------------------------------------
83 -- 8-Bit Character and String Types --
84 --------------------------------------
86 -- We use Standard.Character and Standard.String freely, since we are
87 -- compiling ourselves, and we properly implement the required 8-bit
88 -- character code as required in Ada 95. This section defines a few
89 -- general use constants and subtypes.
91 EOF : constant Character := ASCII.SUB;
92 -- The character SUB (16#1A#) is used in DOS and other systems derived
93 -- from DOS (XP, NT etc) to signal the end of a text file. Internally
94 -- all source files are ended by an EOF character, even on Unix systems.
95 -- An EOF character acts as the end of file only as the last character
96 -- of a source buffer, in any other position, it is treated as a blank
97 -- if it appears between tokens, and as an illegal character otherwise.
98 -- This makes life easier dealing with files that originated from DOS,
99 -- including concatenated files with interspersed EOF characters.
101 subtype Graphic_Character is Character range ' ' .. '~';
102 -- Graphic characters, as defined in ARM
104 subtype Line_Terminator is Character range ASCII.LF .. ASCII.CR;
105 -- Line terminator characters (LF, VT, FF, CR). For further details, see
106 -- the extensive discussion of line termination in the Sinput spec.
108 subtype Upper_Half_Character is
109 Character range Character'Val (16#80#) .. Character'Val (16#FF#);
110 -- 8-bit Characters with the upper bit set
112 type Character_Ptr is access all Character;
113 type String_Ptr is access all String;
114 type String_Ptr_Const is access constant String;
115 -- Standard character and string pointers
117 procedure Free is new Unchecked_Deallocation (String, String_Ptr);
118 -- Procedure for freeing dynamically allocated String values
120 subtype Big_String is String (Positive);
121 type Big_String_Ptr is access all Big_String;
122 -- Virtual type for handling imported big strings. Note that we should
123 -- never have any allocators for this type, but we don't give a storage
124 -- size of zero, since there are legitimate deallocations going on.
126 function To_Big_String_Ptr is
127 new Unchecked_Conversion (System.Address, Big_String_Ptr);
128 -- Used to obtain Big_String_Ptr values from external addresses
130 subtype Word_Hex_String is String (1 .. 8);
131 -- Type used to represent Word value as 8 hex digits, with lower case
132 -- letters for the alphabetic cases.
134 function Get_Hex_String (W : Word) return Word_Hex_String;
135 -- Convert word value to 8-character hex string
137 -----------------------------------------
138 -- Types Used for Text Buffer Handling --
139 -----------------------------------------
141 -- We can not use type String for text buffers, since we must use the
142 -- standard 32-bit integer as an index value, since we count on all index
143 -- values being the same size.
145 type Text_Ptr is new Int;
146 -- Type used for subscripts in text buffer
148 type Text_Buffer is array (Text_Ptr range <>) of Character;
149 -- Text buffer used to hold source file or library information file
151 type Text_Buffer_Ptr is access all Text_Buffer;
152 -- Text buffers for input files are allocated dynamically and this type
153 -- is used to reference these text buffers.
155 procedure Free is new Unchecked_Deallocation (Text_Buffer, Text_Buffer_Ptr);
156 -- Procedure for freeing dynamically allocated text buffers
158 ------------------------------------------
159 -- Types Used for Source Input Handling --
160 ------------------------------------------
162 type Logical_Line_Number is range 0 .. Int'Last;
163 for Logical_Line_Number'Size use 32;
164 -- Line number type, used for storing logical line numbers (i.e. line
165 -- numbers that include effects of any Source_Reference pragmas in the
166 -- source file). The value zero indicates a line containing a source
167 -- reference pragma.
169 No_Line_Number : constant Logical_Line_Number := 0;
170 -- Special value used to indicate no line number
172 type Physical_Line_Number is range 1 .. Int'Last;
173 for Physical_Line_Number'Size use 32;
174 -- Line number type, used for storing physical line numbers (i.e. line
175 -- numbers in the physical file being compiled, unaffected by the presence
176 -- of source reference pragmas).
178 type Column_Number is range 0 .. 32767;
179 for Column_Number'Size use 16;
180 -- Column number (assume that 2**15 - 1 is large enough). The range for
181 -- this type is used to compute Hostparm.Max_Line_Length. See also the
182 -- processing for -gnatyM in Stylesw).
184 No_Column_Number : constant Column_Number := 0;
185 -- Special value used to indicate no column number
187 Source_Align : constant := 2 ** 12;
188 -- Alignment requirement for source buffers (by keeping source buffers
189 -- aligned, we can optimize the implementation of Get_Source_File_Index.
190 -- See this routine in Sinput for details.
192 subtype Source_Buffer is Text_Buffer;
193 -- Type used to store text of a source file. The buffer for the main
194 -- source (the source specified on the command line) has a lower bound
195 -- starting at zero. Subsequent subsidiary sources have lower bounds
196 -- which are one greater than the previous upper bound, rounded up to
197 -- a multiple of Source_Align.
199 type Source_Buffer_Ptr_Var is access all Source_Buffer;
200 type Source_Buffer_Ptr is access constant Source_Buffer;
201 -- Pointer to source buffer. Source_Buffer_Ptr_Var is used for allocation
202 -- and deallocation; Source_Buffer_Ptr is used for all other uses of source
203 -- buffers.
205 function Null_Source_Buffer_Ptr (X : Source_Buffer_Ptr) return Boolean;
206 -- True if X = null
208 function Source_Buffer_Ptr_Equal (X, Y : Source_Buffer_Ptr) return Boolean
209 renames "=";
210 -- Squirrel away the predefined "=", for use in Null_Source_Buffer_Ptr.
211 -- Do not call this elsewhere.
213 function "=" (X, Y : Source_Buffer_Ptr) return Boolean is abstract;
214 -- Make "=" abstract. Note that this makes "/=" abstract as well. This is a
215 -- vestige of the zero-origin array indexing we used to use, where "=" is
216 -- always wrong (including the one in Null_Source_Buffer_Ptr). We keep this
217 -- just because we never need to compare Source_Buffer_Ptrs other than to
218 -- null.
220 subtype Source_Ptr is Text_Ptr;
221 -- Type used to represent a source location, which is a subscript of a
222 -- character in the source buffer. As noted above, different source buffers
223 -- have different ranges, so it is possible to tell from a Source_Ptr value
224 -- which source it refers to. Note that negative numbers are allowed to
225 -- accommodate the following special values.
227 No_Location : constant Source_Ptr := -1;
228 -- Value used to indicate no source position set in a node. A test for a
229 -- Source_Ptr value being > No_Location is the approved way to test for a
230 -- standard value that does not include No_Location or any of the following
231 -- special definitions. One important use of No_Location is to label
232 -- generated nodes that we don't want the debugger to see in normal mode
233 -- (very often we conditionalize so that we set No_Location in normal mode
234 -- and the corresponding source line in -gnatD mode).
236 Standard_Location : constant Source_Ptr := -2;
237 -- Used for all nodes in the representation of package Standard other than
238 -- nodes representing the contents of Standard.ASCII. Note that testing for
239 -- a value being <= Standard_Location tests for both Standard_Location and
240 -- for Standard_ASCII_Location.
242 Standard_ASCII_Location : constant Source_Ptr := -3;
243 -- Used for all nodes in the presentation of package Standard.ASCII
245 System_Location : constant Source_Ptr := -4;
246 -- Used to identify locations of pragmas scanned by Targparm, where we know
247 -- the location is in System, but we don't know exactly what line.
249 First_Source_Ptr : constant Source_Ptr := 0;
250 -- Starting source pointer index value for first source program
252 -------------------------------------
253 -- Range Definitions for Tree Data --
254 -------------------------------------
256 -- The tree has fields that can hold any of the following types:
258 -- Pointers to other tree nodes (type Node_Id)
259 -- List pointers (type List_Id)
260 -- Element list pointers (type Elist_Id)
261 -- Names (type Name_Id)
262 -- Strings (type String_Id)
263 -- Universal integers (type Uint)
264 -- Universal reals (type Ureal)
266 -- These types are represented as integer indices into various tables.
267 -- However, they should be treated as private, except in a few documented
268 -- cases. In particular it is never appropriate to perform arithmetic
269 -- operations using these types.
271 -- In most contexts, the strongly typed interface determines which of these
272 -- types is present. However, there are some situations (involving untyped
273 -- traversals of the tree), where it is convenient to be easily able to
274 -- distinguish these values. The underlying representation in all cases is
275 -- an integer type Union_Id, and we ensure that the range of the various
276 -- possible values for each of the above types is disjoint so that this
277 -- distinction is possible.
279 -- Note: it is also helpful for debugging purposes to make these ranges
280 -- distinct. If a bug leads to misidentification of a value, then it will
281 -- typically result in an out of range value and a Constraint_Error.
283 type Union_Id is new Int;
284 -- The type in the tree for a union of possible ID values
286 List_Low_Bound : constant := -100_000_000;
287 -- The List_Id values are subscripts into an array of list headers which
288 -- has List_Low_Bound as its lower bound. This value is chosen so that all
289 -- List_Id values are negative, and the value zero is in the range of both
290 -- List_Id and Node_Id values (see further description below).
292 List_High_Bound : constant := 0;
293 -- Maximum List_Id subscript value. This allows up to 100 million list Id
294 -- values, which is in practice infinite, and there is no need to check the
295 -- range. The range overlaps the node range by one element (with value
296 -- zero), which is used both for the Empty node, and for indicating no
297 -- list. The fact that the same value is used is convenient because it
298 -- means that the default value of Empty applies to both nodes and lists,
299 -- and also is more efficient to test for.
301 Node_Low_Bound : constant := 0;
302 -- The tree Id values start at zero, because we use zero for Empty (to
303 -- allow a zero test for Empty). Actual tree node subscripts start at 0
304 -- since Empty is a legitimate node value.
306 Node_High_Bound : constant := 099_999_999;
307 -- Maximum number of nodes that can be allocated is 100 million, which
308 -- is in practice infinite, and there is no need to check the range.
310 Elist_Low_Bound : constant := 100_000_000;
311 -- The Elist_Id values are subscripts into an array of elist headers which
312 -- has Elist_Low_Bound as its lower bound.
314 Elist_High_Bound : constant := 199_999_999;
315 -- Maximum Elist_Id subscript value. This allows up to 100 million Elists,
316 -- which is in practice infinite and there is no need to check the range.
318 Elmt_Low_Bound : constant := 200_000_000;
319 -- Low bound of element Id values. The use of these values is internal to
320 -- the Elists package, but the definition of the range is included here
321 -- since it must be disjoint from other Id values. The Elmt_Id values are
322 -- subscripts into an array of list elements which has this as lower bound.
324 Elmt_High_Bound : constant := 299_999_999;
325 -- Upper bound of Elmt_Id values. This allows up to 100 million element
326 -- list members, which is in practice infinite (no range check needed).
328 Names_Low_Bound : constant := 300_000_000;
329 -- Low bound for name Id values
331 Names_High_Bound : constant := 399_999_999;
332 -- Maximum number of names that can be allocated is 100 million, which is
333 -- in practice infinite and there is no need to check the range.
335 Strings_Low_Bound : constant := 400_000_000;
336 -- Low bound for string Id values
338 Strings_High_Bound : constant := 499_999_999;
339 -- Maximum number of strings that can be allocated is 100 million, which
340 -- is in practice infinite and there is no need to check the range.
342 Ureal_Low_Bound : constant := 500_000_000;
343 -- Low bound for Ureal values
345 Ureal_High_Bound : constant := 599_999_999;
346 -- Maximum number of Ureal values stored is 100_000_000 which is in
347 -- practice infinite so that no check is required.
349 Uint_Low_Bound : constant := 600_000_000;
350 -- Low bound for Uint values
352 Uint_Table_Start : constant := 2_000_000_000;
353 -- Location where table entries for universal integers start (see
354 -- Uintp spec for details of the representation of Uint values).
356 Uint_High_Bound : constant := 2_099_999_999;
357 -- The range of Uint values is very large, since a substantial part
358 -- of this range is used to store direct values, see Uintp for details.
360 -- The following subtype definitions are used to provide convenient names
361 -- for membership tests on Int values to see what data type range they
362 -- lie in. Such tests appear only in the lowest level packages.
364 subtype List_Range is Union_Id
365 range List_Low_Bound .. List_High_Bound;
367 subtype Node_Range is Union_Id
368 range Node_Low_Bound .. Node_High_Bound;
370 subtype Elist_Range is Union_Id
371 range Elist_Low_Bound .. Elist_High_Bound;
373 subtype Elmt_Range is Union_Id
374 range Elmt_Low_Bound .. Elmt_High_Bound;
376 subtype Names_Range is Union_Id
377 range Names_Low_Bound .. Names_High_Bound;
379 subtype Strings_Range is Union_Id
380 range Strings_Low_Bound .. Strings_High_Bound;
382 subtype Uint_Range is Union_Id
383 range Uint_Low_Bound .. Uint_High_Bound;
385 subtype Ureal_Range is Union_Id
386 range Ureal_Low_Bound .. Ureal_High_Bound;
388 -----------------------------
389 -- Types for Atree Package --
390 -----------------------------
392 -- Node_Id values are used to identify nodes in the tree. They are
393 -- subscripts into the Nodes table declared in package Atree. Note that
394 -- the special values Empty and Error are subscripts into this table.
395 -- See package Atree for further details.
397 type Node_Id is range Node_Low_Bound .. Node_High_Bound;
398 -- Type used to identify nodes in the tree
400 subtype Entity_Id is Node_Id;
401 -- A synonym for node types, used in the Einfo package to refer to nodes
402 -- that are entities (i.e. nodes with an Nkind of N_Defining_xxx). All such
403 -- nodes are extended nodes and these are the only extended nodes, so that
404 -- in practice entity and extended nodes are synonymous.
406 subtype Node_Or_Entity_Id is Node_Id;
407 -- A synonym for node types, used in cases where a given value may be used
408 -- to represent either a node or an entity. We like to minimize such uses
409 -- for obvious reasons of logical type consistency, but where such uses
410 -- occur, they should be documented by use of this type.
412 Empty : constant Node_Id := Node_Low_Bound;
413 -- Used to indicate null node. A node is actually allocated with this
414 -- Id value, so that Nkind (Empty) = N_Empty. Note that Node_Low_Bound
415 -- is zero, so Empty = No_List = zero.
417 Empty_List_Or_Node : constant := 0;
418 -- This constant is used in situations (e.g. initializing empty fields)
419 -- where the value set will be used to represent either an empty node or
420 -- a non-existent list, depending on the context.
422 Error : constant Node_Id := Node_Low_Bound + 1;
423 -- Used to indicate an error in the source program. A node is actually
424 -- allocated with this Id value, so that Nkind (Error) = N_Error.
426 Empty_Or_Error : constant Node_Id := Error;
427 -- Since Empty and Error are the first two Node_Id values, the test for
428 -- N <= Empty_Or_Error tests to see if N is Empty or Error. This definition
429 -- provides convenient self-documentation for such tests.
431 First_Node_Id : constant Node_Id := Node_Low_Bound;
432 -- Subscript of first allocated node. Note that Empty and Error are both
433 -- allocated nodes, whose Nkind fields can be accessed without error.
435 ------------------------------
436 -- Types for Nlists Package --
437 ------------------------------
439 -- List_Id values are used to identify node lists stored in the tree, so
440 -- that each node can be on at most one such list (see package Nlists for
441 -- further details). Note that the special value Error_List is a subscript
442 -- in this table, but the value No_List is *not* a valid subscript, and any
443 -- attempt to apply list operations to No_List will cause a (detected)
444 -- error.
446 type List_Id is range List_Low_Bound .. List_High_Bound;
447 -- Type used to identify a node list
449 No_List : constant List_Id := List_High_Bound;
450 -- Used to indicate absence of a list. Note that the value is zero, which
451 -- is the same as Empty, which is helpful in initializing nodes where a
452 -- value of zero can represent either an empty node or an empty list.
454 Error_List : constant List_Id := List_Low_Bound;
455 -- Used to indicate that there was an error in the source program in a
456 -- context which would normally require a list. This node appears to be
457 -- an empty list to the list operations (a null list is actually allocated
458 -- which has this Id value).
460 First_List_Id : constant List_Id := Error_List;
461 -- Subscript of first allocated list header
463 ------------------------------
464 -- Types for Elists Package --
465 ------------------------------
467 -- Element list Id values are used to identify element lists stored outside
468 -- of the tree, allowing nodes to be members of more than one such list
469 -- (see package Elists for further details).
471 type Elist_Id is range Elist_Low_Bound .. Elist_High_Bound;
472 -- Type used to identify an element list (Elist header table subscript)
474 No_Elist : constant Elist_Id := Elist_Low_Bound;
475 -- Used to indicate absence of an element list. Note that this is not an
476 -- actual Elist header, so element list operations on this value are not
477 -- valid.
479 First_Elist_Id : constant Elist_Id := No_Elist + 1;
480 -- Subscript of first allocated Elist header
482 -- Element Id values are used to identify individual elements of an element
483 -- list (see package Elists for further details).
485 type Elmt_Id is range Elmt_Low_Bound .. Elmt_High_Bound;
486 -- Type used to identify an element list
488 No_Elmt : constant Elmt_Id := Elmt_Low_Bound;
489 -- Used to represent empty element
491 First_Elmt_Id : constant Elmt_Id := No_Elmt + 1;
492 -- Subscript of first allocated Elmt table entry
494 -------------------------------
495 -- Types for Stringt Package --
496 -------------------------------
498 -- String_Id values are used to identify entries in the strings table. They
499 -- are subscripts into the Strings table defined in package Stringt.
501 type String_Id is range Strings_Low_Bound .. Strings_High_Bound;
502 -- Type used to identify entries in the strings table
504 No_String : constant String_Id := Strings_Low_Bound;
505 -- Used to indicate missing string Id. Note that the value zero is used
506 -- to indicate a missing data value for all the Int types in this section.
508 First_String_Id : constant String_Id := No_String + 1;
509 -- First subscript allocated in string table
511 -------------------------
512 -- Character Code Type --
513 -------------------------
515 -- The type Char is used for character data internally in the compiler, but
516 -- character codes in the source are represented by the Char_Code type.
517 -- Each character literal in the source is interpreted as being one of the
518 -- 16#7FFF_FFFF# possible Wide_Wide_Character codes, and a unique Integer
519 -- value is assigned, corresponding to the UTF-32 value, which also
520 -- corresponds to the Pos value in the Wide_Wide_Character type, and also
521 -- corresponds to the Pos value in the Wide_Character and Character types
522 -- for values that are in appropriate range. String literals are similarly
523 -- interpreted as a sequence of such codes.
525 type Char_Code_Base is mod 2 ** 32;
526 for Char_Code_Base'Size use 32;
528 subtype Char_Code is Char_Code_Base range 0 .. 16#7FFF_FFFF#;
529 for Char_Code'Value_Size use 32;
530 for Char_Code'Object_Size use 32;
532 function Get_Char_Code (C : Character) return Char_Code;
533 pragma Inline (Get_Char_Code);
534 -- Function to obtain internal character code from source character. For
535 -- the moment, the internal character code is simply the Pos value of the
536 -- input source character, but we provide this interface for possible
537 -- later support of alternative character sets.
539 function In_Character_Range (C : Char_Code) return Boolean;
540 pragma Inline (In_Character_Range);
541 -- Determines if the given character code is in range of type Character,
542 -- and if so, returns True. If not, returns False.
544 function In_Wide_Character_Range (C : Char_Code) return Boolean;
545 pragma Inline (In_Wide_Character_Range);
546 -- Determines if the given character code is in range of the type
547 -- Wide_Character, and if so, returns True. If not, returns False.
549 function Get_Character (C : Char_Code) return Character;
550 pragma Inline (Get_Character);
551 -- For a character C that is in Character range (see above function), this
552 -- function returns the corresponding Character value. It is an error to
553 -- call Get_Character if C is not in Character range.
555 function Get_Wide_Character (C : Char_Code) return Wide_Character;
556 -- For a character C that is in Wide_Character range (see above function),
557 -- this function returns the corresponding Wide_Character value. It is an
558 -- error to call Get_Wide_Character if C is not in Wide_Character range.
560 ---------------------------------------
561 -- Types used for Library Management --
562 ---------------------------------------
564 type Unit_Number_Type is new Int range -1 .. Int'Last;
565 -- Unit number. The main source is unit 0, and subsidiary sources have
566 -- non-zero numbers starting with 1. Unit numbers are used to index the
567 -- Units table in package Lib.
569 Main_Unit : constant Unit_Number_Type := 0;
570 -- Unit number value for main unit
572 No_Unit : constant Unit_Number_Type := -1;
573 -- Special value used to signal no unit
575 type Source_File_Index is new Int range 0 .. Int'Last;
576 -- Type used to index the source file table (see package Sinput)
578 No_Source_File : constant Source_File_Index := 0;
579 -- Value used to indicate no source file present
581 -----------------------------------
582 -- Representation of Time Stamps --
583 -----------------------------------
585 -- All compiled units are marked with a time stamp which is derived from
586 -- the source file (we assume that the host system has the concept of a
587 -- file time stamp which is modified when a file is modified). These
588 -- time stamps are used to ensure consistency of the set of units that
589 -- constitutes a library. Time stamps are 14-character strings with
590 -- with the following format:
592 -- YYYYMMDDHHMMSS
594 -- YYYY year
595 -- MM month (2 digits 01-12)
596 -- DD day (2 digits 01-31)
597 -- HH hour (2 digits 00-23)
598 -- MM minutes (2 digits 00-59)
599 -- SS seconds (2 digits 00-59)
601 -- In the case of Unix systems (and other systems which keep the time in
602 -- GMT), the time stamp is the GMT time of the file, not the local time.
603 -- This solves problems in using libraries across networks with clients
604 -- spread across multiple time-zones.
606 Time_Stamp_Length : constant := 14;
607 -- Length of time stamp value
609 subtype Time_Stamp_Index is Natural range 1 .. Time_Stamp_Length;
610 type Time_Stamp_Type is new String (Time_Stamp_Index);
611 -- Type used to represent time stamp
613 Empty_Time_Stamp : constant Time_Stamp_Type := (others => ' ');
614 -- Value representing an empty or missing time stamp. Looks less than any
615 -- real time stamp if two time stamps are compared. Note that although this
616 -- is not private, clients should not rely on the exact way in which this
617 -- string is represented, and instead should use the subprograms below.
619 Dummy_Time_Stamp : constant Time_Stamp_Type := (others => '0');
620 -- This is used for dummy time stamp values used in the D lines for
621 -- non-existent files, and is intended to be an impossible value.
623 function "=" (Left, Right : Time_Stamp_Type) return Boolean;
624 function "<=" (Left, Right : Time_Stamp_Type) return Boolean;
625 function ">=" (Left, Right : Time_Stamp_Type) return Boolean;
626 function "<" (Left, Right : Time_Stamp_Type) return Boolean;
627 function ">" (Left, Right : Time_Stamp_Type) return Boolean;
628 -- Comparison functions on time stamps. Note that two time stamps are
629 -- defined as being equal if they have the same day/month/year and the
630 -- hour/minutes/seconds values are within 2 seconds of one another. This
631 -- deals with rounding effects in library file time stamps caused by
632 -- copying operations during installation. We have particularly noticed
633 -- that WinNT seems susceptible to such changes.
635 -- Note: the Empty_Time_Stamp value looks equal to itself, and less than
636 -- any non-empty time stamp value.
638 procedure Split_Time_Stamp
639 (TS : Time_Stamp_Type;
640 Year : out Nat;
641 Month : out Nat;
642 Day : out Nat;
643 Hour : out Nat;
644 Minutes : out Nat;
645 Seconds : out Nat);
646 -- Given a time stamp, decompose it into its components
648 procedure Make_Time_Stamp
649 (Year : Nat;
650 Month : Nat;
651 Day : Nat;
652 Hour : Nat;
653 Minutes : Nat;
654 Seconds : Nat;
655 TS : out Time_Stamp_Type);
656 -- Given the components of a time stamp, initialize the value
658 -------------------------------------
659 -- Types used for Check Management --
660 -------------------------------------
662 type Check_Id is new Nat;
663 -- Type used to represent a check id
665 No_Check_Id : constant := 0;
666 -- Check_Id value used to indicate no check
668 Access_Check : constant := 1;
669 Accessibility_Check : constant := 2;
670 Alignment_Check : constant := 3;
671 Allocation_Check : constant := 4;
672 Atomic_Synchronization : constant := 5;
673 Discriminant_Check : constant := 6;
674 Division_Check : constant := 7;
675 Duplicated_Tag_Check : constant := 8;
676 Elaboration_Check : constant := 9;
677 Index_Check : constant := 10;
678 Length_Check : constant := 11;
679 Overflow_Check : constant := 12;
680 Predicate_Check : constant := 13;
681 Range_Check : constant := 14;
682 Storage_Check : constant := 15;
683 Tag_Check : constant := 16;
684 Validity_Check : constant := 17;
685 Container_Checks : constant := 18;
686 Tampering_Check : constant := 19;
687 -- Values used to represent individual predefined checks (including the
688 -- setting of Atomic_Synchronization, which is implemented internally using
689 -- a "check" whose name is Atomic_Synchronization).
691 All_Checks : constant := 20;
692 -- Value used to represent All_Checks value
694 subtype Predefined_Check_Id is Check_Id range 1 .. All_Checks;
695 -- Subtype for predefined checks, including All_Checks
697 -- The following array contains an entry for each recognized check name
698 -- for pragma Suppress. It is used to represent current settings of scope
699 -- based suppress actions from pragma Suppress or command line settings.
701 -- Note: when Suppress_Array (All_Checks) is True, then generally all other
702 -- specific check entries are set True, except for the Elaboration_Check
703 -- entry which is set only if an explicit Suppress for this check is given.
704 -- The reason for this non-uniformity is that we do not want All_Checks to
705 -- suppress elaboration checking when using the static elaboration model.
706 -- We recognize only an explicit suppress of Elaboration_Check as a signal
707 -- that the static elaboration checking should skip a compile time check.
709 type Suppress_Array is array (Predefined_Check_Id) of Boolean;
710 pragma Pack (Suppress_Array);
712 -- To add a new check type to GNAT, the following steps are required:
714 -- 1. Add an entry to Snames spec for the new name
715 -- 2. Add an entry to the definition of Check_Id above
716 -- 3. Add a new function to Checks to handle the new check test
717 -- 4. Add a new Do_xxx_Check flag to Sinfo (if required)
718 -- 5. Add appropriate checks for the new test
720 -- The following provides precise details on the mode used to generate
721 -- code for intermediate operations in expressions for signed integer
722 -- arithmetic (and how to generate overflow checks if enabled). Note
723 -- that this only affects handling of intermediate results. The final
724 -- result must always fit within the target range, and if overflow
725 -- checking is enabled, the check on the final result is against this
726 -- target range.
728 type Overflow_Mode_Type is (
729 Not_Set,
730 -- Dummy value used during initialization process to show that the
731 -- corresponding value has not yet been initialized.
733 Strict,
734 -- Operations are done in the base type of the subexpression. If
735 -- overflow checks are enabled, then the check is against the range
736 -- of this base type.
738 Minimized,
739 -- Where appropriate, intermediate arithmetic operations are performed
740 -- with an extended range, using Long_Long_Integer if necessary. If
741 -- overflow checking is enabled, then the check is against the range
742 -- of Long_Long_Integer.
744 Eliminated);
745 -- In this mode arbitrary precision arithmetic is used as needed to
746 -- ensure that it is impossible for intermediate arithmetic to cause an
747 -- overflow. In this mode, intermediate expressions are not affected by
748 -- the overflow checking mode, since overflows are eliminated.
750 subtype Minimized_Or_Eliminated is
751 Overflow_Mode_Type range Minimized .. Eliminated;
752 -- Define subtype so that clients don't need to know ordering. Note that
753 -- Overflow_Mode_Type is not marked as an ordered enumeration type.
755 -- The following structure captures the state of check suppression or
756 -- activation at a particular point in the program execution.
758 type Suppress_Record is record
759 Suppress : Suppress_Array;
760 -- Indicates suppression status of each possible check
762 Overflow_Mode_General : Overflow_Mode_Type;
763 -- This field indicates the mode for handling code generation and
764 -- overflow checking (if enabled) for intermediate expression values.
765 -- This applies to general expressions outside assertions.
767 Overflow_Mode_Assertions : Overflow_Mode_Type;
768 -- This field indicates the mode for handling code generation and
769 -- overflow checking (if enabled) for intermediate expression values.
770 -- This applies to any expression occuring inside assertions.
771 end record;
773 -----------------------------------
774 -- Global Exception Declarations --
775 -----------------------------------
777 -- This section contains declarations of exceptions that are used
778 -- throughout the compiler or in other GNAT tools.
780 Unrecoverable_Error : exception;
781 -- This exception is raised to immediately terminate the compilation of the
782 -- current source program. Used in situations where things are bad enough
783 -- that it doesn't seem worth continuing (e.g. max errors reached, or a
784 -- required file is not found). Also raised when the compiler finds itself
785 -- in trouble after an error (see Comperr).
787 Terminate_Program : exception;
788 -- This exception is raised to immediately terminate the tool being
789 -- executed. Each tool where this exception may be raised must have a
790 -- single exception handler that contains only a null statement and that is
791 -- the last statement of the program. If needed, procedure Set_Exit_Status
792 -- is called with the appropriate exit status before raising
793 -- Terminate_Program.
795 ---------------------------------
796 -- Parameter Mechanism Control --
797 ---------------------------------
799 -- Function and parameter entities have a field that records the passing
800 -- mechanism. See specification of Sem_Mech for full details. The following
801 -- subtype is used to represent values of this type:
803 subtype Mechanism_Type is Int range -2 .. Int'Last;
804 -- Type used to represent a mechanism value. This is a subtype rather than
805 -- a type to avoid some annoying processing problems with certain routines
806 -- in Einfo (processing them to create the corresponding C). The values in
807 -- the range -2 .. 0 are used to represent mechanism types declared as
808 -- named constants in the spec of Sem_Mech. Positive values are used for
809 -- the case of a pragma C_Pass_By_Copy that sets a threshold value for the
810 -- mechanism to be used. For example if pragma C_Pass_By_Copy (32) is given
811 -- then Default_C_Record_Mechanism is set to 32, and the meaning is to use
812 -- By_Reference if the size is greater than 32, and By_Copy otherwise.
814 ------------------------------
815 -- Run-Time Exception Codes --
816 ------------------------------
818 -- When the code generator generates a run-time exception, it provides a
819 -- reason code which is one of the following. This reason code is used to
820 -- select the appropriate run-time routine to be called, determining both
821 -- the exception to be raised, and the message text to be added.
823 -- The prefix CE/PE/SE indicates the exception to be raised
824 -- CE = Constraint_Error
825 -- PE = Program_Error
826 -- SE = Storage_Error
828 -- The remaining part of the name indicates the message text to be added,
829 -- where all letters are lower case, and underscores are converted to
830 -- spaces (for example CE_Invalid_Data adds the text "invalid data").
832 -- To add a new code, you need to do the following:
834 -- 1. Assign a new number to the reason. Do not renumber existing codes,
835 -- since this causes compatibility/bootstrap issues, so always add the
836 -- new code at the end of the list.
838 -- 2. Update the contents of the array Kind
840 -- 3. Modify the corresponding definitions in types.h, including the
841 -- definition of last_reason_code.
843 -- 4. Add the name of the routines in exp_ch11.Get_RT_Exception_Name
845 -- 5. Add a new routine in Ada.Exceptions with the appropriate call and
846 -- static string constant. Note that there is more than one version
847 -- of a-except.adb which must be modified.
849 -- Note on ordering of references. For the tables in Ada.Exceptions units,
850 -- usually the ordering does not matter, and we use the same ordering as
851 -- is used here (note the requirement in the ordering here that CE/PE/SE
852 -- codes be kept together, so the subtype declarations work OK).
854 type RT_Exception_Code is
855 (CE_Access_Check_Failed, -- 00
856 CE_Access_Parameter_Is_Null, -- 01
857 CE_Discriminant_Check_Failed, -- 02
858 CE_Divide_By_Zero, -- 03
859 CE_Explicit_Raise, -- 04
860 CE_Index_Check_Failed, -- 05
861 CE_Invalid_Data, -- 06
862 CE_Length_Check_Failed, -- 07
863 CE_Null_Exception_Id, -- 08
864 CE_Null_Not_Allowed, -- 09
866 CE_Overflow_Check_Failed, -- 10
867 CE_Partition_Check_Failed, -- 11
868 CE_Range_Check_Failed, -- 12
869 CE_Tag_Check_Failed, -- 13
870 PE_Access_Before_Elaboration, -- 14
871 PE_Accessibility_Check_Failed, -- 15
872 PE_Address_Of_Intrinsic, -- 16
873 PE_Aliased_Parameters, -- 17
874 PE_All_Guards_Closed, -- 18
875 PE_Bad_Predicated_Generic_Type, -- 19
877 PE_Current_Task_In_Entry_Body, -- 20
878 PE_Duplicated_Entry_Address, -- 21
879 PE_Explicit_Raise, -- 22
880 PE_Finalize_Raised_Exception, -- 23
881 PE_Implicit_Return, -- 24
882 PE_Misaligned_Address_Value, -- 25
883 PE_Missing_Return, -- 26
884 PE_Overlaid_Controlled_Object, -- 27
885 PE_Potentially_Blocking_Operation, -- 28
886 PE_Stubbed_Subprogram_Called, -- 29
888 PE_Unchecked_Union_Restriction, -- 30
889 PE_Non_Transportable_Actual, -- 31
890 SE_Empty_Storage_Pool, -- 32
891 SE_Explicit_Raise, -- 33
892 SE_Infinite_Recursion, -- 34
893 SE_Object_Too_Large, -- 35
894 PE_Stream_Operation_Not_Allowed); -- 36
896 Last_Reason_Code : constant := 36;
897 -- Last reason code
899 type Reason_Kind is (CE_Reason, PE_Reason, SE_Reason);
900 -- Categorization of reason codes by exception raised
902 Rkind : constant array (RT_Exception_Code range <>) of Reason_Kind :=
903 (CE_Access_Check_Failed => CE_Reason,
904 CE_Access_Parameter_Is_Null => CE_Reason,
905 CE_Discriminant_Check_Failed => CE_Reason,
906 CE_Divide_By_Zero => CE_Reason,
907 CE_Explicit_Raise => CE_Reason,
908 CE_Index_Check_Failed => CE_Reason,
909 CE_Invalid_Data => CE_Reason,
910 CE_Length_Check_Failed => CE_Reason,
911 CE_Null_Exception_Id => CE_Reason,
912 CE_Null_Not_Allowed => CE_Reason,
913 CE_Overflow_Check_Failed => CE_Reason,
914 CE_Partition_Check_Failed => CE_Reason,
915 CE_Range_Check_Failed => CE_Reason,
916 CE_Tag_Check_Failed => CE_Reason,
918 PE_Access_Before_Elaboration => PE_Reason,
919 PE_Accessibility_Check_Failed => PE_Reason,
920 PE_Address_Of_Intrinsic => PE_Reason,
921 PE_Aliased_Parameters => PE_Reason,
922 PE_All_Guards_Closed => PE_Reason,
923 PE_Bad_Predicated_Generic_Type => PE_Reason,
924 PE_Current_Task_In_Entry_Body => PE_Reason,
925 PE_Duplicated_Entry_Address => PE_Reason,
926 PE_Explicit_Raise => PE_Reason,
927 PE_Finalize_Raised_Exception => PE_Reason,
928 PE_Implicit_Return => PE_Reason,
929 PE_Misaligned_Address_Value => PE_Reason,
930 PE_Missing_Return => PE_Reason,
931 PE_Overlaid_Controlled_Object => PE_Reason,
932 PE_Potentially_Blocking_Operation => PE_Reason,
933 PE_Stubbed_Subprogram_Called => PE_Reason,
934 PE_Unchecked_Union_Restriction => PE_Reason,
935 PE_Non_Transportable_Actual => PE_Reason,
936 PE_Stream_Operation_Not_Allowed => PE_Reason,
938 SE_Empty_Storage_Pool => SE_Reason,
939 SE_Explicit_Raise => SE_Reason,
940 SE_Infinite_Recursion => SE_Reason,
941 SE_Object_Too_Large => SE_Reason);
943 end Types;