Update concepts branch to revision 131834
[official-gcc.git] / gcc / ada / sem_mech.ads
blob1673a671b0ec3a9080c34e2cc4b628babac7e953
1 ------------------------------------------------------------------------------
2 -- --
3 -- GNAT COMPILER COMPONENTS --
4 -- --
5 -- S E M _ M E C H --
6 -- --
7 -- S p e c --
8 -- --
9 -- Copyright (C) 1996-2008, 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. 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 COPYING3. If not, go to --
19 -- http://www.gnu.org/licenses for a complete copy of the license. --
20 -- --
21 -- GNAT was originally developed by the GNAT team at New York University. --
22 -- Extensive contributions were provided by Ada Core Technologies Inc. --
23 -- --
24 ------------------------------------------------------------------------------
26 -- This package contains the routine used to establish calling mechanisms
27 -- The reason we separate this off into its own package is that it is
28 -- entirely possible that it may need some target specific specialization.
30 with Types; use Types;
32 package Sem_Mech is
34 -------------------------------------------------
35 -- Definitions for Parameter Mechanism Control --
36 -------------------------------------------------
38 -- For parameters passed to subprograms, and for function return values,
39 -- as passing mechanism is defined. The entity attribute Mechanism returns
40 -- an indication of the mechanism, and Set_Mechanism can be used to set
41 -- the mechanism. At the program level, there are three ways to explicitly
42 -- set the mechanism:
44 -- An Import_xxx or Export_xxx pragma (where xxx is Function, Procedure,
45 -- or Valued_Procedure) can explicitly set the mechanism for either a
46 -- parameter or a function return value. A mechanism explicitly set by
47 -- such a pragma overrides the effect of C_Pass_By_Copy described below.
49 -- If convention C_Pass_By_Copy is set for a record, and the record type
50 -- is used as the formal type of a subprogram with a foreign convention,
51 -- then the mechanism is set to By_Copy.
53 -- If a pragma C_Pass_By_Copy applies, and a record type has Convention
54 -- C, and the record type is used as the formal type of a subprogram
55 -- with a foreign convention, then the mechanism is set to use By_Copy
56 -- if the size of the record is sufficiently small (as determined by
57 -- the value of the parameter to pragma C_Pass_By_Copy).
59 -- The subtype Mechanism_Type (declared in Types) is used to describe
60 -- the mechanism to be used. The following special values of this type
61 -- specify the mechanism, as follows.
63 Default_Mechanism : constant Mechanism_Type := 0;
64 -- The default setting indicates that the backend will choose the proper
65 -- default mechanism. This depends on the convention of the subprogram
66 -- involved, and is generally target dependent. In the compiler, the
67 -- backend chooses the mechanism in this case in accordance with any
68 -- requirements imposed by the ABI. Note that Default is never used for
69 -- record types on foreign convention subprograms, since By_Reference
70 -- is forced for such types unless one of the above described approaches
71 -- is used to explicitly force By_Copy.
73 By_Copy : constant Mechanism_Type := -1;
74 -- Passing by copy is forced. The exact meaning of By_Copy (e.g. whether
75 -- at a low level the value is passed in registers, or the value is copied
76 -- and a pointer is passed), is determined by the backend in accordance
77 -- with requirements imposed by the ABI. Note that in the extended import
78 -- and export pragma mechanisms, this is called Value, rather than Copy.
80 By_Reference : constant Mechanism_Type := -2;
81 -- Passing by reference is forced. This is always equivalent to passing
82 -- a simple pointer in the case of subprograms with a foreign convention.
83 -- For unconstrained arrays passed to foreign convention subprograms, the
84 -- address of the first element of the array is passed. For convention
85 -- Ada, the result is logically to pass a reference, but the precise
86 -- mechanism (e.g. to pass bounds of unconstrained types and other needed
87 -- special information) is determined by the backend in accordance with
88 -- requirements imposed by the ABI as interpreted for Ada.
90 By_Descriptor : constant Mechanism_Type := -3;
91 By_Descriptor_UBS : constant Mechanism_Type := -4;
92 By_Descriptor_UBSB : constant Mechanism_Type := -5;
93 By_Descriptor_UBA : constant Mechanism_Type := -6;
94 By_Descriptor_S : constant Mechanism_Type := -7;
95 By_Descriptor_SB : constant Mechanism_Type := -8;
96 By_Descriptor_A : constant Mechanism_Type := -9;
97 By_Descriptor_NCA : constant Mechanism_Type := -10;
98 -- These values are used only in OpenVMS ports of GNAT. Pass by descriptor
99 -- is forced, as described in the OpenVMS ABI. The suffix indicates the
100 -- descriptor type:
102 -- UBS unaligned bit string
103 -- UBSB aligned bit string with arbitrary bounds
104 -- UBA unaligned bit array
105 -- S string, also a scalar or access type parameter
106 -- SB string with arbitrary bounds
107 -- A contiguous array
108 -- NCA non-contiguous array
110 -- Note: the form with no suffix is used if the Import/Export pragma
111 -- uses the simple form of the mechanism name where no descriptor
112 -- type is supplied. In this case the back end assigns a descriptor
113 -- type based on the Ada type in accordance with the OpenVMS ABI.
115 subtype Descriptor_Codes is Mechanism_Type
116 range By_Descriptor_NCA .. By_Descriptor;
117 -- Subtype including all descriptor mechanisms
119 -- All the above special values are non-positive. Positive values for
120 -- Mechanism_Type values have a special meaning. They are used only in
121 -- the case of records, as a result of the use of the C_Pass_By_Copy
122 -- pragma, and the meaning is that if the size of the record is known
123 -- at compile time and does not exceed the mechanism type value, then
124 -- By_Copy passing is forced, otherwise By_Reference is forced.
126 ----------------------
127 -- Global Variables --
128 ----------------------
130 Default_C_Record_Mechanism : Mechanism_Type := By_Reference;
131 -- This value is the default mechanism used for C convention records
132 -- in foreign-convention subprograms if no mechanism is otherwise
133 -- specified. This value is modified appropriately by the occurrence
134 -- of a C_Pass_By_Copy configuration pragma.
136 -----------------
137 -- Subprograms --
138 -----------------
140 procedure Set_Mechanisms (E : Entity_Id);
141 -- E is a subprogram or subprogram type that has been frozen, so the
142 -- convention of the subprogram and all its formal types and result
143 -- type in the case of a function are established. The function of
144 -- this call is to set mechanism values for formals and for the
145 -- function return if they have not already been explicitly set by
146 -- a use of an extended Import or Export pragma. The idea is to set
147 -- mechanism values wherever the semantics is dictated by either
148 -- requirements or implementation advice in the RM, and to leave
149 -- the mechanism set to Default if there is no requirement, so that
150 -- the back-end is free to choose the most efficient method.
152 procedure Set_Mechanism_Value (Ent : Entity_Id; Mech_Name : Node_Id);
153 -- Mech is a parameter passing mechanism (see Import_Function syntax
154 -- for MECHANISM_NAME). This routine checks that the mechanism argument
155 -- has the right form, and if not issues an error message. If the
156 -- argument has the right form then the Mechanism field of Ent is
157 -- set appropriately. It also performs some error checks. Note that
158 -- the mechanism name has not been analyzed (and cannot indeed be
159 -- analyzed, since it is semantic nonsense), so we get it in the
160 -- exact form created by the parser.
162 procedure Set_Mechanism_With_Checks
163 (Ent : Entity_Id;
164 Mech : Mechanism_Type;
165 Enod : Node_Id);
166 -- Sets the mechanism of Ent to the given Mech value, after first checking
167 -- that the request makes sense. If it does not make sense, a warning is
168 -- posted on node Enod, and the Mechanism of Ent is unchanged.
170 end Sem_Mech;