1 ------------------------------------------------------------------------------
3 -- GNAT COMPILER COMPONENTS --
9 -- Copyright (C) 1992-2006, Free Software Foundation, Inc. --
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 2, 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. See the GNU General Public License --
17 -- for more details. You should have received a copy of the GNU General --
18 -- Public License distributed with GNAT; see file COPYING. If not, write --
19 -- to the Free Software Foundation, 51 Franklin Street, Fifth Floor, --
20 -- Boston, MA 02110-1301, USA. --
22 -- As a special exception, if other files instantiate generics from this --
23 -- unit, or you link this unit with other files to produce an executable, --
24 -- this unit does not by itself cause the resulting executable to be --
25 -- covered by the GNU General Public License. This exception does not --
26 -- however invalidate any other reasons why the executable file might be --
27 -- covered by the GNU Public License. --
29 -- GNAT was originally developed by the GNAT team at New York University. --
30 -- Extensive contributions were provided by Ada Core Technologies Inc. --
32 ------------------------------------------------------------------------------
34 -- This package contains routines for accessing and outputting the library
35 -- information. It contains the routine to load subsidiary units.
39 with Types
; use Types
;
43 --------------------------------------------
44 -- General Approach to Library Management --
45 --------------------------------------------
47 -- As described in GNote #1, when a unit is compiled, all its subsidiary
48 -- units are recompiled, including the following:
50 -- (a) Corresponding spec for a body
51 -- (b) Parent spec of a child library spec
53 -- (d) Parent body of a subunit
54 -- (e) Subunits corresponding to any specified stubs
55 -- (f) Bodies of inlined subprograms that are called
56 -- (g) Bodies of generic subprograms or packages that are instantiated
57 -- (h) Bodies of packages containing either of the above two items
58 -- (i) Specs and bodies of runtime units
59 -- (j) Parent specs for with'ed child library units
61 -- If a unit is being compiled only for syntax checking, then no subsidiary
62 -- units are loaded, the syntax check applies only to the main unit,
63 -- i.e. the one contained in the source submitted to the library.
65 -- If a unit is being compiled for syntax and semantic checking, then only
66 -- cases (a)-(d) loads are performed, since the full semantic checking can
67 -- be carried out without needing (e)-(i) loads. In this case no object
68 -- file, or library information file, is generated, so the missing units
69 -- do not affect the results.
71 -- Specifications of library subprograms, subunits, and generic specs
72 -- and bodies, can only be compiled in syntax/semantic checking mode,
73 -- since no code is ever generated directly for these units. In the case
74 -- of subunits, only the compilation of the ultimate parent unit generates
75 -- actual code. If a subunit is submitted to the compiler in syntax/
76 -- semantic checking mode, the parent (or parents in the nested case) are
77 -- semantically checked only up to the point of the corresponding stub.
79 -- If code is being generated, then all the above units are required,
80 -- although the need for bodies of inlined procedures can be suppressed
81 -- by the use of a switch that sets the mode to ignore pragma Inline
84 -- The two main sections of the front end, Par and Sem, are recursive.
85 -- Compilation proceeds unit by unit making recursive calls as necessary.
86 -- The process is controlled from the GNAT main program, which makes calls
87 -- to Par and Sem sequence for the main unit.
89 -- Par parses the given unit, and then, after the parse is complete, uses
90 -- the Par.Load subprogram to load all its subsidiary units in categories
91 -- (a)-(d) above, installing pointers to the loaded units in the parse
92 -- tree, as described in a later section of this spec. If any of these
93 -- required units is missing, a fatal error is signalled, so that no
94 -- attempt is made to run Sem in such cases, since it is assumed that
95 -- too many cascaded errors would result, and the confusion would not
98 -- Following the call to Par on the main unit, the entire tree of required
99 -- units is thus loaded, and Sem is called on the main unit. The parameter
100 -- passed to Sem is the unit to be analyzed. The visibility table, which
101 -- is a single global structure, starts out containing only the entries
102 -- for the visible entities in Standard. Every call to Sem establishes a
103 -- new scope stack table, pushing an entry for Standard on entry to provide
104 -- the proper initial scope environment.
106 -- Sem first proceeds to perform semantic analysis on the currently loaded
109 -- In the case of a body (case (a) above), Sem analyzes the corresponding
110 -- spec, using a recursive call to Sem. As is always expected to be the
111 -- case with calls to Sem, any entities installed in the visibility table
112 -- are removed on exit from Sem, so that these entities have to be
113 -- reinstalled on return to continue the analysis of the body which of
114 -- course needs visibility of these entities.
116 -- In the case of the parent of a child spec (case (b) above), a similar
117 -- call is made to Sem to analyze the parent. Again, on return, the
118 -- entities from the analyzed parent spec have to be installed in the
119 -- visibility table of the caller (the child unit), which must have
120 -- visibility to the entities in its parent spec.
122 -- For with'ed specs (case (c) above), a recursive call to Sem is made
123 -- to analyze each spec in turn. After all the spec's have been analyzed,
124 -- but not till that point, the entities from all the with'ed units are
125 -- reinstalled in the visibility table so that the caller can proceed
126 -- with the analysis of the unit doing the with's with the necessary
127 -- entities made either potentially use visible or visible by selection
130 -- Case (d) arises when Sem is passed a subunit to analyze. This means
131 -- that the main unit is a subunit, and the unit passed to Sem is either
132 -- the main unit, or one of its ancestors that is still a subunit. Since
133 -- analysis must start at the top of the tree, Sem essentially cancels
134 -- the current call by immediately making a call to analyze the parent
135 -- (when this call is finished it immediately returns, so logically this
136 -- call is like a goto). The subunit will then be analyzed at the proper
137 -- time as described for the stub case. Note that we also turn off the
138 -- indication that code should be generated in this case, since the only
139 -- time we generate code for subunits is when compiling the main parent.
141 -- Case (e), subunits corresponding to stubs, are handled as the stubs
142 -- are encountered. There are three sub-cases:
144 -- If the subunit has already been loaded, then this means that the
145 -- main unit was a subunit, and we are back on our way down to it
146 -- after following the initial processing described for case (d).
147 -- In this case we analyze this particular subunit, as described
148 -- for the case where we are generating code, but when we get back
149 -- we are all done, since the rest of the parent is irrelevant. To
150 -- get out of the parent, we raise the exception Subunit_Found, which
151 -- is handled at the outer level of Sem.
153 -- The cases where the subunit has not already been loaded correspond
154 -- to cases where the main unit was a parent. In this case the action
155 -- depends on whether or not we are generating code. If we are not
156 -- generating code, then this is the case where we can simply ignore
157 -- the subunit, since in checking mode we don't even want to insist
158 -- that the subunit exist, much less waste time checking it.
160 -- If we are generating code, then we need to load and analyze
161 -- all subunits. This is achieved with a call to Lib.Load to load
162 -- and parse the unit, followed by processing that installs the
163 -- context clause of the subunit, analyzes the subunit, and then
164 -- removes the context clause (from the visibility chains of the
165 -- parent). Note that we do *not* do a recursive call to Sem in
166 -- this case, precisely because we need to do the analysis of the
167 -- subunit with the current visibility table and scope stack.
169 -- Case (f) applies only to subprograms for which a pragma Inline is
170 -- given, providing that the compiler is operating in the mode where
171 -- pragma Inline's are activated. When the expander encounters a call
172 -- to such a subprogram, it loads the body of the subprogram if it has
173 -- not already been loaded, and calls Sem to process it.
175 -- Case (g) is similar to case (f), except that the body of a generic
176 -- is unconditionally required, regardless of compiler mode settings.
177 -- As in the subprogram case, when the expander encounters a generic
178 -- instantiation, it loads the generic body of the subprogram if it
179 -- has not already been loaded, and calls Sem to process it.
181 -- Case (h) arises when a package contains either an inlined subprogram
182 -- which is called, or a generic which is instantiated. In this case the
183 -- body of the package must be loaded and analyzed with a call to Sem.
185 -- Case (i) is handled by adding implicit with clauses to the context
186 -- clauses of all units that potentially reference the relevant runtime
187 -- entities. Note that since we have the full set of units available,
188 -- the parser can always determine the set of runtime units that is
189 -- needed. These with clauses do not have associated use clauses, so
190 -- all references to the entities must be by selection. Once the with
191 -- clauses have been added, subsequent processing is as for normal
194 -- Case (j) is also handled by adding appropriate implicit with clauses
195 -- to any unit that withs a child unit. Again there is no use clause,
196 -- and subsequent processing proceeds as for an explicit with clause.
198 -- Sem thus completes the loading of all required units, except those
199 -- required for inline subprogram bodies or inlined generics. If any
200 -- of these load attempts fails, then the expander will not be called,
201 -- even if code was to be generated. If the load attempts all succeed
202 -- then the expander is called, though the attempt to generate code may
203 -- still fail if an error occurs during a load attempt for an inlined
204 -- body or a generic body.
206 -------------------------------------------
207 -- Special Handling of Subprogram Bodies --
208 -------------------------------------------
210 -- A subprogram body (in an adb file) may stand for both a spec and a
211 -- body. A simple model (and one that was adopted through version 2.07),
212 -- is simply to assume that such an adb file acts as its own spec if no
213 -- ads file is present.
215 -- However, this is not correct. RM 10.1.4(4) requires that such a body
216 -- act as a spec unless a subprogram declaration of the same name is
217 -- already present. The correct interpretation of this in GNAT library
218 -- terms is to ignore an existing ads file of the same name unless this
219 -- ads file contains a subprogram declaration with the same name.
221 -- If there is an ads file with a unit other than a subprogram declaration
222 -- with the same name, then a fatal message is output, noting that this
223 -- irrelevant file must be deleted before the body can be compiled. See
224 -- ACVC test CA1020D to see how this processing is required.
230 Current_Sem_Unit
: Unit_Number_Type
:= Main_Unit
;
231 -- Unit number of unit currently being analyzed/expanded. This is set when
232 -- ever a new unit is entered, saving and restoring the old value, so that
233 -- it always reflects the unit currently being analyzed. The initial value
234 -- of Main_Unit ensures that a proper value is set initially, and in
235 -- particular for analysis of configuration pragmas in gnat.adc.
237 Main_Unit_Entity
: Entity_Id
;
238 -- Entity of main unit, same as Cunit_Entity (Main_Unit) except where
239 -- Main_Unit is a body with a separate spec, in which case it is the
240 -- entity for the spec.
246 -- The units table has an entry for each unit (source file) read in by the
247 -- current compilation. The table is indexed by the unit number value,
248 -- The first entry in the table, subscript Main_Unit, is for the main file.
249 -- Each entry in this units table contains the following data.
252 -- The name of the source file containing the unit. Set when the entry
253 -- is created by a call to Lib.Load, and then cannot be changed.
256 -- The index in the source file table of the corresponding source file.
257 -- Set when the entry is created by a call to Lib.Load and then cannot
261 -- The index of the unit within the file for multiple unit per file
262 -- mode. Set to zero in normal single unit per file mode.
265 -- This is copied from the Sloc field of the Enode argument passed
266 -- to Load_Unit. It refers to the enclosing construct which caused
267 -- this unit to be loaded, e.g. most typically the with clause that
268 -- referenced the unit, and is used for error handling in Par.Load.
271 -- This is the expected unit name for a file other than the main unit,
272 -- since these are cases where we load the unit using Lib.Load and we
273 -- know the unit that is expected. It must be the same as Unit_Name
274 -- if it is set (see test in Par.Load). Expected_Unit is set to
275 -- No_Name for the main unit.
278 -- The name of the unit. Initialized to No_Name by Lib.Load, and then
279 -- set by the parser when the unit is parsed to the unit name actually
280 -- found in the file (which should, in the absence of errors) be the
281 -- same name as Expected_Unit.
284 -- Pointer to the N_Compilation_Unit node. Initially set to Empty by
285 -- Lib.Load, and then reset to the required node by the parser when
286 -- the unit is parsed.
289 -- Pointer to the entity node for the compilation unit. Initially set
290 -- to Empty by Lib.Load, and then reset to the required entity by the
291 -- parser when the unit is parsed.
294 -- This is the number of the unit within the generated dependency
295 -- lines (D lines in the ALI file) which are sorted into alphabetical
296 -- order. The number is ones origin, so a value of 2 refers to the
297 -- second generated D line. The Dependency_Number values are set
298 -- as the D lines are generated, and are used to generate proper
299 -- unit references in the generated xref information.
302 -- A flag indicating if this unit was compiled with dynamic elaboration
303 -- checks specified (as the result of using the -gnatE compilation
304 -- option or a pragma Elaboration_Checks (Dynamic).
307 -- A flag that is initialized to False, and gets set to True if a fatal
308 -- error occurs during the processing of a unit. A fatal error is one
309 -- defined as serious enough to stop the next phase of the compiler
310 -- from running (i.e. fatal error during parsing stops semantics,
311 -- fatal error during semantics stops code generation). Note that
312 -- currently, errors of any kind cause Fatal_Error to be set, but
313 -- eventually perhaps only errors labeled as Fatal_Errors should be
314 -- this severe if we decide to try Sem on sources with minor errors.
317 -- This flag is set True for all units in the current file for which
318 -- code is to be generated. This includes the unit explicitly compiled,
319 -- together with its specification, and any subunits.
322 -- A Boolean flag, initially set to False when a unit entry is created,
323 -- and set to True if the unit defines a remote access to class wide
324 -- (RACW) object. This is used for controlling generation of the RA
325 -- attribute in the ali file.
328 -- N_String_Literal node from a valid pragma Ident that applies to
329 -- this unit. If no Ident pragma applies to the unit, then Empty.
332 -- A flag that is used to catch circular WITH dependencies. It is set
333 -- True when an entry is initially created in the file table, and set
334 -- False when the load is completed, or ends with an error.
337 -- This field is used to indicate the priority of a possible main
338 -- program, as set by a pragma Priority. A value of -1 indicates
339 -- that the default priority is to be used (and is also used for
340 -- entries that do not correspond to possible main programs).
343 -- This field holds a serial number used by New_Internal_Name to
344 -- generate unique temporary numbers on a unit by unit basis. The
345 -- only access to this field is via the Increment_Serial_Number
346 -- routine which increments the current value and returns it. This
347 -- serial number is separate for each unit.
350 -- This field holds the version of the unit, which is computed as
351 -- the exclusive or of the checksums of this unit, and all its
352 -- semantically dependent units. Access to the version number field
353 -- is not direct, but is done through the routines described below.
354 -- When a unit table entry is created, this field is initialized to
355 -- the checksum of the corresponding source file. Version_Update is
356 -- then called to reflect the contributions of any unit on which this
357 -- unit is semantically dependent.
359 -- The units table is reset to empty at the start of the compilation of
360 -- each main unit by Lib.Initialize. Entries are then added by calls to
361 -- the Lib.Load procedure. The following subprograms are used to access
362 -- and modify entries in the Units table. Individual entries are accessed
363 -- using a unit number value which ranges from Main_Unit (the first entry,
364 -- which is always for the current main unit) to Last_Unit.
366 Default_Main_Priority
: constant Int
:= -1;
367 -- Value used in Main_Priority field to indicate default main priority
369 function Cunit
(U
: Unit_Number_Type
) return Node_Id
;
370 function Cunit_Entity
(U
: Unit_Number_Type
) return Entity_Id
;
371 function Dependency_Num
(U
: Unit_Number_Type
) return Nat
;
372 function Dynamic_Elab
(U
: Unit_Number_Type
) return Boolean;
373 function Error_Location
(U
: Unit_Number_Type
) return Source_Ptr
;
374 function Expected_Unit
(U
: Unit_Number_Type
) return Unit_Name_Type
;
375 function Fatal_Error
(U
: Unit_Number_Type
) return Boolean;
376 function Generate_Code
(U
: Unit_Number_Type
) return Boolean;
377 function Ident_String
(U
: Unit_Number_Type
) return Node_Id
;
378 function Has_RACW
(U
: Unit_Number_Type
) return Boolean;
379 function Loading
(U
: Unit_Number_Type
) return Boolean;
380 function Main_Priority
(U
: Unit_Number_Type
) return Int
;
381 function Munit_Index
(U
: Unit_Number_Type
) return Nat
;
382 function Source_Index
(U
: Unit_Number_Type
) return Source_File_Index
;
383 function Unit_File_Name
(U
: Unit_Number_Type
) return File_Name_Type
;
384 function Unit_Name
(U
: Unit_Number_Type
) return Unit_Name_Type
;
385 -- Get value of named field from given units table entry
387 procedure Set_Cunit
(U
: Unit_Number_Type
; N
: Node_Id
);
388 procedure Set_Cunit_Entity
(U
: Unit_Number_Type
; E
: Entity_Id
);
389 procedure Set_Dynamic_Elab
(U
: Unit_Number_Type
; B
: Boolean := True);
390 procedure Set_Error_Location
(U
: Unit_Number_Type
; W
: Source_Ptr
);
391 procedure Set_Fatal_Error
(U
: Unit_Number_Type
; B
: Boolean := True);
392 procedure Set_Generate_Code
(U
: Unit_Number_Type
; B
: Boolean := True);
393 procedure Set_Has_RACW
(U
: Unit_Number_Type
; B
: Boolean := True);
394 procedure Set_Ident_String
(U
: Unit_Number_Type
; N
: Node_Id
);
395 procedure Set_Loading
(U
: Unit_Number_Type
; B
: Boolean := True);
396 procedure Set_Main_Priority
(U
: Unit_Number_Type
; P
: Int
);
397 procedure Set_Unit_Name
(U
: Unit_Number_Type
; N
: Unit_Name_Type
);
398 -- Set value of named field for given units table entry. Note that we
399 -- do not have an entry for each possible field, since some of the fields
400 -- can only be set by specialized interfaces (defined below).
402 function Version_Get
(U
: Unit_Number_Type
) return Word_Hex_String
;
403 -- Returns the version as a string with 8 hex digits (upper case letters)
405 function Last_Unit
return Unit_Number_Type
;
406 -- Unit number of last allocated unit
408 function Num_Units
return Nat
;
409 -- Number of units currently in unit table
411 procedure Remove_Unit
(U
: Unit_Number_Type
);
412 -- Remove unit U from unit table. Currently this is effective only
413 -- if U is the last unit currently stored in the unit table.
415 function Entity_Is_In_Main_Unit
(E
: Entity_Id
) return Boolean;
416 -- Returns True if the entity E is declared in the main unit, or, in
417 -- its corresponding spec, or one of its subunits. Entities declared
418 -- within generic instantiations return True if the instantiation is
419 -- itself "in the main unit" by this definition. Otherwise False.
421 function Get_Source_Unit
(N
: Node_Or_Entity_Id
) return Unit_Number_Type
;
422 pragma Inline
(Get_Source_Unit
);
423 function Get_Source_Unit
(S
: Source_Ptr
) return Unit_Number_Type
;
424 -- Return unit number of file identified by given source pointer value.
425 -- This call must always succeed, since any valid source pointer value
426 -- belongs to some previously loaded module. If the given source pointer
427 -- value is within an instantiation, this function returns the unit number
428 -- of the template, i.e. the unit containing the source code corresponding
429 -- to the given Source_Ptr value. The version taking a Node_Id argument, N,
430 -- simply applies the function to Sloc (N).
432 function Get_Code_Unit
(N
: Node_Or_Entity_Id
) return Unit_Number_Type
;
433 pragma Inline
(Get_Code_Unit
);
434 function Get_Code_Unit
(S
: Source_Ptr
) return Unit_Number_Type
;
435 -- This is like Get_Source_Unit, except that in the instantiation case,
436 -- it uses the location of the top level instantiation, rather than the
437 -- template, so it returns the unit number containing the code that
438 -- corresponds to the node N, or the source location S.
440 function In_Same_Source_Unit
(N1
, N2
: Node_Or_Entity_Id
) return Boolean;
441 pragma Inline
(In_Same_Source_Unit
);
442 -- Determines if the two nodes or entities N1 and N2 are in the same
443 -- source unit, the criterion being that Get_Source_Unit yields the
444 -- same value for each argument.
446 function In_Same_Code_Unit
(N1
, N2
: Node_Or_Entity_Id
) return Boolean;
447 pragma Inline
(In_Same_Code_Unit
);
448 -- Determines if the two nodes or entities N1 and N2 are in the same
449 -- code unit, the criterion being that Get_Code_Unit yields the same
450 -- value for each argument.
452 function In_Same_Extended_Unit
(N1
, N2
: Node_Or_Entity_Id
) return Boolean;
453 pragma Inline
(In_Same_Extended_Unit
);
454 -- Determines if two nodes or entities N1 and N2 are in the same
455 -- extended unit, where an extended unit is defined as a unit and all
456 -- its subunits (considered recursively, i.e. subunits of subunits are
457 -- included). Returns true if S1 and S2 are in the same extended unit
458 -- and False otherwise.
460 function In_Same_Extended_Unit
(S1
, S2
: Source_Ptr
) return Boolean;
461 pragma Inline
(In_Same_Extended_Unit
);
462 -- Determines if the two source locations S1 and S2 are in the same
463 -- extended unit, where an extended unit is defined as a unit and all
464 -- its subunits (considered recursively, i.e. subunits of subunits are
465 -- included). Returns true if S1 and S2 are in the same extended unit
466 -- and False otherwise.
468 function In_Extended_Main_Code_Unit
469 (N
: Node_Or_Entity_Id
) return Boolean;
470 -- Return True if the node is in the generated code of the extended main
471 -- unit, defined as the main unit, its specification (if any), and all
472 -- its subunits (considered recursively). Units for which this enquiry
473 -- returns True are those for which code will be generated. Nodes from
474 -- instantiations are included in the extended main unit for this call.
475 -- If the main unit is itself a subunit, then the extended main unit
476 -- includes its parent unit, and the parent unit spec if it is separate.
478 function In_Extended_Main_Code_Unit
(Loc
: Source_Ptr
) return Boolean;
479 -- Same function as above, but argument is a source pointer rather
482 function In_Extended_Main_Source_Unit
483 (N
: Node_Or_Entity_Id
) return Boolean;
484 -- Return True if the node is in the source text of the extended main
485 -- unit, defined as the main unit, its specification (if any), and all
486 -- its subunits (considered recursively). Units for which this enquiry
487 -- returns True are those for which code will be generated. This differs
488 -- from In_Extended_Main_Code_Unit only in that instantiations are not
489 -- included for the purposes of this call. If the main unit is itself
490 -- a subunit, then the extended main unit includes its parent unit,
491 -- and the parent unit spec if it is separate.
493 function In_Extended_Main_Source_Unit
(Loc
: Source_Ptr
) return Boolean;
494 -- Same function as above, but argument is a source pointer
496 function In_Predefined_Unit
(N
: Node_Or_Entity_Id
) return Boolean;
497 -- Returns True if the given node or entity appears within the source text
498 -- of a predefined unit (i.e. within Ada, Interfaces, System or within one
499 -- of the descendent packages of one of these three packages).
501 function In_Predefined_Unit
(S
: Source_Ptr
) return Boolean;
502 -- Same function as above but argument is a source pointer
504 function Earlier_In_Extended_Unit
(S1
, S2
: Source_Ptr
) return Boolean;
505 -- Given two Sloc values for which In_Same_Extended_Unit is true,
506 -- determine if S1 appears before S2. Returns True if S1 appears before
507 -- S2, and False otherwise. The result is undefined if S1 and S2 are
508 -- not in the same extended unit.
510 function Compilation_Switches_Last
return Nat
;
511 -- Return the count of stored compilation switches
513 function Get_Compilation_Switch
(N
: Pos
) return String_Ptr
;
514 -- Return the Nth stored compilation switch, or null if less than N
515 -- switches have been stored. Used by ASIS and back ends written in Ada.
517 function Get_Cunit_Unit_Number
(N
: Node_Id
) return Unit_Number_Type
;
518 -- Return unit number of the unit whose N_Compilation_Unit node is the
519 -- one passed as an argument. This must always succeed since the node
520 -- could not have been built without making a unit table entry.
522 function Get_Cunit_Entity_Unit_Number
523 (E
: Entity_Id
) return Unit_Number_Type
;
524 -- Return unit number of the unit whose compilation unit spec entity is
525 -- the one passed as an argument. This must always succeed since the
526 -- entity could not have been built without making a unit table entry.
528 function Increment_Serial_Number
return Nat
;
529 -- Increment Serial_Number field for current unit, and return the
530 -- incremented value.
532 procedure Synchronize_Serial_Number
;
533 -- This function increments the Serial_Number field for the current
534 -- unit but does not return the incremented value. This is used when
535 -- there is a situation where one path of control increments a serial
536 -- number (using Increment_Serial_Number), and the other path does not
537 -- and it is important to keep the serial numbers synchronized in the
538 -- two cases (e.g. when the references in a package and a client must
539 -- be kept consistent).
541 procedure Replace_Linker_Option_String
543 Match_String
: String);
544 -- Replace an existing Linker_Option if the prefix Match_String
545 -- matches, otherwise call Store_Linker_Option_String.
547 procedure Store_Compilation_Switch
(Switch
: String);
548 -- Called to register a compilation switch, either front-end or
549 -- back-end, which may influence the generated output file(s).
551 procedure Disable_Switch_Storing
;
552 -- Disable the registration of compilation switches with
553 -- Store_Compilation_Switch. This is used to not register switches added
554 -- automatically by the gcc driver.
556 procedure Store_Linker_Option_String
(S
: String_Id
);
557 -- This procedure is called to register the string from a pragma
558 -- Linker_Option. The argument is the Id of the string to register.
560 procedure Initialize
;
561 -- Initialize internal tables
564 -- Lock internal tables before calling back end
567 -- Initializes internal tables from current tree file using the relevant
568 -- Table.Tree_Read routines.
570 procedure Tree_Write
;
571 -- Writes out internal tables to current tree file using the relevant
572 -- Table.Tree_Write routines.
574 function Is_Loaded
(Uname
: Unit_Name_Type
) return Boolean;
575 -- Determines if unit with given name is already loaded, i.e. there is
576 -- already an entry in the file table with this unit name for which the
577 -- corresponding file was found and parsed. Note that the Fatal_Error flag
578 -- of this entry must be checked before proceeding with further processing.
580 procedure Version_Referenced
(S
: String_Id
);
581 -- This routine is called from Exp_Attr to register the use of a Version
582 -- or Body_Version attribute. The argument is the external name used to
583 -- access the version string.
585 procedure List
(File_Names_Only
: Boolean := False);
586 -- Lists units in active library (i.e. generates output consisting of a
587 -- sorted listing of the units represented in File table, with the
588 -- exception of the main unit). If File_Names_Only is set to True, then
589 -- the list includes only file names, and no other information. Otherwise
590 -- the unit name and time stamp are also output. File_Names_Only also
591 -- restricts the list to exclude any predefined files.
593 function Generic_Separately_Compiled
(E
: Entity_Id
) return Boolean;
594 -- This is the old version of tbe documentation of this function:
596 -- Most generic units must be separately compiled. Since we always use
597 -- macro substitution for generics, the resulting object file is a dummy
598 -- one with no code, but the ali file has the normal form, and we need
599 -- this ali file so that the binder can work out a correct order of
600 -- elaboration. However, we do not need to separate compile generics
601 -- if the generic files are language defined, since in this case there
602 -- are no order of elaborration problems, and we can simply incorporate
603 -- the context clause of the generic unit into the client. There are two
604 -- reasons for making this exception for predefined units. First, clearly
605 -- it is more efficient not to introduce extra unnecessary files. Second,
606 -- the old version of GNAT did not compile any generic units. That was
607 -- clearly incorrect in some cases of complex order of elaboration and
608 -- was fixed in version 3.10 of GNAT. However, the transition would have
609 -- caused bootstrap path problems in the case of generics used in the
610 -- compiler itself. The only such generics are predefined ones. This
611 -- function returns True if the given generic unit entity E is for a
612 -- generic unit that should be separately compiled, and false otherwise.
614 -- Now GNAT can compile any generic unit including predefined ones, but
615 -- because of the backward compatibility (to keep the ability to use old
616 -- compiler versions to build GNAT) compiling library generics is an
617 -- option. That is, now GNAT compiles a library generic as an ordinary
618 -- unit, but it also can build an exeutable in case if its library
619 -- contains some (or all) predefined generics non compiled. See 9628-002
620 -- for the description of changes to be done to get rid of a special
621 -- processing of library generic.
623 -- So now this function returns TRUE if a generic MUST be separately
624 -- compiled with the current approach.
626 function Generic_Separately_Compiled
627 (Sfile
: File_Name_Type
) return Boolean;
628 -- Same as the previous function, but works directly on a unit file name
631 pragma Inline
(Cunit
);
632 pragma Inline
(Cunit_Entity
);
633 pragma Inline
(Dependency_Num
);
634 pragma Inline
(Fatal_Error
);
635 pragma Inline
(Generate_Code
);
636 pragma Inline
(Has_RACW
);
637 pragma Inline
(Increment_Serial_Number
);
638 pragma Inline
(Loading
);
639 pragma Inline
(Main_Priority
);
640 pragma Inline
(Munit_Index
);
641 pragma Inline
(Set_Cunit
);
642 pragma Inline
(Set_Cunit_Entity
);
643 pragma Inline
(Set_Fatal_Error
);
644 pragma Inline
(Set_Generate_Code
);
645 pragma Inline
(Set_Has_RACW
);
646 pragma Inline
(Set_Loading
);
647 pragma Inline
(Set_Main_Priority
);
648 pragma Inline
(Set_Unit_Name
);
649 pragma Inline
(Source_Index
);
650 pragma Inline
(Unit_File_Name
);
651 pragma Inline
(Unit_Name
);
653 type Unit_Record
is record
654 Unit_File_Name
: File_Name_Type
;
655 Unit_Name
: Unit_Name_Type
;
657 Expected_Unit
: Unit_Name_Type
;
658 Source_Index
: Source_File_Index
;
660 Cunit_Entity
: Entity_Id
;
661 Dependency_Num
: Int
;
662 Fatal_Error
: Boolean;
663 Generate_Code
: Boolean;
665 Ident_String
: Node_Id
;
670 Dynamic_Elab
: Boolean;
671 Error_Location
: Source_Ptr
;
674 package Units
is new Table
.Table
(
675 Table_Component_Type
=> Unit_Record
,
676 Table_Index_Type
=> Unit_Number_Type
,
677 Table_Low_Bound
=> Main_Unit
,
678 Table_Initial
=> Alloc
.Units_Initial
,
679 Table_Increment
=> Alloc
.Units_Increment
,
680 Table_Name
=> "Units");
682 -- The following table stores strings from pragma Linker_Option lines
684 type Linker_Option_Entry
is record
686 -- The string for the linker option line
688 Unit
: Unit_Number_Type
;
689 -- The unit from which the linker option comes
692 package Linker_Option_Lines
is new Table
.Table
(
693 Table_Component_Type
=> Linker_Option_Entry
,
694 Table_Index_Type
=> Integer,
695 Table_Low_Bound
=> 1,
696 Table_Initial
=> Alloc
.Linker_Option_Lines_Initial
,
697 Table_Increment
=> Alloc
.Linker_Option_Lines_Increment
,
698 Table_Name
=> "Linker_Option_Lines");
700 -- The following table records the compilation switches used to compile
701 -- the main unit. The table includes only switches and excludes -quiet,
702 -- -dumpbase, and -o switches, since the latter are typically artifacts
703 -- of the gcc/gnat1 interface.
705 -- This table is set as part of the compiler argument scanning in
706 -- Back_End. It can also be reset in -gnatc mode from the data in an
707 -- existing ali file, and is read and written by the Tree_Read and
708 -- Tree_Write routines for ASIS.
710 package Compilation_Switches
is new Table
.Table
(
711 Table_Component_Type
=> String_Ptr
,
712 Table_Index_Type
=> Nat
,
713 Table_Low_Bound
=> 1,
715 Table_Increment
=> 100,
716 Table_Name
=> "Compilation_Switches");
718 Load_Msg_Sloc
: Source_Ptr
;
719 -- Location for placing error messages (a token in the main source text)
720 -- This is set from Sloc (Enode) by Load only in the case where this Sloc
721 -- is in the main source file. This ensures that not found messages and
722 -- circular dependency messages reference the original with in this source.
724 type Unit_Ref_Table
is array (Pos
range <>) of Unit_Number_Type
;
725 -- Type to hold list of indirect references to unit number table
727 type Load_Stack_Entry
is record
728 Unit_Number
: Unit_Number_Type
;
729 From_Limited_With
: Boolean;
732 -- The Load_Stack table contains a list of unit numbers (indices into the
733 -- unit table) of units being loaded on a single dependency chain, and a
734 -- flag to indicate whether this unit is loaded through a limited_with
735 -- clause. The First entry is the main unit. The second entry, if present
736 -- is a unit on which the first unit depends, etc. This stack is used to
737 -- generate error messages showing the dependency chain if a file is not
738 -- found, or whether a true circular dependency exists. The Load_Unit
739 -- function makes an entry in this table when it is called, and removes
740 -- the entry just before it returns.
742 package Load_Stack
is new Table
.Table
(
743 Table_Component_Type
=> Load_Stack_Entry
,
744 Table_Index_Type
=> Nat
,
745 Table_Low_Bound
=> 0,
746 Table_Initial
=> Alloc
.Load_Stack_Initial
,
747 Table_Increment
=> Alloc
.Load_Stack_Increment
,
748 Table_Name
=> "Load_Stack");
750 procedure Sort
(Tbl
: in out Unit_Ref_Table
);
751 -- This procedure sorts the given unit reference table in order of
752 -- ascending unit names, where the ordering relation is as described
753 -- by the comparison routines provided by package Uname.
755 -- The Version_Ref table records Body_Version and Version attribute
756 -- references. The entries are simply the strings for the external
757 -- names that correspond to the referenced values.
759 package Version_Ref
is new Table
.Table
(
760 Table_Component_Type
=> String_Id
,
761 Table_Index_Type
=> Nat
,
762 Table_Low_Bound
=> 1,
764 Table_Increment
=> 100,
765 Table_Name
=> "Version_Ref");