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