1 \input texinfo @c -*-texinfo-*-
4 @c oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
6 @c GNAT DOCUMENTATION o
10 @c GNAT is maintained by Ada Core Technologies Inc (http://www.gnat.com). o
12 @c oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
14 @setfilename gnat_ugn.info
17 Copyright @copyright{} 1995-2009 Free Software Foundation,
20 Permission is granted to copy, distribute and/or modify this document
21 under the terms of the GNU Free Documentation License, Version 1.2 or
22 any later version published by the Free Software Foundation; with no
23 Invariant Sections, with no Front-Cover Texts and with no Back-Cover
24 Texts. A copy of the license is included in the section entitled
25 ``GNU Free Documentation License''.
28 @c oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
30 @c GNAT_UGN Style Guide
32 @c 1. Always put a @noindent on the line before the first paragraph
33 @c after any of these commands:
45 @c 2. DO NOT use @example. Use @smallexample instead.
46 @c a) DO NOT use highlighting commands (@b{}, @i{}) inside an @smallexample
47 @c context. These can interfere with the readability of the texi
48 @c source file. Instead, use one of the following annotated
49 @c @smallexample commands, and preprocess the texi file with the
50 @c ada2texi tool (which generates appropriate highlighting):
51 @c @smallexample @c ada
52 @c @smallexample @c adanocomment
53 @c @smallexample @c projectfile
54 @c b) The "@c ada" markup will result in boldface for reserved words
55 @c and italics for comments
56 @c c) The "@c adanocomment" markup will result only in boldface for
57 @c reserved words (comments are left alone)
58 @c d) The "@c projectfile" markup is like "@c ada" except that the set
59 @c of reserved words include the new reserved words for project files
61 @c 3. Each @chapter, @section, @subsection, @subsubsection, etc.
62 @c command must be preceded by two empty lines
64 @c 4. The @item command should be on a line of its own if it is in an
65 @c @itemize or @enumerate command.
67 @c 5. When talking about ALI files use "ALI" (all uppercase), not "Ali"
70 @c 6. DO NOT put trailing spaces at the end of a line. Such spaces will
71 @c cause the document build to fail.
73 @c 7. DO NOT use @cartouche for examples that are longer than around 10 lines.
74 @c This command inhibits page breaks, so long examples in a @cartouche can
75 @c lead to large, ugly patches of empty space on a page.
77 @c NOTE: This file should be submitted to xgnatugn with either the vms flag
78 @c or the unw flag set. The unw flag covers topics for both Unix and
81 @c oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
84 @c This flag is used where the text refers to conditions that exist when the
85 @c text was entered into the document but which may change over time.
86 @c Update the setting for the flag, and (if necessary) the text surrounding,
87 @c the references to the flag, on future doc revisions:
88 @c search for @value{NOW}.
92 @set DEFAULTLANGUAGEVERSION Ada 2005
93 @set NONDEFAULTLANGUAGEVERSION Ada 95
100 @set PLATFORM OpenVMS
105 @c The ARG is an optional argument. To be used for macro arguments in
106 @c their documentation (@defmac).
108 @r{[}@var{\varname\}@r{]}@c
111 @settitle @value{EDITION} User's Guide @value{PLATFORM}
112 @dircategory GNU Ada tools
114 * @value{EDITION} User's Guide: (gnat_ugn). @value{PLATFORM}
117 @include gcc-common.texi
119 @setchapternewpage odd
124 @title @value{EDITION} User's Guide
128 @titlefont{@i{@value{PLATFORM}}}
134 @subtitle GNAT, The GNU Ada Compiler
139 @vskip 0pt plus 1filll
146 @node Top, About This Guide, (dir), (dir)
147 @top @value{EDITION} User's Guide
150 @value{EDITION} User's Guide @value{PLATFORM}
153 GNAT, The GNU Ada Compiler@*
154 GCC version @value{version-GCC}@*
161 * Getting Started with GNAT::
162 * The GNAT Compilation Model::
163 * Compiling Using gcc::
164 * Binding Using gnatbind::
165 * Linking Using gnatlink::
166 * The GNAT Make Program gnatmake::
167 * Improving Performance::
168 * Renaming Files Using gnatchop::
169 * Configuration Pragmas::
170 * Handling Arbitrary File Naming Conventions Using gnatname::
171 * GNAT Project Manager::
172 * The Cross-Referencing Tools gnatxref and gnatfind::
173 * The GNAT Pretty-Printer gnatpp::
174 * The GNAT Metric Tool gnatmetric::
175 * File Name Krunching Using gnatkr::
176 * Preprocessing Using gnatprep::
178 * The GNAT Run-Time Library Builder gnatlbr::
180 * The GNAT Library Browser gnatls::
181 * Cleaning Up Using gnatclean::
183 * GNAT and Libraries::
184 * Using the GNU make Utility::
186 * Memory Management Issues::
187 * Stack Related Facilities::
188 * Verifying Properties Using gnatcheck::
189 * Creating Sample Bodies Using gnatstub::
190 * Generating Ada Bindings for C and C++ headers::
191 * Other Utility Programs::
192 * Running and Debugging Ada Programs::
194 * Code Coverage and Profiling::
197 * Compatibility with HP Ada::
199 * Platform-Specific Information for the Run-Time Libraries::
200 * Example of Binder Output File::
201 * Elaboration Order Handling in GNAT::
202 * Conditional Compilation::
204 * Compatibility and Porting Guide::
206 * Microsoft Windows Topics::
208 * GNU Free Documentation License::
211 --- The Detailed Node Listing ---
215 * What This Guide Contains::
216 * What You Should Know before Reading This Guide::
217 * Related Information::
220 Getting Started with GNAT
223 * Running a Simple Ada Program::
224 * Running a Program with Multiple Units::
225 * Using the gnatmake Utility::
227 * Editing with Emacs::
230 * Introduction to GPS::
233 The GNAT Compilation Model
235 * Source Representation::
236 * Foreign Language Representation::
237 * File Naming Rules::
238 * Using Other File Names::
239 * Alternative File Naming Schemes::
240 * Generating Object Files::
241 * Source Dependencies::
242 * The Ada Library Information Files::
243 * Binding an Ada Program::
244 * Mixed Language Programming::
246 * Building Mixed Ada & C++ Programs::
247 * Comparison between GNAT and C/C++ Compilation Models::
249 * Comparison between GNAT and Conventional Ada Library Models::
251 * Placement of temporary files::
254 Foreign Language Representation
257 * Other 8-Bit Codes::
258 * Wide Character Encodings::
260 Compiling Ada Programs With gcc
262 * Compiling Programs::
264 * Search Paths and the Run-Time Library (RTL)::
265 * Order of Compilation Issues::
270 * Output and Error Message Control::
271 * Warning Message Control::
272 * Debugging and Assertion Control::
273 * Validity Checking::
276 * Using gcc for Syntax Checking::
277 * Using gcc for Semantic Checking::
278 * Compiling Different Versions of Ada::
279 * Character Set Control::
280 * File Naming Control::
281 * Subprogram Inlining Control::
282 * Auxiliary Output Control::
283 * Debugging Control::
284 * Exception Handling Control::
285 * Units to Sources Mapping Files::
286 * Integrated Preprocessing::
291 Binding Ada Programs With gnatbind
294 * Switches for gnatbind::
295 * Command-Line Access::
296 * Search Paths for gnatbind::
297 * Examples of gnatbind Usage::
299 Switches for gnatbind
301 * Consistency-Checking Modes::
302 * Binder Error Message Control::
303 * Elaboration Control::
305 * Binding with Non-Ada Main Programs::
306 * Binding Programs with No Main Subprogram::
308 Linking Using gnatlink
311 * Switches for gnatlink::
313 The GNAT Make Program gnatmake
316 * Switches for gnatmake::
317 * Mode Switches for gnatmake::
318 * Notes on the Command Line::
319 * How gnatmake Works::
320 * Examples of gnatmake Usage::
322 Improving Performance
323 * Performance Considerations::
324 * Text_IO Suggestions::
325 * Reducing Size of Ada Executables with gnatelim::
326 * Reducing Size of Executables with unused subprogram/data elimination::
328 Performance Considerations
329 * Controlling Run-Time Checks::
330 * Use of Restrictions::
331 * Optimization Levels::
332 * Debugging Optimized Code::
333 * Inlining of Subprograms::
334 * Other Optimization Switches::
335 * Optimization and Strict Aliasing::
337 * Coverage Analysis::
340 Reducing Size of Ada Executables with gnatelim
343 * Correcting the List of Eliminate Pragmas::
344 * Making Your Executables Smaller::
345 * Summary of the gnatelim Usage Cycle::
347 Reducing Size of Executables with unused subprogram/data elimination
348 * About unused subprogram/data elimination::
349 * Compilation options::
351 Renaming Files Using gnatchop
353 * Handling Files with Multiple Units::
354 * Operating gnatchop in Compilation Mode::
355 * Command Line for gnatchop::
356 * Switches for gnatchop::
357 * Examples of gnatchop Usage::
359 Configuration Pragmas
361 * Handling of Configuration Pragmas::
362 * The Configuration Pragmas Files::
364 Handling Arbitrary File Naming Conventions Using gnatname
366 * Arbitrary File Naming Conventions::
368 * Switches for gnatname::
369 * Examples of gnatname Usage::
374 * Examples of Project Files::
375 * Project File Syntax::
376 * Objects and Sources in Project Files::
377 * Importing Projects::
378 * Project Extension::
379 * Project Hierarchy Extension::
380 * External References in Project Files::
381 * Packages in Project Files::
382 * Variables from Imported Projects::
385 * Stand-alone Library Projects::
386 * Switches Related to Project Files::
387 * Tools Supporting Project Files::
388 * An Extended Example::
389 * Project File Complete Syntax::
391 The Cross-Referencing Tools gnatxref and gnatfind
393 * gnatxref Switches::
394 * gnatfind Switches::
395 * Project Files for gnatxref and gnatfind::
396 * Regular Expressions in gnatfind and gnatxref::
397 * Examples of gnatxref Usage::
398 * Examples of gnatfind Usage::
400 The GNAT Pretty-Printer gnatpp
402 * Switches for gnatpp::
405 The GNAT Metrics Tool gnatmetric
407 * Switches for gnatmetric::
409 File Name Krunching Using gnatkr
414 * Examples of gnatkr Usage::
416 Preprocessing Using gnatprep
417 * Preprocessing Symbols::
419 * Switches for gnatprep::
420 * Form of Definitions File::
421 * Form of Input Text for gnatprep::
424 The GNAT Run-Time Library Builder gnatlbr
427 * Switches for gnatlbr::
428 * Examples of gnatlbr Usage::
431 The GNAT Library Browser gnatls
434 * Switches for gnatls::
435 * Examples of gnatls Usage::
437 Cleaning Up Using gnatclean
439 * Running gnatclean::
440 * Switches for gnatclean::
441 @c * Examples of gnatclean Usage::
447 * Introduction to Libraries in GNAT::
448 * General Ada Libraries::
449 * Stand-alone Ada Libraries::
450 * Rebuilding the GNAT Run-Time Library::
452 Using the GNU make Utility
454 * Using gnatmake in a Makefile::
455 * Automatically Creating a List of Directories::
456 * Generating the Command Line Switches::
457 * Overcoming Command Line Length Limits::
460 Memory Management Issues
462 * Some Useful Memory Pools::
463 * The GNAT Debug Pool Facility::
468 Stack Related Facilities
470 * Stack Overflow Checking::
471 * Static Stack Usage Analysis::
472 * Dynamic Stack Usage Analysis::
474 Some Useful Memory Pools
476 The GNAT Debug Pool Facility
482 * Switches for gnatmem::
483 * Example of gnatmem Usage::
486 Verifying Properties Using gnatcheck
488 * Format of the Report File::
489 * General gnatcheck Switches::
490 * gnatcheck Rule Options::
491 * Adding the Results of Compiler Checks to gnatcheck Output::
492 * Project-Wide Checks::
495 Sample Bodies Using gnatstub
498 * Switches for gnatstub::
500 Other Utility Programs
502 * Using Other Utility Programs with GNAT::
503 * The External Symbol Naming Scheme of GNAT::
504 * Converting Ada Files to html with gnathtml::
507 Code Coverage and Profiling
509 * Code Coverage of Ada Programs using gcov::
510 * Profiling an Ada Program using gprof::
513 Running and Debugging Ada Programs
515 * The GNAT Debugger GDB::
517 * Introduction to GDB Commands::
518 * Using Ada Expressions::
519 * Calling User-Defined Subprograms::
520 * Using the Next Command in a Function::
523 * Debugging Generic Units::
524 * GNAT Abnormal Termination or Failure to Terminate::
525 * Naming Conventions for GNAT Source Files::
526 * Getting Internal Debugging Information::
534 Compatibility with HP Ada
536 * Ada Language Compatibility::
537 * Differences in the Definition of Package System::
538 * Language-Related Features::
539 * The Package STANDARD::
540 * The Package SYSTEM::
541 * Tasking and Task-Related Features::
542 * Pragmas and Pragma-Related Features::
543 * Library of Predefined Units::
545 * Main Program Definition::
546 * Implementation-Defined Attributes::
547 * Compiler and Run-Time Interfacing::
548 * Program Compilation and Library Management::
550 * Implementation Limits::
551 * Tools and Utilities::
553 Language-Related Features
555 * Integer Types and Representations::
556 * Floating-Point Types and Representations::
557 * Pragmas Float_Representation and Long_Float::
558 * Fixed-Point Types and Representations::
559 * Record and Array Component Alignment::
561 * Other Representation Clauses::
563 Tasking and Task-Related Features
565 * Implementation of Tasks in HP Ada for OpenVMS Alpha Systems::
566 * Assigning Task IDs::
567 * Task IDs and Delays::
568 * Task-Related Pragmas::
569 * Scheduling and Task Priority::
571 * External Interrupts::
573 Pragmas and Pragma-Related Features
575 * Restrictions on the Pragma INLINE::
576 * Restrictions on the Pragma INTERFACE::
577 * Restrictions on the Pragma SYSTEM_NAME::
579 Library of Predefined Units
581 * Changes to DECLIB::
585 * Shared Libraries and Options Files::
589 Platform-Specific Information for the Run-Time Libraries
591 * Summary of Run-Time Configurations::
592 * Specifying a Run-Time Library::
593 * Choosing the Scheduling Policy::
594 * Solaris-Specific Considerations::
595 * Linux-Specific Considerations::
596 * AIX-Specific Considerations::
597 * Irix-Specific Considerations::
599 Example of Binder Output File
601 Elaboration Order Handling in GNAT
604 * Checking the Elaboration Order::
605 * Controlling the Elaboration Order::
606 * Controlling Elaboration in GNAT - Internal Calls::
607 * Controlling Elaboration in GNAT - External Calls::
608 * Default Behavior in GNAT - Ensuring Safety::
609 * Treatment of Pragma Elaborate::
610 * Elaboration Issues for Library Tasks::
611 * Mixing Elaboration Models::
612 * What to Do If the Default Elaboration Behavior Fails::
613 * Elaboration for Access-to-Subprogram Values::
614 * Summary of Procedures for Elaboration Control::
615 * Other Elaboration Order Considerations::
617 Conditional Compilation
618 * Use of Boolean Constants::
619 * Debugging - A Special Case::
620 * Conditionalizing Declarations::
621 * Use of Alternative Implementations::
626 * Basic Assembler Syntax::
627 * A Simple Example of Inline Assembler::
628 * Output Variables in Inline Assembler::
629 * Input Variables in Inline Assembler::
630 * Inlining Inline Assembler Code::
631 * Other Asm Functionality::
633 Compatibility and Porting Guide
635 * Compatibility with Ada 83::
636 * Compatibility between Ada 95 and Ada 2005::
637 * Implementation-dependent characteristics::
639 @c This brief section is only in the non-VMS version
640 @c The complete chapter on HP Ada issues is in the VMS version
641 * Compatibility with HP Ada 83::
643 * Compatibility with Other Ada Systems::
644 * Representation Clauses::
646 * Transitioning to 64-Bit GNAT for OpenVMS::
650 Microsoft Windows Topics
652 * Using GNAT on Windows::
653 * CONSOLE and WINDOWS subsystems::
655 * Mixed-Language Programming on Windows::
656 * Windows Calling Conventions::
657 * Introduction to Dynamic Link Libraries (DLLs)::
658 * Using DLLs with GNAT::
659 * Building DLLs with GNAT::
660 * GNAT and Windows Resources::
662 * Setting Stack Size from gnatlink::
663 * Setting Heap Size from gnatlink::
670 @node About This Guide
671 @unnumbered About This Guide
675 This guide describes the use of @value{EDITION},
676 a compiler and software development toolset for the full Ada
677 programming language, implemented on OpenVMS for HP's Alpha and
678 Integrity server (I64) platforms.
681 This guide describes the use of @value{EDITION},
682 a compiler and software development
683 toolset for the full Ada programming language.
685 It documents the features of the compiler and tools, and explains
686 how to use them to build Ada applications.
688 @value{EDITION} implements Ada 95 and Ada 2005, and it may also be invoked in
689 Ada 83 compatibility mode.
690 By default, @value{EDITION} assumes @value{DEFAULTLANGUAGEVERSION},
691 but you can override with a compiler switch
692 (@pxref{Compiling Different Versions of Ada})
693 to explicitly specify the language version.
694 Throughout this manual, references to ``Ada'' without a year suffix
695 apply to both the Ada 95 and Ada 2005 versions of the language.
699 For ease of exposition, ``@value{EDITION}'' will be referred to simply as
700 ``GNAT'' in the remainder of this document.
707 * What This Guide Contains::
708 * What You Should Know before Reading This Guide::
709 * Related Information::
713 @node What This Guide Contains
714 @unnumberedsec What This Guide Contains
717 This guide contains the following chapters:
721 @ref{Getting Started with GNAT}, describes how to get started compiling
722 and running Ada programs with the GNAT Ada programming environment.
724 @ref{The GNAT Compilation Model}, describes the compilation model used
728 @ref{Compiling Using gcc}, describes how to compile
729 Ada programs with @command{gcc}, the Ada compiler.
732 @ref{Binding Using gnatbind}, describes how to
733 perform binding of Ada programs with @code{gnatbind}, the GNAT binding
737 @ref{Linking Using gnatlink},
738 describes @command{gnatlink}, a
739 program that provides for linking using the GNAT run-time library to
740 construct a program. @command{gnatlink} can also incorporate foreign language
741 object units into the executable.
744 @ref{The GNAT Make Program gnatmake}, describes @command{gnatmake}, a
745 utility that automatically determines the set of sources
746 needed by an Ada compilation unit, and executes the necessary compilations
750 @ref{Improving Performance}, shows various techniques for making your
751 Ada program run faster or take less space.
752 It discusses the effect of the compiler's optimization switch and
753 also describes the @command{gnatelim} tool and unused subprogram/data
757 @ref{Renaming Files Using gnatchop}, describes
758 @code{gnatchop}, a utility that allows you to preprocess a file that
759 contains Ada source code, and split it into one or more new files, one
760 for each compilation unit.
763 @ref{Configuration Pragmas}, describes the configuration pragmas
767 @ref{Handling Arbitrary File Naming Conventions Using gnatname},
768 shows how to override the default GNAT file naming conventions,
769 either for an individual unit or globally.
772 @ref{GNAT Project Manager}, describes how to use project files
773 to organize large projects.
776 @ref{The Cross-Referencing Tools gnatxref and gnatfind}, discusses
777 @code{gnatxref} and @code{gnatfind}, two tools that provide an easy
778 way to navigate through sources.
781 @ref{The GNAT Pretty-Printer gnatpp}, shows how to produce a reformatted
782 version of an Ada source file with control over casing, indentation,
783 comment placement, and other elements of program presentation style.
786 @ref{The GNAT Metric Tool gnatmetric}, shows how to compute various
787 metrics for an Ada source file, such as the number of types and subprograms,
788 and assorted complexity measures.
791 @ref{File Name Krunching Using gnatkr}, describes the @code{gnatkr}
792 file name krunching utility, used to handle shortened
793 file names on operating systems with a limit on the length of names.
796 @ref{Preprocessing Using gnatprep}, describes @code{gnatprep}, a
797 preprocessor utility that allows a single source file to be used to
798 generate multiple or parameterized source files by means of macro
803 @ref{The GNAT Run-Time Library Builder gnatlbr}, describes @command{gnatlbr},
804 a tool for rebuilding the GNAT run time with user-supplied
805 configuration pragmas.
809 @ref{The GNAT Library Browser gnatls}, describes @code{gnatls}, a
810 utility that displays information about compiled units, including dependences
811 on the corresponding sources files, and consistency of compilations.
814 @ref{Cleaning Up Using gnatclean}, describes @code{gnatclean}, a utility
815 to delete files that are produced by the compiler, binder and linker.
819 @ref{GNAT and Libraries}, describes the process of creating and using
820 Libraries with GNAT. It also describes how to recompile the GNAT run-time
824 @ref{Using the GNU make Utility}, describes some techniques for using
825 the GNAT toolset in Makefiles.
829 @ref{Memory Management Issues}, describes some useful predefined storage pools
830 and in particular the GNAT Debug Pool facility, which helps detect incorrect
833 It also describes @command{gnatmem}, a utility that monitors dynamic
834 allocation and deallocation and helps detect ``memory leaks''.
838 @ref{Stack Related Facilities}, describes some useful tools associated with
839 stack checking and analysis.
842 @ref{Verifying Properties Using gnatcheck}, discusses @code{gnatcheck},
843 a utility that checks Ada code against a set of rules.
846 @ref{Creating Sample Bodies Using gnatstub}, discusses @code{gnatstub},
847 a utility that generates empty but compilable bodies for library units.
850 @ref{Generating Ada Bindings for C and C++ headers}, describes how to
851 generate automatically Ada bindings from C and C++ headers.
854 @ref{Other Utility Programs}, discusses several other GNAT utilities,
855 including @code{gnathtml}.
859 @ref{Code Coverage and Profiling}, describes how to perform a structural
860 coverage and profile the execution of Ada programs.
864 @ref{Running and Debugging Ada Programs}, describes how to run and debug
869 @ref{Compatibility with HP Ada}, details the compatibility of GNAT with
870 HP Ada 83 @footnote{``HP Ada'' refers to the legacy product originally
871 developed by Digital Equipment Corporation and currently supported by HP.}
872 for OpenVMS Alpha. This product was formerly known as DEC Ada,
875 historical compatibility reasons, the relevant libraries still use the
880 @ref{Platform-Specific Information for the Run-Time Libraries},
881 describes the various run-time
882 libraries supported by GNAT on various platforms and explains how to
883 choose a particular library.
886 @ref{Example of Binder Output File}, shows the source code for the binder
887 output file for a sample program.
890 @ref{Elaboration Order Handling in GNAT}, describes how GNAT helps
891 you deal with elaboration order issues.
894 @ref{Conditional Compilation}, describes how to model conditional compilation,
895 both with Ada in general and with GNAT facilities in particular.
898 @ref{Inline Assembler}, shows how to use the inline assembly facility
902 @ref{Compatibility and Porting Guide}, contains sections on compatibility
903 of GNAT with other Ada development environments (including Ada 83 systems),
904 to assist in porting code from those environments.
908 @ref{Microsoft Windows Topics}, presents information relevant to the
909 Microsoft Windows platform.
913 @c *************************************************
914 @node What You Should Know before Reading This Guide
915 @c *************************************************
916 @unnumberedsec What You Should Know before Reading This Guide
918 @cindex Ada 95 Language Reference Manual
919 @cindex Ada 2005 Language Reference Manual
921 This guide assumes a basic familiarity with the Ada 95 language, as
922 described in the International Standard ANSI/ISO/IEC-8652:1995, January
924 It does not require knowledge of the new features introduced by Ada 2005,
925 (officially known as ISO/IEC 8652:1995 with Technical Corrigendum 1
927 Both reference manuals are included in the GNAT documentation
930 @node Related Information
931 @unnumberedsec Related Information
934 For further information about related tools, refer to the following
939 @xref{Top, GNAT Reference Manual, About This Guide, gnat_rm, GNAT
940 Reference Manual}, which contains all reference material for the GNAT
941 implementation of Ada.
945 @cite{Using the GNAT Programming Studio}, which describes the GPS
946 Integrated Development Environment.
949 @cite{GNAT Programming Studio Tutorial}, which introduces the
950 main GPS features through examples.
954 @cite{Ada 95 Reference Manual}, which contains reference
955 material for the Ada 95 programming language.
958 @cite{Ada 2005 Reference Manual}, which contains reference
959 material for the Ada 2005 programming language.
962 @xref{Top,, Debugging with GDB, gdb, Debugging with GDB},
964 in the GNU:[DOCS] directory,
966 for all details on the use of the GNU source-level debugger.
969 @xref{Top,, The extensible self-documenting text editor, emacs,
972 located in the GNU:[DOCS] directory if the EMACS kit is installed,
974 for full information on the extensible editor and programming
981 @unnumberedsec Conventions
983 @cindex Typographical conventions
986 Following are examples of the typographical and graphic conventions used
991 @code{Functions}, @command{utility program names}, @code{standard names},
995 @option{Option flags}
998 @file{File names}, @samp{button names}, and @samp{field names}.
1001 @code{Variables}, @env{environment variables}, and @var{metasyntactic
1008 @r{[}optional information or parameters@r{]}
1011 Examples are described by text
1013 and then shown this way.
1018 Commands that are entered by the user are preceded in this manual by the
1019 characters @w{``@code{$ }''} (dollar sign followed by space). If your system
1020 uses this sequence as a prompt, then the commands will appear exactly as
1021 you see them in the manual. If your system uses some other prompt, then
1022 the command will appear with the @code{$} replaced by whatever prompt
1023 character you are using.
1026 Full file names are shown with the ``@code{/}'' character
1027 as the directory separator; e.g., @file{parent-dir/subdir/myfile.adb}.
1028 If you are using GNAT on a Windows platform, please note that
1029 the ``@code{\}'' character should be used instead.
1032 @c ****************************
1033 @node Getting Started with GNAT
1034 @chapter Getting Started with GNAT
1037 This chapter describes some simple ways of using GNAT to build
1038 executable Ada programs.
1040 @ref{Running GNAT}, through @ref{Using the gnatmake Utility},
1041 show how to use the command line environment.
1042 @ref{Introduction to GPS}, provides a brief
1043 introduction to the GNAT Programming Studio, a visually-oriented
1044 Integrated Development Environment for GNAT.
1045 GPS offers a graphical ``look and feel'', support for development in
1046 other programming languages, comprehensive browsing features, and
1047 many other capabilities.
1048 For information on GPS please refer to
1049 @cite{Using the GNAT Programming Studio}.
1054 * Running a Simple Ada Program::
1055 * Running a Program with Multiple Units::
1056 * Using the gnatmake Utility::
1058 * Editing with Emacs::
1061 * Introduction to GPS::
1066 @section Running GNAT
1069 Three steps are needed to create an executable file from an Ada source
1074 The source file(s) must be compiled.
1076 The file(s) must be bound using the GNAT binder.
1078 All appropriate object files must be linked to produce an executable.
1082 All three steps are most commonly handled by using the @command{gnatmake}
1083 utility program that, given the name of the main program, automatically
1084 performs the necessary compilation, binding and linking steps.
1086 @node Running a Simple Ada Program
1087 @section Running a Simple Ada Program
1090 Any text editor may be used to prepare an Ada program.
1092 used, the optional Ada mode may be helpful in laying out the program.)
1094 program text is a normal text file. We will assume in our initial
1095 example that you have used your editor to prepare the following
1096 standard format text file:
1098 @smallexample @c ada
1100 with Ada.Text_IO; use Ada.Text_IO;
1103 Put_Line ("Hello WORLD!");
1109 This file should be named @file{hello.adb}.
1110 With the normal default file naming conventions, GNAT requires
1112 contain a single compilation unit whose file name is the
1114 with periods replaced by hyphens; the
1115 extension is @file{ads} for a
1116 spec and @file{adb} for a body.
1117 You can override this default file naming convention by use of the
1118 special pragma @code{Source_File_Name} (@pxref{Using Other File Names}).
1119 Alternatively, if you want to rename your files according to this default
1120 convention, which is probably more convenient if you will be using GNAT
1121 for all your compilations, then the @code{gnatchop} utility
1122 can be used to generate correctly-named source files
1123 (@pxref{Renaming Files Using gnatchop}).
1125 You can compile the program using the following command (@code{$} is used
1126 as the command prompt in the examples in this document):
1133 @command{gcc} is the command used to run the compiler. This compiler is
1134 capable of compiling programs in several languages, including Ada and
1135 C. It assumes that you have given it an Ada program if the file extension is
1136 either @file{.ads} or @file{.adb}, and it will then call
1137 the GNAT compiler to compile the specified file.
1140 The @option{-c} switch is required. It tells @command{gcc} to only do a
1141 compilation. (For C programs, @command{gcc} can also do linking, but this
1142 capability is not used directly for Ada programs, so the @option{-c}
1143 switch must always be present.)
1146 This compile command generates a file
1147 @file{hello.o}, which is the object
1148 file corresponding to your Ada program. It also generates
1149 an ``Ada Library Information'' file @file{hello.ali},
1150 which contains additional information used to check
1151 that an Ada program is consistent.
1152 To build an executable file,
1153 use @code{gnatbind} to bind the program
1154 and @command{gnatlink} to link it. The
1155 argument to both @code{gnatbind} and @command{gnatlink} is the name of the
1156 @file{ALI} file, but the default extension of @file{.ali} can
1157 be omitted. This means that in the most common case, the argument
1158 is simply the name of the main program:
1166 A simpler method of carrying out these steps is to use
1168 a master program that invokes all the required
1169 compilation, binding and linking tools in the correct order. In particular,
1170 @command{gnatmake} automatically recompiles any sources that have been
1171 modified since they were last compiled, or sources that depend
1172 on such modified sources, so that ``version skew'' is avoided.
1173 @cindex Version skew (avoided by @command{gnatmake})
1176 $ gnatmake hello.adb
1180 The result is an executable program called @file{hello}, which can be
1188 assuming that the current directory is on the search path
1189 for executable programs.
1192 and, if all has gone well, you will see
1199 appear in response to this command.
1201 @c ****************************************
1202 @node Running a Program with Multiple Units
1203 @section Running a Program with Multiple Units
1206 Consider a slightly more complicated example that has three files: a
1207 main program, and the spec and body of a package:
1209 @smallexample @c ada
1212 package Greetings is
1217 with Ada.Text_IO; use Ada.Text_IO;
1218 package body Greetings is
1221 Put_Line ("Hello WORLD!");
1224 procedure Goodbye is
1226 Put_Line ("Goodbye WORLD!");
1243 Following the one-unit-per-file rule, place this program in the
1244 following three separate files:
1248 spec of package @code{Greetings}
1251 body of package @code{Greetings}
1254 body of main program
1258 To build an executable version of
1259 this program, we could use four separate steps to compile, bind, and link
1260 the program, as follows:
1264 $ gcc -c greetings.adb
1270 Note that there is no required order of compilation when using GNAT.
1271 In particular it is perfectly fine to compile the main program first.
1272 Also, it is not necessary to compile package specs in the case where
1273 there is an accompanying body; you only need to compile the body. If you want
1274 to submit these files to the compiler for semantic checking and not code
1275 generation, then use the
1276 @option{-gnatc} switch:
1279 $ gcc -c greetings.ads -gnatc
1283 Although the compilation can be done in separate steps as in the
1284 above example, in practice it is almost always more convenient
1285 to use the @command{gnatmake} tool. All you need to know in this case
1286 is the name of the main program's source file. The effect of the above four
1287 commands can be achieved with a single one:
1290 $ gnatmake gmain.adb
1294 In the next section we discuss the advantages of using @command{gnatmake} in
1297 @c *****************************
1298 @node Using the gnatmake Utility
1299 @section Using the @command{gnatmake} Utility
1302 If you work on a program by compiling single components at a time using
1303 @command{gcc}, you typically keep track of the units you modify. In order to
1304 build a consistent system, you compile not only these units, but also any
1305 units that depend on the units you have modified.
1306 For example, in the preceding case,
1307 if you edit @file{gmain.adb}, you only need to recompile that file. But if
1308 you edit @file{greetings.ads}, you must recompile both
1309 @file{greetings.adb} and @file{gmain.adb}, because both files contain
1310 units that depend on @file{greetings.ads}.
1312 @code{gnatbind} will warn you if you forget one of these compilation
1313 steps, so that it is impossible to generate an inconsistent program as a
1314 result of forgetting to do a compilation. Nevertheless it is tedious and
1315 error-prone to keep track of dependencies among units.
1316 One approach to handle the dependency-bookkeeping is to use a
1317 makefile. However, makefiles present maintenance problems of their own:
1318 if the dependencies change as you change the program, you must make
1319 sure that the makefile is kept up-to-date manually, which is also an
1320 error-prone process.
1322 The @command{gnatmake} utility takes care of these details automatically.
1323 Invoke it using either one of the following forms:
1326 $ gnatmake gmain.adb
1327 $ gnatmake ^gmain^GMAIN^
1331 The argument is the name of the file containing the main program;
1332 you may omit the extension. @command{gnatmake}
1333 examines the environment, automatically recompiles any files that need
1334 recompiling, and binds and links the resulting set of object files,
1335 generating the executable file, @file{^gmain^GMAIN.EXE^}.
1336 In a large program, it
1337 can be extremely helpful to use @command{gnatmake}, because working out by hand
1338 what needs to be recompiled can be difficult.
1340 Note that @command{gnatmake}
1341 takes into account all the Ada rules that
1342 establish dependencies among units. These include dependencies that result
1343 from inlining subprogram bodies, and from
1344 generic instantiation. Unlike some other
1345 Ada make tools, @command{gnatmake} does not rely on the dependencies that were
1346 found by the compiler on a previous compilation, which may possibly
1347 be wrong when sources change. @command{gnatmake} determines the exact set of
1348 dependencies from scratch each time it is run.
1351 @node Editing with Emacs
1352 @section Editing with Emacs
1356 Emacs is an extensible self-documenting text editor that is available in a
1357 separate VMSINSTAL kit.
1359 Invoke Emacs by typing @kbd{Emacs} at the command prompt. To get started,
1360 click on the Emacs Help menu and run the Emacs Tutorial.
1361 In a character cell terminal, Emacs help is invoked with @kbd{Ctrl-h} (also
1362 written as @kbd{C-h}), and the tutorial by @kbd{C-h t}.
1364 Documentation on Emacs and other tools is available in Emacs under the
1365 pull-down menu button: @code{Help - Info}. After selecting @code{Info},
1366 use the middle mouse button to select a topic (e.g.@: Emacs).
1368 In a character cell terminal, do @kbd{C-h i} to invoke info, and then @kbd{m}
1369 (stands for menu) followed by the menu item desired, as in @kbd{m Emacs}, to
1370 get to the Emacs manual.
1371 Help on Emacs is also available by typing @kbd{HELP EMACS} at the DCL command
1374 The tutorial is highly recommended in order to learn the intricacies of Emacs,
1375 which is sufficiently extensible to provide for a complete programming
1376 environment and shell for the sophisticated user.
1380 @node Introduction to GPS
1381 @section Introduction to GPS
1382 @cindex GPS (GNAT Programming Studio)
1383 @cindex GNAT Programming Studio (GPS)
1385 Although the command line interface (@command{gnatmake}, etc.) alone
1386 is sufficient, a graphical Interactive Development
1387 Environment can make it easier for you to compose, navigate, and debug
1388 programs. This section describes the main features of GPS
1389 (``GNAT Programming Studio''), the GNAT graphical IDE.
1390 You will see how to use GPS to build and debug an executable, and
1391 you will also learn some of the basics of the GNAT ``project'' facility.
1393 GPS enables you to do much more than is presented here;
1394 e.g., you can produce a call graph, interface to a third-party
1395 Version Control System, and inspect the generated assembly language
1397 Indeed, GPS also supports languages other than Ada.
1398 Such additional information, and an explanation of all of the GPS menu
1399 items. may be found in the on-line help, which includes
1400 a user's guide and a tutorial (these are also accessible from the GNAT
1404 * Building a New Program with GPS::
1405 * Simple Debugging with GPS::
1408 @node Building a New Program with GPS
1409 @subsection Building a New Program with GPS
1411 GPS invokes the GNAT compilation tools using information
1412 contained in a @emph{project} (also known as a @emph{project file}):
1413 a collection of properties such
1414 as source directories, identities of main subprograms, tool switches, etc.,
1415 and their associated values.
1416 See @ref{GNAT Project Manager} for details.
1417 In order to run GPS, you will need to either create a new project
1418 or else open an existing one.
1420 This section will explain how you can use GPS to create a project,
1421 to associate Ada source files with a project, and to build and run
1425 @item @emph{Creating a project}
1427 Invoke GPS, either from the command line or the platform's IDE.
1428 After it starts, GPS will display a ``Welcome'' screen with three
1433 @code{Start with default project in directory}
1436 @code{Create new project with wizard}
1439 @code{Open existing project}
1443 Select @code{Create new project with wizard} and press @code{OK}.
1444 A new window will appear. In the text box labeled with
1445 @code{Enter the name of the project to create}, type @file{sample}
1446 as the project name.
1447 In the next box, browse to choose the directory in which you
1448 would like to create the project file.
1449 After selecting an appropriate directory, press @code{Forward}.
1451 A window will appear with the title
1452 @code{Version Control System Configuration}.
1453 Simply press @code{Forward}.
1455 A window will appear with the title
1456 @code{Please select the source directories for this project}.
1457 The directory that you specified for the project file will be selected
1458 by default as the one to use for sources; simply press @code{Forward}.
1460 A window will appear with the title
1461 @code{Please select the build directory for this project}.
1462 The directory that you specified for the project file will be selected
1463 by default for object files and executables;
1464 simply press @code{Forward}.
1466 A window will appear with the title
1467 @code{Please select the main units for this project}.
1468 You will supply this information later, after creating the source file.
1469 Simply press @code{Forward} for now.
1471 A window will appear with the title
1472 @code{Please select the switches to build the project}.
1473 Press @code{Apply}. This will create a project file named
1474 @file{sample.prj} in the directory that you had specified.
1476 @item @emph{Creating and saving the source file}
1478 After you create the new project, a GPS window will appear, which is
1479 partitioned into two main sections:
1483 A @emph{Workspace area}, initially greyed out, which you will use for
1484 creating and editing source files
1487 Directly below, a @emph{Messages area}, which initially displays a
1488 ``Welcome'' message.
1489 (If the Messages area is not visible, drag its border upward to expand it.)
1493 Select @code{File} on the menu bar, and then the @code{New} command.
1494 The Workspace area will become white, and you can now
1495 enter the source program explicitly.
1496 Type the following text
1498 @smallexample @c ada
1500 with Ada.Text_IO; use Ada.Text_IO;
1503 Put_Line("Hello from GPS!");
1509 Select @code{File}, then @code{Save As}, and enter the source file name
1511 The file will be saved in the same directory you specified as the
1512 location of the default project file.
1514 @item @emph{Updating the project file}
1516 You need to add the new source file to the project.
1518 the @code{Project} menu and then @code{Edit project properties}.
1519 Click the @code{Main files} tab on the left, and then the
1521 Choose @file{hello.adb} from the list, and press @code{Open}.
1522 The project settings window will reflect this action.
1525 @item @emph{Building and running the program}
1527 In the main GPS window, now choose the @code{Build} menu, then @code{Make},
1528 and select @file{hello.adb}.
1529 The Messages window will display the resulting invocations of @command{gcc},
1530 @command{gnatbind}, and @command{gnatlink}
1531 (reflecting the default switch settings from the
1532 project file that you created) and then a ``successful compilation/build''
1535 To run the program, choose the @code{Build} menu, then @code{Run}, and
1536 select @command{hello}.
1537 An @emph{Arguments Selection} window will appear.
1538 There are no command line arguments, so just click @code{OK}.
1540 The Messages window will now display the program's output (the string
1541 @code{Hello from GPS}), and at the bottom of the GPS window a status
1542 update is displayed (@code{Run: hello}).
1543 Close the GPS window (or select @code{File}, then @code{Exit}) to
1544 terminate this GPS session.
1547 @node Simple Debugging with GPS
1548 @subsection Simple Debugging with GPS
1550 This section illustrates basic debugging techniques (setting breakpoints,
1551 examining/modifying variables, single stepping).
1554 @item @emph{Opening a project}
1556 Start GPS and select @code{Open existing project}; browse to
1557 specify the project file @file{sample.prj} that you had created in the
1560 @item @emph{Creating a source file}
1562 Select @code{File}, then @code{New}, and type in the following program:
1564 @smallexample @c ada
1566 with Ada.Text_IO; use Ada.Text_IO;
1567 procedure Example is
1568 Line : String (1..80);
1571 Put_Line("Type a line of text at each prompt; an empty line to exit");
1575 Put_Line (Line (1..N) );
1583 Select @code{File}, then @code{Save as}, and enter the file name
1586 @item @emph{Updating the project file}
1588 Add @code{Example} as a new main unit for the project:
1591 Select @code{Project}, then @code{Edit Project Properties}.
1594 Select the @code{Main files} tab, click @code{Add}, then
1595 select the file @file{example.adb} from the list, and
1597 You will see the file name appear in the list of main units
1603 @item @emph{Building/running the executable}
1605 To build the executable
1606 select @code{Build}, then @code{Make}, and then choose @file{example.adb}.
1608 Run the program to see its effect (in the Messages area).
1609 Each line that you enter is displayed; an empty line will
1610 cause the loop to exit and the program to terminate.
1612 @item @emph{Debugging the program}
1614 Note that the @option{-g} switches to @command{gcc} and @command{gnatlink},
1615 which are required for debugging, are on by default when you create
1617 Thus unless you intentionally remove these settings, you will be able
1618 to debug any program that you develop using GPS.
1621 @item @emph{Initializing}
1623 Select @code{Debug}, then @code{Initialize}, then @file{example}
1625 @item @emph{Setting a breakpoint}
1627 After performing the initialization step, you will observe a small
1628 icon to the right of each line number.
1629 This serves as a toggle for breakpoints; clicking the icon will
1630 set a breakpoint at the corresponding line (the icon will change to
1631 a red circle with an ``x''), and clicking it again
1632 will remove the breakpoint / reset the icon.
1634 For purposes of this example, set a breakpoint at line 10 (the
1635 statement @code{Put_Line@ (Line@ (1..N));}
1637 @item @emph{Starting program execution}
1639 Select @code{Debug}, then @code{Run}. When the
1640 @code{Program Arguments} window appears, click @code{OK}.
1641 A console window will appear; enter some line of text,
1642 e.g.@: @code{abcde}, at the prompt.
1643 The program will pause execution when it gets to the
1644 breakpoint, and the corresponding line is highlighted.
1646 @item @emph{Examining a variable}
1648 Move the mouse over one of the occurrences of the variable @code{N}.
1649 You will see the value (5) displayed, in ``tool tip'' fashion.
1650 Right click on @code{N}, select @code{Debug}, then select @code{Display N}.
1651 You will see information about @code{N} appear in the @code{Debugger Data}
1652 pane, showing the value as 5.
1654 @item @emph{Assigning a new value to a variable}
1656 Right click on the @code{N} in the @code{Debugger Data} pane, and
1657 select @code{Set value of N}.
1658 When the input window appears, enter the value @code{4} and click
1660 This value does not automatically appear in the @code{Debugger Data}
1661 pane; to see it, right click again on the @code{N} in the
1662 @code{Debugger Data} pane and select @code{Update value}.
1663 The new value, 4, will appear in red.
1665 @item @emph{Single stepping}
1667 Select @code{Debug}, then @code{Next}.
1668 This will cause the next statement to be executed, in this case the
1669 call of @code{Put_Line} with the string slice.
1670 Notice in the console window that the displayed string is simply
1671 @code{abcd} and not @code{abcde} which you had entered.
1672 This is because the upper bound of the slice is now 4 rather than 5.
1674 @item @emph{Removing a breakpoint}
1676 Toggle the breakpoint icon at line 10.
1678 @item @emph{Resuming execution from a breakpoint}
1680 Select @code{Debug}, then @code{Continue}.
1681 The program will reach the next iteration of the loop, and
1682 wait for input after displaying the prompt.
1683 This time, just hit the @kbd{Enter} key.
1684 The value of @code{N} will be 0, and the program will terminate.
1685 The console window will disappear.
1690 @node The GNAT Compilation Model
1691 @chapter The GNAT Compilation Model
1692 @cindex GNAT compilation model
1693 @cindex Compilation model
1696 * Source Representation::
1697 * Foreign Language Representation::
1698 * File Naming Rules::
1699 * Using Other File Names::
1700 * Alternative File Naming Schemes::
1701 * Generating Object Files::
1702 * Source Dependencies::
1703 * The Ada Library Information Files::
1704 * Binding an Ada Program::
1705 * Mixed Language Programming::
1707 * Building Mixed Ada & C++ Programs::
1708 * Comparison between GNAT and C/C++ Compilation Models::
1710 * Comparison between GNAT and Conventional Ada Library Models::
1712 * Placement of temporary files::
1717 This chapter describes the compilation model used by GNAT. Although
1718 similar to that used by other languages, such as C and C++, this model
1719 is substantially different from the traditional Ada compilation models,
1720 which are based on a library. The model is initially described without
1721 reference to the library-based model. If you have not previously used an
1722 Ada compiler, you need only read the first part of this chapter. The
1723 last section describes and discusses the differences between the GNAT
1724 model and the traditional Ada compiler models. If you have used other
1725 Ada compilers, this section will help you to understand those
1726 differences, and the advantages of the GNAT model.
1728 @node Source Representation
1729 @section Source Representation
1733 Ada source programs are represented in standard text files, using
1734 Latin-1 coding. Latin-1 is an 8-bit code that includes the familiar
1735 7-bit ASCII set, plus additional characters used for
1736 representing foreign languages (@pxref{Foreign Language Representation}
1737 for support of non-USA character sets). The format effector characters
1738 are represented using their standard ASCII encodings, as follows:
1743 Vertical tab, @code{16#0B#}
1747 Horizontal tab, @code{16#09#}
1751 Carriage return, @code{16#0D#}
1755 Line feed, @code{16#0A#}
1759 Form feed, @code{16#0C#}
1763 Source files are in standard text file format. In addition, GNAT will
1764 recognize a wide variety of stream formats, in which the end of
1765 physical lines is marked by any of the following sequences:
1766 @code{LF}, @code{CR}, @code{CR-LF}, or @code{LF-CR}. This is useful
1767 in accommodating files that are imported from other operating systems.
1769 @cindex End of source file
1770 @cindex Source file, end
1772 The end of a source file is normally represented by the physical end of
1773 file. However, the control character @code{16#1A#} (@code{SUB}) is also
1774 recognized as signalling the end of the source file. Again, this is
1775 provided for compatibility with other operating systems where this
1776 code is used to represent the end of file.
1778 Each file contains a single Ada compilation unit, including any pragmas
1779 associated with the unit. For example, this means you must place a
1780 package declaration (a package @dfn{spec}) and the corresponding body in
1781 separate files. An Ada @dfn{compilation} (which is a sequence of
1782 compilation units) is represented using a sequence of files. Similarly,
1783 you will place each subunit or child unit in a separate file.
1785 @node Foreign Language Representation
1786 @section Foreign Language Representation
1789 GNAT supports the standard character sets defined in Ada as well as
1790 several other non-standard character sets for use in localized versions
1791 of the compiler (@pxref{Character Set Control}).
1794 * Other 8-Bit Codes::
1795 * Wide Character Encodings::
1803 The basic character set is Latin-1. This character set is defined by ISO
1804 standard 8859, part 1. The lower half (character codes @code{16#00#}
1805 @dots{} @code{16#7F#)} is identical to standard ASCII coding, but the upper half
1806 is used to represent additional characters. These include extended letters
1807 used by European languages, such as French accents, the vowels with umlauts
1808 used in German, and the extra letter A-ring used in Swedish.
1810 @findex Ada.Characters.Latin_1
1811 For a complete list of Latin-1 codes and their encodings, see the source
1812 file of library unit @code{Ada.Characters.Latin_1} in file
1813 @file{a-chlat1.ads}.
1814 You may use any of these extended characters freely in character or
1815 string literals. In addition, the extended characters that represent
1816 letters can be used in identifiers.
1818 @node Other 8-Bit Codes
1819 @subsection Other 8-Bit Codes
1822 GNAT also supports several other 8-bit coding schemes:
1825 @item ISO 8859-2 (Latin-2)
1828 Latin-2 letters allowed in identifiers, with uppercase and lowercase
1831 @item ISO 8859-3 (Latin-3)
1834 Latin-3 letters allowed in identifiers, with uppercase and lowercase
1837 @item ISO 8859-4 (Latin-4)
1840 Latin-4 letters allowed in identifiers, with uppercase and lowercase
1843 @item ISO 8859-5 (Cyrillic)
1846 ISO 8859-5 letters (Cyrillic) allowed in identifiers, with uppercase and
1847 lowercase equivalence.
1849 @item ISO 8859-15 (Latin-9)
1852 ISO 8859-15 (Latin-9) letters allowed in identifiers, with uppercase and
1853 lowercase equivalence
1855 @item IBM PC (code page 437)
1856 @cindex code page 437
1857 This code page is the normal default for PCs in the U.S. It corresponds
1858 to the original IBM PC character set. This set has some, but not all, of
1859 the extended Latin-1 letters, but these letters do not have the same
1860 encoding as Latin-1. In this mode, these letters are allowed in
1861 identifiers with uppercase and lowercase equivalence.
1863 @item IBM PC (code page 850)
1864 @cindex code page 850
1865 This code page is a modification of 437 extended to include all the
1866 Latin-1 letters, but still not with the usual Latin-1 encoding. In this
1867 mode, all these letters are allowed in identifiers with uppercase and
1868 lowercase equivalence.
1870 @item Full Upper 8-bit
1871 Any character in the range 80-FF allowed in identifiers, and all are
1872 considered distinct. In other words, there are no uppercase and lowercase
1873 equivalences in this range. This is useful in conjunction with
1874 certain encoding schemes used for some foreign character sets (e.g.,
1875 the typical method of representing Chinese characters on the PC).
1878 No upper-half characters in the range 80-FF are allowed in identifiers.
1879 This gives Ada 83 compatibility for identifier names.
1883 For precise data on the encodings permitted, and the uppercase and lowercase
1884 equivalences that are recognized, see the file @file{csets.adb} in
1885 the GNAT compiler sources. You will need to obtain a full source release
1886 of GNAT to obtain this file.
1888 @node Wide Character Encodings
1889 @subsection Wide Character Encodings
1892 GNAT allows wide character codes to appear in character and string
1893 literals, and also optionally in identifiers, by means of the following
1894 possible encoding schemes:
1899 In this encoding, a wide character is represented by the following five
1907 Where @code{a}, @code{b}, @code{c}, @code{d} are the four hexadecimal
1908 characters (using uppercase letters) of the wide character code. For
1909 example, ESC A345 is used to represent the wide character with code
1911 This scheme is compatible with use of the full Wide_Character set.
1913 @item Upper-Half Coding
1914 @cindex Upper-Half Coding
1915 The wide character with encoding @code{16#abcd#} where the upper bit is on
1916 (in other words, ``a'' is in the range 8-F) is represented as two bytes,
1917 @code{16#ab#} and @code{16#cd#}. The second byte cannot be a format control
1918 character, but is not required to be in the upper half. This method can
1919 be also used for shift-JIS or EUC, where the internal coding matches the
1922 @item Shift JIS Coding
1923 @cindex Shift JIS Coding
1924 A wide character is represented by a two-character sequence,
1926 @code{16#cd#}, with the restrictions described for upper-half encoding as
1927 described above. The internal character code is the corresponding JIS
1928 character according to the standard algorithm for Shift-JIS
1929 conversion. Only characters defined in the JIS code set table can be
1930 used with this encoding method.
1934 A wide character is represented by a two-character sequence
1936 @code{16#cd#}, with both characters being in the upper half. The internal
1937 character code is the corresponding JIS character according to the EUC
1938 encoding algorithm. Only characters defined in the JIS code set table
1939 can be used with this encoding method.
1942 A wide character is represented using
1943 UCS Transformation Format 8 (UTF-8) as defined in Annex R of ISO
1944 10646-1/Am.2. Depending on the character value, the representation
1945 is a one, two, or three byte sequence:
1950 16#0000#-16#007f#: 2#0@var{xxxxxxx}#
1951 16#0080#-16#07ff#: 2#110@var{xxxxx}# 2#10@var{xxxxxx}#
1952 16#0800#-16#ffff#: 2#1110@var{xxxx}# 2#10@var{xxxxxx}# 2#10@var{xxxxxx}#
1957 where the @var{xxx} bits correspond to the left-padded bits of the
1958 16-bit character value. Note that all lower half ASCII characters
1959 are represented as ASCII bytes and all upper half characters and
1960 other wide characters are represented as sequences of upper-half
1961 (The full UTF-8 scheme allows for encoding 31-bit characters as
1962 6-byte sequences, but in this implementation, all UTF-8 sequences
1963 of four or more bytes length will be treated as illegal).
1964 @item Brackets Coding
1965 In this encoding, a wide character is represented by the following eight
1973 Where @code{a}, @code{b}, @code{c}, @code{d} are the four hexadecimal
1974 characters (using uppercase letters) of the wide character code. For
1975 example, [``A345''] is used to represent the wide character with code
1976 @code{16#A345#}. It is also possible (though not required) to use the
1977 Brackets coding for upper half characters. For example, the code
1978 @code{16#A3#} can be represented as @code{[``A3'']}.
1980 This scheme is compatible with use of the full Wide_Character set,
1981 and is also the method used for wide character encoding in the standard
1982 ACVC (Ada Compiler Validation Capability) test suite distributions.
1987 Note: Some of these coding schemes do not permit the full use of the
1988 Ada character set. For example, neither Shift JIS, nor EUC allow the
1989 use of the upper half of the Latin-1 set.
1991 @node File Naming Rules
1992 @section File Naming Rules
1995 The default file name is determined by the name of the unit that the
1996 file contains. The name is formed by taking the full expanded name of
1997 the unit and replacing the separating dots with hyphens and using
1998 ^lowercase^uppercase^ for all letters.
2000 An exception arises if the file name generated by the above rules starts
2001 with one of the characters
2003 @samp{A}, @samp{G}, @samp{I}, or @samp{S},
2006 @samp{a}, @samp{g}, @samp{i}, or @samp{s},
2008 and the second character is a
2009 minus. In this case, the character ^tilde^dollar sign^ is used in place
2010 of the minus. The reason for this special rule is to avoid clashes with
2011 the standard names for child units of the packages System, Ada,
2012 Interfaces, and GNAT, which use the prefixes
2014 @samp{S-}, @samp{A-}, @samp{I-}, and @samp{G-},
2017 @samp{s-}, @samp{a-}, @samp{i-}, and @samp{g-},
2021 The file extension is @file{.ads} for a spec and
2022 @file{.adb} for a body. The following list shows some
2023 examples of these rules.
2030 @item arith_functions.ads
2031 Arith_Functions (package spec)
2032 @item arith_functions.adb
2033 Arith_Functions (package body)
2035 Func.Spec (child package spec)
2037 Func.Spec (child package body)
2039 Sub (subunit of Main)
2040 @item ^a~bad.adb^A$BAD.ADB^
2041 A.Bad (child package body)
2045 Following these rules can result in excessively long
2046 file names if corresponding
2047 unit names are long (for example, if child units or subunits are
2048 heavily nested). An option is available to shorten such long file names
2049 (called file name ``krunching''). This may be particularly useful when
2050 programs being developed with GNAT are to be used on operating systems
2051 with limited file name lengths. @xref{Using gnatkr}.
2053 Of course, no file shortening algorithm can guarantee uniqueness over
2054 all possible unit names; if file name krunching is used, it is your
2055 responsibility to ensure no name clashes occur. Alternatively you
2056 can specify the exact file names that you want used, as described
2057 in the next section. Finally, if your Ada programs are migrating from a
2058 compiler with a different naming convention, you can use the gnatchop
2059 utility to produce source files that follow the GNAT naming conventions.
2060 (For details @pxref{Renaming Files Using gnatchop}.)
2062 Note: in the case of @code{Windows NT/XP} or @code{OpenVMS} operating
2063 systems, case is not significant. So for example on @code{Windows XP}
2064 if the canonical name is @code{main-sub.adb}, you can use the file name
2065 @code{Main-Sub.adb} instead. However, case is significant for other
2066 operating systems, so for example, if you want to use other than
2067 canonically cased file names on a Unix system, you need to follow
2068 the procedures described in the next section.
2070 @node Using Other File Names
2071 @section Using Other File Names
2075 In the previous section, we have described the default rules used by
2076 GNAT to determine the file name in which a given unit resides. It is
2077 often convenient to follow these default rules, and if you follow them,
2078 the compiler knows without being explicitly told where to find all
2081 However, in some cases, particularly when a program is imported from
2082 another Ada compiler environment, it may be more convenient for the
2083 programmer to specify which file names contain which units. GNAT allows
2084 arbitrary file names to be used by means of the Source_File_Name pragma.
2085 The form of this pragma is as shown in the following examples:
2086 @cindex Source_File_Name pragma
2088 @smallexample @c ada
2090 pragma Source_File_Name (My_Utilities.Stacks,
2091 Spec_File_Name => "myutilst_a.ada");
2092 pragma Source_File_name (My_Utilities.Stacks,
2093 Body_File_Name => "myutilst.ada");
2098 As shown in this example, the first argument for the pragma is the unit
2099 name (in this example a child unit). The second argument has the form
2100 of a named association. The identifier
2101 indicates whether the file name is for a spec or a body;
2102 the file name itself is given by a string literal.
2104 The source file name pragma is a configuration pragma, which means that
2105 normally it will be placed in the @file{gnat.adc}
2106 file used to hold configuration
2107 pragmas that apply to a complete compilation environment.
2108 For more details on how the @file{gnat.adc} file is created and used
2109 see @ref{Handling of Configuration Pragmas}.
2110 @cindex @file{gnat.adc}
2113 GNAT allows completely arbitrary file names to be specified using the
2114 source file name pragma. However, if the file name specified has an
2115 extension other than @file{.ads} or @file{.adb} it is necessary to use
2116 a special syntax when compiling the file. The name in this case must be
2117 preceded by the special sequence @option{-x} followed by a space and the name
2118 of the language, here @code{ada}, as in:
2121 $ gcc -c -x ada peculiar_file_name.sim
2126 @command{gnatmake} handles non-standard file names in the usual manner (the
2127 non-standard file name for the main program is simply used as the
2128 argument to gnatmake). Note that if the extension is also non-standard,
2129 then it must be included in the @command{gnatmake} command, it may not
2132 @node Alternative File Naming Schemes
2133 @section Alternative File Naming Schemes
2134 @cindex File naming schemes, alternative
2137 In the previous section, we described the use of the @code{Source_File_Name}
2138 pragma to allow arbitrary names to be assigned to individual source files.
2139 However, this approach requires one pragma for each file, and especially in
2140 large systems can result in very long @file{gnat.adc} files, and also create
2141 a maintenance problem.
2143 GNAT also provides a facility for specifying systematic file naming schemes
2144 other than the standard default naming scheme previously described. An
2145 alternative scheme for naming is specified by the use of
2146 @code{Source_File_Name} pragmas having the following format:
2147 @cindex Source_File_Name pragma
2149 @smallexample @c ada
2150 pragma Source_File_Name (
2151 Spec_File_Name => FILE_NAME_PATTERN
2152 @r{[},Casing => CASING_SPEC@r{]}
2153 @r{[},Dot_Replacement => STRING_LITERAL@r{]});
2155 pragma Source_File_Name (
2156 Body_File_Name => FILE_NAME_PATTERN
2157 @r{[},Casing => CASING_SPEC@r{]}
2158 @r{[},Dot_Replacement => STRING_LITERAL@r{]});
2160 pragma Source_File_Name (
2161 Subunit_File_Name => FILE_NAME_PATTERN
2162 @r{[},Casing => CASING_SPEC@r{]}
2163 @r{[},Dot_Replacement => STRING_LITERAL@r{]});
2165 FILE_NAME_PATTERN ::= STRING_LITERAL
2166 CASING_SPEC ::= Lowercase | Uppercase | Mixedcase
2170 The @code{FILE_NAME_PATTERN} string shows how the file name is constructed.
2171 It contains a single asterisk character, and the unit name is substituted
2172 systematically for this asterisk. The optional parameter
2173 @code{Casing} indicates
2174 whether the unit name is to be all upper-case letters, all lower-case letters,
2175 or mixed-case. If no
2176 @code{Casing} parameter is used, then the default is all
2177 ^lower-case^upper-case^.
2179 The optional @code{Dot_Replacement} string is used to replace any periods
2180 that occur in subunit or child unit names. If no @code{Dot_Replacement}
2181 argument is used then separating dots appear unchanged in the resulting
2183 Although the above syntax indicates that the
2184 @code{Casing} argument must appear
2185 before the @code{Dot_Replacement} argument, but it
2186 is also permissible to write these arguments in the opposite order.
2188 As indicated, it is possible to specify different naming schemes for
2189 bodies, specs, and subunits. Quite often the rule for subunits is the
2190 same as the rule for bodies, in which case, there is no need to give
2191 a separate @code{Subunit_File_Name} rule, and in this case the
2192 @code{Body_File_name} rule is used for subunits as well.
2194 The separate rule for subunits can also be used to implement the rather
2195 unusual case of a compilation environment (e.g.@: a single directory) which
2196 contains a subunit and a child unit with the same unit name. Although
2197 both units cannot appear in the same partition, the Ada Reference Manual
2198 allows (but does not require) the possibility of the two units coexisting
2199 in the same environment.
2201 The file name translation works in the following steps:
2206 If there is a specific @code{Source_File_Name} pragma for the given unit,
2207 then this is always used, and any general pattern rules are ignored.
2210 If there is a pattern type @code{Source_File_Name} pragma that applies to
2211 the unit, then the resulting file name will be used if the file exists. If
2212 more than one pattern matches, the latest one will be tried first, and the
2213 first attempt resulting in a reference to a file that exists will be used.
2216 If no pattern type @code{Source_File_Name} pragma that applies to the unit
2217 for which the corresponding file exists, then the standard GNAT default
2218 naming rules are used.
2223 As an example of the use of this mechanism, consider a commonly used scheme
2224 in which file names are all lower case, with separating periods copied
2225 unchanged to the resulting file name, and specs end with @file{.1.ada}, and
2226 bodies end with @file{.2.ada}. GNAT will follow this scheme if the following
2229 @smallexample @c ada
2230 pragma Source_File_Name
2231 (Spec_File_Name => "*.1.ada");
2232 pragma Source_File_Name
2233 (Body_File_Name => "*.2.ada");
2237 The default GNAT scheme is actually implemented by providing the following
2238 default pragmas internally:
2240 @smallexample @c ada
2241 pragma Source_File_Name
2242 (Spec_File_Name => "*.ads", Dot_Replacement => "-");
2243 pragma Source_File_Name
2244 (Body_File_Name => "*.adb", Dot_Replacement => "-");
2248 Our final example implements a scheme typically used with one of the
2249 Ada 83 compilers, where the separator character for subunits was ``__''
2250 (two underscores), specs were identified by adding @file{_.ADA}, bodies
2251 by adding @file{.ADA}, and subunits by
2252 adding @file{.SEP}. All file names were
2253 upper case. Child units were not present of course since this was an
2254 Ada 83 compiler, but it seems reasonable to extend this scheme to use
2255 the same double underscore separator for child units.
2257 @smallexample @c ada
2258 pragma Source_File_Name
2259 (Spec_File_Name => "*_.ADA",
2260 Dot_Replacement => "__",
2261 Casing = Uppercase);
2262 pragma Source_File_Name
2263 (Body_File_Name => "*.ADA",
2264 Dot_Replacement => "__",
2265 Casing = Uppercase);
2266 pragma Source_File_Name
2267 (Subunit_File_Name => "*.SEP",
2268 Dot_Replacement => "__",
2269 Casing = Uppercase);
2272 @node Generating Object Files
2273 @section Generating Object Files
2276 An Ada program consists of a set of source files, and the first step in
2277 compiling the program is to generate the corresponding object files.
2278 These are generated by compiling a subset of these source files.
2279 The files you need to compile are the following:
2283 If a package spec has no body, compile the package spec to produce the
2284 object file for the package.
2287 If a package has both a spec and a body, compile the body to produce the
2288 object file for the package. The source file for the package spec need
2289 not be compiled in this case because there is only one object file, which
2290 contains the code for both the spec and body of the package.
2293 For a subprogram, compile the subprogram body to produce the object file
2294 for the subprogram. The spec, if one is present, is as usual in a
2295 separate file, and need not be compiled.
2299 In the case of subunits, only compile the parent unit. A single object
2300 file is generated for the entire subunit tree, which includes all the
2304 Compile child units independently of their parent units
2305 (though, of course, the spec of all the ancestor unit must be present in order
2306 to compile a child unit).
2310 Compile generic units in the same manner as any other units. The object
2311 files in this case are small dummy files that contain at most the
2312 flag used for elaboration checking. This is because GNAT always handles generic
2313 instantiation by means of macro expansion. However, it is still necessary to
2314 compile generic units, for dependency checking and elaboration purposes.
2318 The preceding rules describe the set of files that must be compiled to
2319 generate the object files for a program. Each object file has the same
2320 name as the corresponding source file, except that the extension is
2323 You may wish to compile other files for the purpose of checking their
2324 syntactic and semantic correctness. For example, in the case where a
2325 package has a separate spec and body, you would not normally compile the
2326 spec. However, it is convenient in practice to compile the spec to make
2327 sure it is error-free before compiling clients of this spec, because such
2328 compilations will fail if there is an error in the spec.
2330 GNAT provides an option for compiling such files purely for the
2331 purposes of checking correctness; such compilations are not required as
2332 part of the process of building a program. To compile a file in this
2333 checking mode, use the @option{-gnatc} switch.
2335 @node Source Dependencies
2336 @section Source Dependencies
2339 A given object file clearly depends on the source file which is compiled
2340 to produce it. Here we are using @dfn{depends} in the sense of a typical
2341 @code{make} utility; in other words, an object file depends on a source
2342 file if changes to the source file require the object file to be
2344 In addition to this basic dependency, a given object may depend on
2345 additional source files as follows:
2349 If a file being compiled @code{with}'s a unit @var{X}, the object file
2350 depends on the file containing the spec of unit @var{X}. This includes
2351 files that are @code{with}'ed implicitly either because they are parents
2352 of @code{with}'ed child units or they are run-time units required by the
2353 language constructs used in a particular unit.
2356 If a file being compiled instantiates a library level generic unit, the
2357 object file depends on both the spec and body files for this generic
2361 If a file being compiled instantiates a generic unit defined within a
2362 package, the object file depends on the body file for the package as
2363 well as the spec file.
2367 @cindex @option{-gnatn} switch
2368 If a file being compiled contains a call to a subprogram for which
2369 pragma @code{Inline} applies and inlining is activated with the
2370 @option{-gnatn} switch, the object file depends on the file containing the
2371 body of this subprogram as well as on the file containing the spec. Note
2372 that for inlining to actually occur as a result of the use of this switch,
2373 it is necessary to compile in optimizing mode.
2375 @cindex @option{-gnatN} switch
2376 The use of @option{-gnatN} activates inlining optimization
2377 that is performed by the front end of the compiler. This inlining does
2378 not require that the code generation be optimized. Like @option{-gnatn},
2379 the use of this switch generates additional dependencies.
2381 When using a gcc-based back end (in practice this means using any version
2382 of GNAT other than the JGNAT, .NET or GNAAMP versions), then the use of
2383 @option{-gnatN} is deprecated, and the use of @option{-gnatn} is preferred.
2384 Historically front end inlining was more extensive than the gcc back end
2385 inlining, but that is no longer the case.
2388 If an object file @file{O} depends on the proper body of a subunit through
2389 inlining or instantiation, it depends on the parent unit of the subunit.
2390 This means that any modification of the parent unit or one of its subunits
2391 affects the compilation of @file{O}.
2394 The object file for a parent unit depends on all its subunit body files.
2397 The previous two rules meant that for purposes of computing dependencies and
2398 recompilation, a body and all its subunits are treated as an indivisible whole.
2401 These rules are applied transitively: if unit @code{A} @code{with}'s
2402 unit @code{B}, whose elaboration calls an inlined procedure in package
2403 @code{C}, the object file for unit @code{A} will depend on the body of
2404 @code{C}, in file @file{c.adb}.
2406 The set of dependent files described by these rules includes all the
2407 files on which the unit is semantically dependent, as dictated by the
2408 Ada language standard. However, it is a superset of what the
2409 standard describes, because it includes generic, inline, and subunit
2412 An object file must be recreated by recompiling the corresponding source
2413 file if any of the source files on which it depends are modified. For
2414 example, if the @code{make} utility is used to control compilation,
2415 the rule for an Ada object file must mention all the source files on
2416 which the object file depends, according to the above definition.
2417 The determination of the necessary
2418 recompilations is done automatically when one uses @command{gnatmake}.
2421 @node The Ada Library Information Files
2422 @section The Ada Library Information Files
2423 @cindex Ada Library Information files
2424 @cindex @file{ALI} files
2427 Each compilation actually generates two output files. The first of these
2428 is the normal object file that has a @file{.o} extension. The second is a
2429 text file containing full dependency information. It has the same
2430 name as the source file, but an @file{.ali} extension.
2431 This file is known as the Ada Library Information (@file{ALI}) file.
2432 The following information is contained in the @file{ALI} file.
2436 Version information (indicates which version of GNAT was used to compile
2437 the unit(s) in question)
2440 Main program information (including priority and time slice settings,
2441 as well as the wide character encoding used during compilation).
2444 List of arguments used in the @command{gcc} command for the compilation
2447 Attributes of the unit, including configuration pragmas used, an indication
2448 of whether the compilation was successful, exception model used etc.
2451 A list of relevant restrictions applying to the unit (used for consistency)
2455 Categorization information (e.g.@: use of pragma @code{Pure}).
2458 Information on all @code{with}'ed units, including presence of
2459 @code{Elaborate} or @code{Elaborate_All} pragmas.
2462 Information from any @code{Linker_Options} pragmas used in the unit
2465 Information on the use of @code{Body_Version} or @code{Version}
2466 attributes in the unit.
2469 Dependency information. This is a list of files, together with
2470 time stamp and checksum information. These are files on which
2471 the unit depends in the sense that recompilation is required
2472 if any of these units are modified.
2475 Cross-reference data. Contains information on all entities referenced
2476 in the unit. Used by tools like @code{gnatxref} and @code{gnatfind} to
2477 provide cross-reference information.
2482 For a full detailed description of the format of the @file{ALI} file,
2483 see the source of the body of unit @code{Lib.Writ}, contained in file
2484 @file{lib-writ.adb} in the GNAT compiler sources.
2486 @node Binding an Ada Program
2487 @section Binding an Ada Program
2490 When using languages such as C and C++, once the source files have been
2491 compiled the only remaining step in building an executable program
2492 is linking the object modules together. This means that it is possible to
2493 link an inconsistent version of a program, in which two units have
2494 included different versions of the same header.
2496 The rules of Ada do not permit such an inconsistent program to be built.
2497 For example, if two clients have different versions of the same package,
2498 it is illegal to build a program containing these two clients.
2499 These rules are enforced by the GNAT binder, which also determines an
2500 elaboration order consistent with the Ada rules.
2502 The GNAT binder is run after all the object files for a program have
2503 been created. It is given the name of the main program unit, and from
2504 this it determines the set of units required by the program, by reading the
2505 corresponding ALI files. It generates error messages if the program is
2506 inconsistent or if no valid order of elaboration exists.
2508 If no errors are detected, the binder produces a main program, in Ada by
2509 default, that contains calls to the elaboration procedures of those
2510 compilation unit that require them, followed by
2511 a call to the main program. This Ada program is compiled to generate the
2512 object file for the main program. The name of
2513 the Ada file is @file{b~@var{xxx}.adb} (with the corresponding spec
2514 @file{b~@var{xxx}.ads}) where @var{xxx} is the name of the
2517 Finally, the linker is used to build the resulting executable program,
2518 using the object from the main program from the bind step as well as the
2519 object files for the Ada units of the program.
2521 @node Mixed Language Programming
2522 @section Mixed Language Programming
2523 @cindex Mixed Language Programming
2526 This section describes how to develop a mixed-language program,
2527 specifically one that comprises units in both Ada and C.
2530 * Interfacing to C::
2531 * Calling Conventions::
2534 @node Interfacing to C
2535 @subsection Interfacing to C
2537 Interfacing Ada with a foreign language such as C involves using
2538 compiler directives to import and/or export entity definitions in each
2539 language---using @code{extern} statements in C, for instance, and the
2540 @code{Import}, @code{Export}, and @code{Convention} pragmas in Ada.
2541 A full treatment of these topics is provided in Appendix B, section 1
2542 of the Ada Reference Manual.
2544 There are two ways to build a program using GNAT that contains some Ada
2545 sources and some foreign language sources, depending on whether or not
2546 the main subprogram is written in Ada. Here is a source example with
2547 the main subprogram in Ada:
2553 void print_num (int num)
2555 printf ("num is %d.\n", num);
2561 /* num_from_Ada is declared in my_main.adb */
2562 extern int num_from_Ada;
2566 return num_from_Ada;
2570 @smallexample @c ada
2572 procedure My_Main is
2574 -- Declare then export an Integer entity called num_from_Ada
2575 My_Num : Integer := 10;
2576 pragma Export (C, My_Num, "num_from_Ada");
2578 -- Declare an Ada function spec for Get_Num, then use
2579 -- C function get_num for the implementation.
2580 function Get_Num return Integer;
2581 pragma Import (C, Get_Num, "get_num");
2583 -- Declare an Ada procedure spec for Print_Num, then use
2584 -- C function print_num for the implementation.
2585 procedure Print_Num (Num : Integer);
2586 pragma Import (C, Print_Num, "print_num");
2589 Print_Num (Get_Num);
2595 To build this example, first compile the foreign language files to
2596 generate object files:
2598 ^gcc -c file1.c^gcc -c FILE1.C^
2599 ^gcc -c file2.c^gcc -c FILE2.C^
2603 Then, compile the Ada units to produce a set of object files and ALI
2606 gnatmake ^-c^/ACTIONS=COMPILE^ my_main.adb
2610 Run the Ada binder on the Ada main program:
2612 gnatbind my_main.ali
2616 Link the Ada main program, the Ada objects and the other language
2619 gnatlink my_main.ali file1.o file2.o
2623 The last three steps can be grouped in a single command:
2625 gnatmake my_main.adb -largs file1.o file2.o
2628 @cindex Binder output file
2630 If the main program is in a language other than Ada, then you may have
2631 more than one entry point into the Ada subsystem. You must use a special
2632 binder option to generate callable routines that initialize and
2633 finalize the Ada units (@pxref{Binding with Non-Ada Main Programs}).
2634 Calls to the initialization and finalization routines must be inserted
2635 in the main program, or some other appropriate point in the code. The
2636 call to initialize the Ada units must occur before the first Ada
2637 subprogram is called, and the call to finalize the Ada units must occur
2638 after the last Ada subprogram returns. The binder will place the
2639 initialization and finalization subprograms into the
2640 @file{b~@var{xxx}.adb} file where they can be accessed by your C
2641 sources. To illustrate, we have the following example:
2645 extern void adainit (void);
2646 extern void adafinal (void);
2647 extern int add (int, int);
2648 extern int sub (int, int);
2650 int main (int argc, char *argv[])
2656 /* Should print "21 + 7 = 28" */
2657 printf ("%d + %d = %d\n", a, b, add (a, b));
2658 /* Should print "21 - 7 = 14" */
2659 printf ("%d - %d = %d\n", a, b, sub (a, b));
2665 @smallexample @c ada
2668 function Add (A, B : Integer) return Integer;
2669 pragma Export (C, Add, "add");
2673 package body Unit1 is
2674 function Add (A, B : Integer) return Integer is
2682 function Sub (A, B : Integer) return Integer;
2683 pragma Export (C, Sub, "sub");
2687 package body Unit2 is
2688 function Sub (A, B : Integer) return Integer is
2697 The build procedure for this application is similar to the last
2698 example's. First, compile the foreign language files to generate object
2701 ^gcc -c main.c^gcc -c main.c^
2705 Next, compile the Ada units to produce a set of object files and ALI
2708 gnatmake ^-c^/ACTIONS=COMPILE^ unit1.adb
2709 gnatmake ^-c^/ACTIONS=COMPILE^ unit2.adb
2713 Run the Ada binder on every generated ALI file. Make sure to use the
2714 @option{-n} option to specify a foreign main program:
2716 gnatbind ^-n^/NOMAIN^ unit1.ali unit2.ali
2720 Link the Ada main program, the Ada objects and the foreign language
2721 objects. You need only list the last ALI file here:
2723 gnatlink unit2.ali main.o -o exec_file
2726 This procedure yields a binary executable called @file{exec_file}.
2730 Depending on the circumstances (for example when your non-Ada main object
2731 does not provide symbol @code{main}), you may also need to instruct the
2732 GNAT linker not to include the standard startup objects by passing the
2733 @option{^-nostartfiles^/NOSTART_FILES^} switch to @command{gnatlink}.
2735 @node Calling Conventions
2736 @subsection Calling Conventions
2737 @cindex Foreign Languages
2738 @cindex Calling Conventions
2739 GNAT follows standard calling sequence conventions and will thus interface
2740 to any other language that also follows these conventions. The following
2741 Convention identifiers are recognized by GNAT:
2744 @cindex Interfacing to Ada
2745 @cindex Other Ada compilers
2746 @cindex Convention Ada
2748 This indicates that the standard Ada calling sequence will be
2749 used and all Ada data items may be passed without any limitations in the
2750 case where GNAT is used to generate both the caller and callee. It is also
2751 possible to mix GNAT generated code and code generated by another Ada
2752 compiler. In this case, the data types should be restricted to simple
2753 cases, including primitive types. Whether complex data types can be passed
2754 depends on the situation. Probably it is safe to pass simple arrays, such
2755 as arrays of integers or floats. Records may or may not work, depending
2756 on whether both compilers lay them out identically. Complex structures
2757 involving variant records, access parameters, tasks, or protected types,
2758 are unlikely to be able to be passed.
2760 Note that in the case of GNAT running
2761 on a platform that supports HP Ada 83, a higher degree of compatibility
2762 can be guaranteed, and in particular records are layed out in an identical
2763 manner in the two compilers. Note also that if output from two different
2764 compilers is mixed, the program is responsible for dealing with elaboration
2765 issues. Probably the safest approach is to write the main program in the
2766 version of Ada other than GNAT, so that it takes care of its own elaboration
2767 requirements, and then call the GNAT-generated adainit procedure to ensure
2768 elaboration of the GNAT components. Consult the documentation of the other
2769 Ada compiler for further details on elaboration.
2771 However, it is not possible to mix the tasking run time of GNAT and
2772 HP Ada 83, All the tasking operations must either be entirely within
2773 GNAT compiled sections of the program, or entirely within HP Ada 83
2774 compiled sections of the program.
2776 @cindex Interfacing to Assembly
2777 @cindex Convention Assembler
2779 Specifies assembler as the convention. In practice this has the
2780 same effect as convention Ada (but is not equivalent in the sense of being
2781 considered the same convention).
2783 @cindex Convention Asm
2786 Equivalent to Assembler.
2788 @cindex Interfacing to COBOL
2789 @cindex Convention COBOL
2792 Data will be passed according to the conventions described
2793 in section B.4 of the Ada Reference Manual.
2796 @cindex Interfacing to C
2797 @cindex Convention C
2799 Data will be passed according to the conventions described
2800 in section B.3 of the Ada Reference Manual.
2802 A note on interfacing to a C ``varargs'' function:
2803 @findex C varargs function
2804 @cindex Interfacing to C varargs function
2805 @cindex varargs function interfaces
2809 In C, @code{varargs} allows a function to take a variable number of
2810 arguments. There is no direct equivalent in this to Ada. One
2811 approach that can be used is to create a C wrapper for each
2812 different profile and then interface to this C wrapper. For
2813 example, to print an @code{int} value using @code{printf},
2814 create a C function @code{printfi} that takes two arguments, a
2815 pointer to a string and an int, and calls @code{printf}.
2816 Then in the Ada program, use pragma @code{Import} to
2817 interface to @code{printfi}.
2820 It may work on some platforms to directly interface to
2821 a @code{varargs} function by providing a specific Ada profile
2822 for a particular call. However, this does not work on
2823 all platforms, since there is no guarantee that the
2824 calling sequence for a two argument normal C function
2825 is the same as for calling a @code{varargs} C function with
2826 the same two arguments.
2829 @cindex Convention Default
2834 @cindex Convention External
2841 @cindex Interfacing to C++
2842 @cindex Convention C++
2843 @item C_Plus_Plus (or CPP)
2844 This stands for C++. For most purposes this is identical to C.
2845 See the separate description of the specialized GNAT pragmas relating to
2846 C++ interfacing for further details.
2850 @cindex Interfacing to Fortran
2851 @cindex Convention Fortran
2853 Data will be passed according to the conventions described
2854 in section B.5 of the Ada Reference Manual.
2857 This applies to an intrinsic operation, as defined in the Ada
2858 Reference Manual. If a pragma Import (Intrinsic) applies to a subprogram,
2859 this means that the body of the subprogram is provided by the compiler itself,
2860 usually by means of an efficient code sequence, and that the user does not
2861 supply an explicit body for it. In an application program, the pragma may
2862 be applied to the following sets of names:
2866 Rotate_Left, Rotate_Right, Shift_Left, Shift_Right,
2867 Shift_Right_Arithmetic. The corresponding subprogram declaration must have
2868 two formal parameters. The
2869 first one must be a signed integer type or a modular type with a binary
2870 modulus, and the second parameter must be of type Natural.
2871 The return type must be the same as the type of the first argument. The size
2872 of this type can only be 8, 16, 32, or 64.
2875 Binary arithmetic operators: ``+'', ``-'', ``*'', ``/''
2876 The corresponding operator declaration must have parameters and result type
2877 that have the same root numeric type (for example, all three are long_float
2878 types). This simplifies the definition of operations that use type checking
2879 to perform dimensional checks:
2881 @smallexample @c ada
2882 type Distance is new Long_Float;
2883 type Time is new Long_Float;
2884 type Velocity is new Long_Float;
2885 function "/" (D : Distance; T : Time)
2887 pragma Import (Intrinsic, "/");
2891 This common idiom is often programmed with a generic definition and an
2892 explicit body. The pragma makes it simpler to introduce such declarations.
2893 It incurs no overhead in compilation time or code size, because it is
2894 implemented as a single machine instruction.
2897 General subprogram entities, to bind an Ada subprogram declaration to
2898 a compiler builtin by name with back-ends where such interfaces are
2899 available. A typical example is the set of ``__builtin'' functions
2900 exposed by the GCC back-end, as in the following example:
2902 @smallexample @c ada
2903 function builtin_sqrt (F : Float) return Float;
2904 pragma Import (Intrinsic, builtin_sqrt, "__builtin_sqrtf");
2907 Most of the GCC builtins are accessible this way, and as for other
2908 import conventions (e.g. C), it is the user's responsibility to ensure
2909 that the Ada subprogram profile matches the underlying builtin
2917 @cindex Convention Stdcall
2919 This is relevant only to Windows XP/2000/NT implementations of GNAT,
2920 and specifies that the @code{Stdcall} calling sequence will be used,
2921 as defined by the NT API. Nevertheless, to ease building
2922 cross-platform bindings this convention will be handled as a @code{C} calling
2923 convention on non-Windows platforms.
2926 @cindex Convention DLL
2928 This is equivalent to @code{Stdcall}.
2931 @cindex Convention Win32
2933 This is equivalent to @code{Stdcall}.
2937 @cindex Convention Stubbed
2939 This is a special convention that indicates that the compiler
2940 should provide a stub body that raises @code{Program_Error}.
2944 GNAT additionally provides a useful pragma @code{Convention_Identifier}
2945 that can be used to parametrize conventions and allow additional synonyms
2946 to be specified. For example if you have legacy code in which the convention
2947 identifier Fortran77 was used for Fortran, you can use the configuration
2950 @smallexample @c ada
2951 pragma Convention_Identifier (Fortran77, Fortran);
2955 And from now on the identifier Fortran77 may be used as a convention
2956 identifier (for example in an @code{Import} pragma) with the same
2960 @node Building Mixed Ada & C++ Programs
2961 @section Building Mixed Ada and C++ Programs
2964 A programmer inexperienced with mixed-language development may find that
2965 building an application containing both Ada and C++ code can be a
2966 challenge. This section gives a few
2967 hints that should make this task easier. The first section addresses
2968 the differences between interfacing with C and interfacing with C++.
2970 looks into the delicate problem of linking the complete application from
2971 its Ada and C++ parts. The last section gives some hints on how the GNAT
2972 run-time library can be adapted in order to allow inter-language dispatching
2973 with a new C++ compiler.
2976 * Interfacing to C++::
2977 * Linking a Mixed C++ & Ada Program::
2978 * A Simple Example::
2979 * Interfacing with C++ constructors::
2980 * Interfacing with C++ at the Class Level::
2983 @node Interfacing to C++
2984 @subsection Interfacing to C++
2987 GNAT supports interfacing with the G++ compiler (or any C++ compiler
2988 generating code that is compatible with the G++ Application Binary
2989 Interface ---see http://www.codesourcery.com/archives/cxx-abi).
2992 Interfacing can be done at 3 levels: simple data, subprograms, and
2993 classes. In the first two cases, GNAT offers a specific @code{Convention
2994 C_Plus_Plus} (or @code{CPP}) that behaves exactly like @code{Convention C}.
2995 Usually, C++ mangles the names of subprograms. To generate proper mangled
2996 names automatically, see @ref{Generating Ada Bindings for C and C++ headers}).
2997 This problem can also be addressed manually in two ways:
3001 by modifying the C++ code in order to force a C convention using
3002 the @code{extern "C"} syntax.
3005 by figuring out the mangled name (using e.g. @command{nm}) and using it as the
3006 Link_Name argument of the pragma import.
3010 Interfacing at the class level can be achieved by using the GNAT specific
3011 pragmas such as @code{CPP_Constructor}. @xref{Interfacing to C++,,,
3012 gnat_rm, GNAT Reference Manual}, for additional information.
3014 @node Linking a Mixed C++ & Ada Program
3015 @subsection Linking a Mixed C++ & Ada Program
3018 Usually the linker of the C++ development system must be used to link
3019 mixed applications because most C++ systems will resolve elaboration
3020 issues (such as calling constructors on global class instances)
3021 transparently during the link phase. GNAT has been adapted to ease the
3022 use of a foreign linker for the last phase. Three cases can be
3027 Using GNAT and G++ (GNU C++ compiler) from the same GCC installation:
3028 The C++ linker can simply be called by using the C++ specific driver
3031 Note that if the C++ code uses inline functions, you will need to
3032 compile your C++ code with the @code{-fkeep-inline-functions} switch in
3033 order to provide an existing function implementation that the Ada code can
3037 $ g++ -c -fkeep-inline-functions file1.C
3038 $ g++ -c -fkeep-inline-functions file2.C
3039 $ gnatmake ada_unit -largs file1.o file2.o --LINK=g++
3043 Using GNAT and G++ from two different GCC installations: If both
3044 compilers are on the @env{PATH}, the previous method may be used. It is
3045 important to note that environment variables such as
3046 @env{C_INCLUDE_PATH}, @env{GCC_EXEC_PREFIX}, @env{BINUTILS_ROOT}, and
3047 @env{GCC_ROOT} will affect both compilers
3048 at the same time and may make one of the two compilers operate
3049 improperly if set during invocation of the wrong compiler. It is also
3050 very important that the linker uses the proper @file{libgcc.a} GCC
3051 library -- that is, the one from the C++ compiler installation. The
3052 implicit link command as suggested in the @command{gnatmake} command
3053 from the former example can be replaced by an explicit link command with
3054 the full-verbosity option in order to verify which library is used:
3057 $ gnatlink -v -v ada_unit file1.o file2.o --LINK=c++
3059 If there is a problem due to interfering environment variables, it can
3060 be worked around by using an intermediate script. The following example
3061 shows the proper script to use when GNAT has not been installed at its
3062 default location and g++ has been installed at its default location:
3070 $ gnatlink -v -v ada_unit file1.o file2.o --LINK=./my_script
3074 Using a non-GNU C++ compiler: The commands previously described can be
3075 used to insure that the C++ linker is used. Nonetheless, you need to add
3076 a few more parameters to the link command line, depending on the exception
3079 If the @code{setjmp/longjmp} exception mechanism is used, only the paths
3080 to the libgcc libraries are required:
3085 CC $* `gcc -print-file-name=libgcc.a` `gcc -print-file-name=libgcc_eh.a`
3086 $ gnatlink ada_unit file1.o file2.o --LINK=./my_script
3089 Where CC is the name of the non-GNU C++ compiler.
3091 If the @code{zero cost} exception mechanism is used, and the platform
3092 supports automatic registration of exception tables (e.g.@: Solaris or IRIX),
3093 paths to more objects are required:
3098 CC `gcc -print-file-name=crtbegin.o` $* \
3099 `gcc -print-file-name=libgcc.a` `gcc -print-file-name=libgcc_eh.a` \
3100 `gcc -print-file-name=crtend.o`
3101 $ gnatlink ada_unit file1.o file2.o --LINK=./my_script
3104 If the @code{zero cost} exception mechanism is used, and the platform
3105 doesn't support automatic registration of exception tables (e.g.@: HP-UX,
3106 Tru64 or AIX), the simple approach described above will not work and
3107 a pre-linking phase using GNAT will be necessary.
3111 Another alternative is to use the @command{gprbuild} multi-language builder
3112 which has a large knowledge base and knows how to link Ada and C++ code
3113 together automatically in most cases.
3115 @node A Simple Example
3116 @subsection A Simple Example
3118 The following example, provided as part of the GNAT examples, shows how
3119 to achieve procedural interfacing between Ada and C++ in both
3120 directions. The C++ class A has two methods. The first method is exported
3121 to Ada by the means of an extern C wrapper function. The second method
3122 calls an Ada subprogram. On the Ada side, The C++ calls are modelled by
3123 a limited record with a layout comparable to the C++ class. The Ada
3124 subprogram, in turn, calls the C++ method. So, starting from the C++
3125 main program, the process passes back and forth between the two
3129 Here are the compilation commands:
3131 $ gnatmake -c simple_cpp_interface
3134 $ gnatbind -n simple_cpp_interface
3135 $ gnatlink simple_cpp_interface -o cpp_main --LINK=g++
3136 -lstdc++ ex7.o cpp_main.o
3140 Here are the corresponding sources:
3148 void adainit (void);
3149 void adafinal (void);
3150 void method1 (A *t);
3172 class A : public Origin @{
3174 void method1 (void);
3175 void method2 (int v);
3185 extern "C" @{ void ada_method2 (A *t, int v);@}
3187 void A::method1 (void)
3190 printf ("in A::method1, a_value = %d \n",a_value);
3194 void A::method2 (int v)
3196 ada_method2 (this, v);
3197 printf ("in A::method2, a_value = %d \n",a_value);
3204 printf ("in A::A, a_value = %d \n",a_value);
3208 @smallexample @c ada
3210 package body Simple_Cpp_Interface is
3212 procedure Ada_Method2 (This : in out A; V : Integer) is
3218 end Simple_Cpp_Interface;
3221 package Simple_Cpp_Interface is
3224 Vptr : System.Address;
3228 pragma Convention (C, A);
3230 procedure Method1 (This : in out A);
3231 pragma Import (C, Method1);
3233 procedure Ada_Method2 (This : in out A; V : Integer);
3234 pragma Export (C, Ada_Method2);
3236 end Simple_Cpp_Interface;
3239 @node Interfacing with C++ constructors
3240 @subsection Interfacing with C++ constructors
3243 In order to interface with C++ constructors GNAT provides the
3244 @code{pragma CPP_Constructor} (@xref{Interfacing to C++,,,
3245 gnat_rm, GNAT Reference Manual}, for additional information).
3246 In this section we present some common uses of C++ constructors
3247 in mixed-languages programs in GNAT.
3249 Let us assume that we need to interface with the following
3257 @b{virtual} int Get_Value ();
3258 Root(); // Default constructor
3259 Root(int v); // 1st non-default constructor
3260 Root(int v, int w); // 2nd non-default constructor
3264 For this purpose we can write the following package spec (further
3265 information on how to build this spec is available in
3266 @ref{Interfacing with C++ at the Class Level} and
3267 @ref{Generating Ada Bindings for C and C++ headers}).
3269 @smallexample @c ada
3270 with Interfaces.C; use Interfaces.C;
3272 type Root is tagged limited record
3276 pragma Import (CPP, Root);
3278 function Get_Value (Obj : Root) return int;
3279 pragma Import (CPP, Get_Value);
3281 function Constructor return Root'Class;
3282 pragma Cpp_Constructor (Constructor, "_ZN4RootC1Ev");
3284 function Constructor (v : Integer) return Root'Class;
3285 pragma Cpp_Constructor (Constructor, "_ZN4RootC1Ei");
3287 function Constructor (v, w : Integer) return Root'Class;
3288 pragma Cpp_Constructor (Constructor, "_ZN4RootC1Eii");
3292 On the Ada side the constructor is represented by a function (whose
3293 name is arbitrary) that returns the classwide type corresponding to
3294 the imported C++ class. Although the constructor is described as a
3295 function, it is typically a procedure with an extra implicit argument
3296 (the object being initialized) at the implementation level. GNAT
3297 issues the appropriate call, whatever it is, to get the object
3298 properly initialized.
3300 Constructors can only appear in the following contexts:
3304 On the right side of an initialization of an object of type @var{T}.
3306 On the right side of an initialization of a record component of type @var{T}.
3308 In an Ada 2005 limited aggregate.
3310 In an Ada 2005 nested limited aggregate.
3312 In an Ada 2005 limited aggregate that initializes an object built in
3313 place by an extended return statement.
3317 In a declaration of an object whose type is a class imported from C++,
3318 either the default C++ constructor is implicitly called by GNAT, or
3319 else the required C++ constructor must be explicitly called in the
3320 expression that initializes the object. For example:
3322 @smallexample @c ada
3324 Obj2 : Root := Constructor;
3325 Obj3 : Root := Constructor (v => 10);
3326 Obj4 : Root := Constructor (30, 40);
3329 The first two declarations are equivalent: in both cases the default C++
3330 constructor is invoked (in the former case the call to the constructor is
3331 implicit, and in the latter case the call is explicit in the object
3332 declaration). @code{Obj3} is initialized by the C++ non-default constructor
3333 that takes an integer argument, and @code{Obj4} is initialized by the
3334 non-default C++ constructor that takes two integers.
3336 Let us derive the imported C++ class in the Ada side. For example:
3338 @smallexample @c ada
3339 type DT is new Root with record
3340 C_Value : Natural := 2009;
3344 In this case the components DT inherited from the C++ side must be
3345 initialized by a C++ constructor, and the additional Ada components
3346 of type DT are initialized by GNAT. The initialization of such an
3347 object is done either by default, or by means of a function returning
3348 an aggregate of type DT, or by means of an extension aggregate.
3350 @smallexample @c ada
3352 Obj6 : DT := Function_Returning_DT (50);
3353 Obj7 : DT := (Constructor (30,40) with C_Value => 50);
3356 The declaration of @code{Obj5} invokes the default constructors: the
3357 C++ default constructor of the parent type takes care of the initialization
3358 of the components inherited from Root, and GNAT takes care of the default
3359 initialization of the additional Ada components of type DT (that is,
3360 @code{C_Value} is initialized to value 2009). The order of invocation of
3361 the constructors is consistent with the order of elaboration required by
3362 Ada and C++. That is, the constructor of the parent type is always called
3363 before the constructor of the derived type.
3365 Let us now consider a record that has components whose type is imported
3366 from C++. For example:
3368 @smallexample @c ada
3369 type Rec1 is limited record
3370 Data1 : Root := Constructor (10);
3371 Value : Natural := 1000;
3374 type Rec2 (D : Integer := 20) is limited record
3376 Data2 : Root := Constructor (D, 30);
3380 The initialization of an object of type @code{Rec2} will call the
3381 non-default C++ constructors specified for the imported components.
3384 @smallexample @c ada
3388 Using Ada 2005 we can use limited aggregates to initialize an object
3389 invoking C++ constructors that differ from those specified in the type
3390 declarations. For example:
3392 @smallexample @c ada
3393 Obj9 : Rec2 := (Rec => (Data1 => Constructor (15, 16),
3398 The above declaration uses an Ada 2005 limited aggregate to
3399 initialize @code{Obj9}, and the C++ constructor that has two integer
3400 arguments is invoked to initialize the @code{Data1} component instead
3401 of the constructor specified in the declaration of type @code{Rec1}. In
3402 Ada 2005 the box in the aggregate indicates that unspecified components
3403 are initialized using the expression (if any) available in the component
3404 declaration. That is, in this case discriminant @code{D} is initialized
3405 to value @code{20}, @code{Value} is initialized to value 1000, and the
3406 non-default C++ constructor that handles two integers takes care of
3407 initializing component @code{Data2} with values @code{20,30}.
3409 In Ada 2005 we can use the extended return statement to build the Ada
3410 equivalent to C++ non-default constructors. For example:
3412 @smallexample @c ada
3413 function Constructor (V : Integer) return Rec2 is
3415 return Obj : Rec2 := (Rec => (Data1 => Constructor (V, 20),
3418 -- Further actions required for construction of
3419 -- objects of type Rec2
3425 In this example the extended return statement construct is used to
3426 build in place the returned object whose components are initialized
3427 by means of a limited aggregate. Any further action associated with
3428 the constructor can be placed inside the construct.
3430 @node Interfacing with C++ at the Class Level
3431 @subsection Interfacing with C++ at the Class Level
3433 In this section we demonstrate the GNAT features for interfacing with
3434 C++ by means of an example making use of Ada 2005 abstract interface
3435 types. This example consists of a classification of animals; classes
3436 have been used to model our main classification of animals, and
3437 interfaces provide support for the management of secondary
3438 classifications. We first demonstrate a case in which the types and
3439 constructors are defined on the C++ side and imported from the Ada
3440 side, and latter the reverse case.
3442 The root of our derivation will be the @code{Animal} class, with a
3443 single private attribute (the @code{Age} of the animal) and two public
3444 primitives to set and get the value of this attribute.
3449 @b{virtual} void Set_Age (int New_Age);
3450 @b{virtual} int Age ();
3456 Abstract interface types are defined in C++ by means of classes with pure
3457 virtual functions and no data members. In our example we will use two
3458 interfaces that provide support for the common management of @code{Carnivore}
3459 and @code{Domestic} animals:
3462 @b{class} Carnivore @{
3464 @b{virtual} int Number_Of_Teeth () = 0;
3467 @b{class} Domestic @{
3469 @b{virtual void} Set_Owner (char* Name) = 0;
3473 Using these declarations, we can now say that a @code{Dog} is an animal that is
3474 both Carnivore and Domestic, that is:
3477 @b{class} Dog : Animal, Carnivore, Domestic @{
3479 @b{virtual} int Number_Of_Teeth ();
3480 @b{virtual} void Set_Owner (char* Name);
3482 Dog(); // Constructor
3489 In the following examples we will assume that the previous declarations are
3490 located in a file named @code{animals.h}. The following package demonstrates
3491 how to import these C++ declarations from the Ada side:
3493 @smallexample @c ada
3494 with Interfaces.C.Strings; use Interfaces.C.Strings;
3496 type Carnivore is interface;
3497 pragma Convention (C_Plus_Plus, Carnivore);
3498 function Number_Of_Teeth (X : Carnivore)
3499 return Natural is abstract;
3501 type Domestic is interface;
3502 pragma Convention (C_Plus_Plus, Set_Owner);
3504 (X : in out Domestic;
3505 Name : Chars_Ptr) is abstract;
3507 type Animal is tagged record
3510 pragma Import (C_Plus_Plus, Animal);
3512 procedure Set_Age (X : in out Animal; Age : Integer);
3513 pragma Import (C_Plus_Plus, Set_Age);
3515 function Age (X : Animal) return Integer;
3516 pragma Import (C_Plus_Plus, Age);
3518 type Dog is new Animal and Carnivore and Domestic with record
3519 Tooth_Count : Natural;
3520 Owner : String (1 .. 30);
3522 pragma Import (C_Plus_Plus, Dog);
3524 function Number_Of_Teeth (A : Dog) return Integer;
3525 pragma Import (C_Plus_Plus, Number_Of_Teeth);
3527 procedure Set_Owner (A : in out Dog; Name : Chars_Ptr);
3528 pragma Import (C_Plus_Plus, Set_Owner);
3530 function New_Dog return Dog'Class;
3531 pragma CPP_Constructor (New_Dog);
3532 pragma Import (CPP, New_Dog, "_ZN3DogC2Ev");
3536 Thanks to the compatibility between GNAT run-time structures and the C++ ABI,
3537 interfacing with these C++ classes is easy. The only requirement is that all
3538 the primitives and components must be declared exactly in the same order in
3541 Regarding the abstract interfaces, we must indicate to the GNAT compiler by
3542 means of a @code{pragma Convention (C_Plus_Plus)}, the convention used to pass
3543 the arguments to the called primitives will be the same as for C++. For the
3544 imported classes we use @code{pragma Import} with convention @code{C_Plus_Plus}
3545 to indicate that they have been defined on the C++ side; this is required
3546 because the dispatch table associated with these tagged types will be built
3547 in the C++ side and therefore will not contain the predefined Ada primitives
3548 which Ada would otherwise expect.
3550 As the reader can see there is no need to indicate the C++ mangled names
3551 associated with each subprogram because it is assumed that all the calls to
3552 these primitives will be dispatching calls. The only exception is the
3553 constructor, which must be registered with the compiler by means of
3554 @code{pragma CPP_Constructor} and needs to provide its associated C++
3555 mangled name because the Ada compiler generates direct calls to it.
3557 With the above packages we can now declare objects of type Dog on the Ada side
3558 and dispatch calls to the corresponding subprograms on the C++ side. We can
3559 also extend the tagged type Dog with further fields and primitives, and
3560 override some of its C++ primitives on the Ada side. For example, here we have
3561 a type derivation defined on the Ada side that inherits all the dispatching
3562 primitives of the ancestor from the C++ side.
3565 @b{with} Animals; @b{use} Animals;
3566 @b{package} Vaccinated_Animals @b{is}
3567 @b{type} Vaccinated_Dog @b{is new} Dog @b{with null record};
3568 @b{function} Vaccination_Expired (A : Vaccinated_Dog) @b{return} Boolean;
3569 @b{end} Vaccinated_Animals;
3572 It is important to note that, because of the ABI compatibility, the programmer
3573 does not need to add any further information to indicate either the object
3574 layout or the dispatch table entry associated with each dispatching operation.
3576 Now let us define all the types and constructors on the Ada side and export
3577 them to C++, using the same hierarchy of our previous example:
3579 @smallexample @c ada
3580 with Interfaces.C.Strings;
3581 use Interfaces.C.Strings;
3583 type Carnivore is interface;
3584 pragma Convention (C_Plus_Plus, Carnivore);
3585 function Number_Of_Teeth (X : Carnivore)
3586 return Natural is abstract;
3588 type Domestic is interface;
3589 pragma Convention (C_Plus_Plus, Set_Owner);
3591 (X : in out Domestic;
3592 Name : Chars_Ptr) is abstract;
3594 type Animal is tagged record
3597 pragma Convention (C_Plus_Plus, Animal);
3599 procedure Set_Age (X : in out Animal; Age : Integer);
3600 pragma Export (C_Plus_Plus, Set_Age);
3602 function Age (X : Animal) return Integer;
3603 pragma Export (C_Plus_Plus, Age);
3605 type Dog is new Animal and Carnivore and Domestic with record
3606 Tooth_Count : Natural;
3607 Owner : String (1 .. 30);
3609 pragma Convention (C_Plus_Plus, Dog);
3611 function Number_Of_Teeth (A : Dog) return Integer;
3612 pragma Export (C_Plus_Plus, Number_Of_Teeth);
3614 procedure Set_Owner (A : in out Dog; Name : Chars_Ptr);
3615 pragma Export (C_Plus_Plus, Set_Owner);
3617 function New_Dog return Dog'Class;
3618 pragma Export (C_Plus_Plus, New_Dog);
3622 Compared with our previous example the only difference is the use of
3623 @code{pragma Export} to indicate to the GNAT compiler that the primitives will
3624 be available to C++. Thanks to the ABI compatibility, on the C++ side there is
3625 nothing else to be done; as explained above, the only requirement is that all
3626 the primitives and components are declared in exactly the same order.
3628 For completeness, let us see a brief C++ main program that uses the
3629 declarations available in @code{animals.h} (presented in our first example) to
3630 import and use the declarations from the Ada side, properly initializing and
3631 finalizing the Ada run-time system along the way:
3634 @b{#include} "animals.h"
3635 @b{#include} <iostream>
3636 @b{using namespace} std;
3638 void Check_Carnivore (Carnivore *obj) @{@dots{}@}
3639 void Check_Domestic (Domestic *obj) @{@dots{}@}
3640 void Check_Animal (Animal *obj) @{@dots{}@}
3641 void Check_Dog (Dog *obj) @{@dots{}@}
3644 void adainit (void);
3645 void adafinal (void);
3651 Dog *obj = new_dog(); // Ada constructor
3652 Check_Carnivore (obj); // Check secondary DT
3653 Check_Domestic (obj); // Check secondary DT
3654 Check_Animal (obj); // Check primary DT
3655 Check_Dog (obj); // Check primary DT
3660 adainit (); test(); adafinal ();
3665 @node Comparison between GNAT and C/C++ Compilation Models
3666 @section Comparison between GNAT and C/C++ Compilation Models
3669 The GNAT model of compilation is close to the C and C++ models. You can
3670 think of Ada specs as corresponding to header files in C. As in C, you
3671 don't need to compile specs; they are compiled when they are used. The
3672 Ada @code{with} is similar in effect to the @code{#include} of a C
3675 One notable difference is that, in Ada, you may compile specs separately
3676 to check them for semantic and syntactic accuracy. This is not always
3677 possible with C headers because they are fragments of programs that have
3678 less specific syntactic or semantic rules.
3680 The other major difference is the requirement for running the binder,
3681 which performs two important functions. First, it checks for
3682 consistency. In C or C++, the only defense against assembling
3683 inconsistent programs lies outside the compiler, in a makefile, for
3684 example. The binder satisfies the Ada requirement that it be impossible
3685 to construct an inconsistent program when the compiler is used in normal
3688 @cindex Elaboration order control
3689 The other important function of the binder is to deal with elaboration
3690 issues. There are also elaboration issues in C++ that are handled
3691 automatically. This automatic handling has the advantage of being
3692 simpler to use, but the C++ programmer has no control over elaboration.
3693 Where @code{gnatbind} might complain there was no valid order of
3694 elaboration, a C++ compiler would simply construct a program that
3695 malfunctioned at run time.
3698 @node Comparison between GNAT and Conventional Ada Library Models
3699 @section Comparison between GNAT and Conventional Ada Library Models
3702 This section is intended for Ada programmers who have
3703 used an Ada compiler implementing the traditional Ada library
3704 model, as described in the Ada Reference Manual.
3706 @cindex GNAT library
3707 In GNAT, there is no ``library'' in the normal sense. Instead, the set of
3708 source files themselves acts as the library. Compiling Ada programs does
3709 not generate any centralized information, but rather an object file and
3710 a ALI file, which are of interest only to the binder and linker.
3711 In a traditional system, the compiler reads information not only from
3712 the source file being compiled, but also from the centralized library.
3713 This means that the effect of a compilation depends on what has been
3714 previously compiled. In particular:
3718 When a unit is @code{with}'ed, the unit seen by the compiler corresponds
3719 to the version of the unit most recently compiled into the library.
3722 Inlining is effective only if the necessary body has already been
3723 compiled into the library.
3726 Compiling a unit may obsolete other units in the library.
3730 In GNAT, compiling one unit never affects the compilation of any other
3731 units because the compiler reads only source files. Only changes to source
3732 files can affect the results of a compilation. In particular:
3736 When a unit is @code{with}'ed, the unit seen by the compiler corresponds
3737 to the source version of the unit that is currently accessible to the
3742 Inlining requires the appropriate source files for the package or
3743 subprogram bodies to be available to the compiler. Inlining is always
3744 effective, independent of the order in which units are complied.
3747 Compiling a unit never affects any other compilations. The editing of
3748 sources may cause previous compilations to be out of date if they
3749 depended on the source file being modified.
3753 The most important result of these differences is that order of compilation
3754 is never significant in GNAT. There is no situation in which one is
3755 required to do one compilation before another. What shows up as order of
3756 compilation requirements in the traditional Ada library becomes, in
3757 GNAT, simple source dependencies; in other words, there is only a set
3758 of rules saying what source files must be present when a file is
3762 @node Placement of temporary files
3763 @section Placement of temporary files
3764 @cindex Temporary files (user control over placement)
3767 GNAT creates temporary files in the directory designated by the environment
3768 variable @env{TMPDIR}.
3769 (See the HP @emph{C RTL Reference Manual} on the function @code{getenv()}
3770 for detailed information on how environment variables are resolved.
3771 For most users the easiest way to make use of this feature is to simply
3772 define @env{TMPDIR} as a job level logical name).
3773 For example, if you wish to use a Ramdisk (assuming DECRAM is installed)
3774 for compiler temporary files, then you can include something like the
3775 following command in your @file{LOGIN.COM} file:
3778 $ define/job TMPDIR "/disk$scratchram/000000/temp/"
3782 If @env{TMPDIR} is not defined, then GNAT uses the directory designated by
3783 @env{TMP}; if @env{TMP} is not defined, then GNAT uses the directory
3784 designated by @env{TEMP}.
3785 If none of these environment variables are defined then GNAT uses the
3786 directory designated by the logical name @code{SYS$SCRATCH:}
3787 (by default the user's home directory). If all else fails
3788 GNAT uses the current directory for temporary files.
3791 @c *************************
3792 @node Compiling Using gcc
3793 @chapter Compiling Using @command{gcc}
3796 This chapter discusses how to compile Ada programs using the @command{gcc}
3797 command. It also describes the set of switches
3798 that can be used to control the behavior of the compiler.
3800 * Compiling Programs::
3801 * Switches for gcc::
3802 * Search Paths and the Run-Time Library (RTL)::
3803 * Order of Compilation Issues::
3807 @node Compiling Programs
3808 @section Compiling Programs
3811 The first step in creating an executable program is to compile the units
3812 of the program using the @command{gcc} command. You must compile the
3817 the body file (@file{.adb}) for a library level subprogram or generic
3821 the spec file (@file{.ads}) for a library level package or generic
3822 package that has no body
3825 the body file (@file{.adb}) for a library level package
3826 or generic package that has a body
3831 You need @emph{not} compile the following files
3836 the spec of a library unit which has a body
3843 because they are compiled as part of compiling related units. GNAT
3845 when the corresponding body is compiled, and subunits when the parent is
3848 @cindex cannot generate code
3849 If you attempt to compile any of these files, you will get one of the
3850 following error messages (where @var{fff} is the name of the file you compiled):
3853 cannot generate code for file @var{fff} (package spec)
3854 to check package spec, use -gnatc
3856 cannot generate code for file @var{fff} (missing subunits)
3857 to check parent unit, use -gnatc
3859 cannot generate code for file @var{fff} (subprogram spec)
3860 to check subprogram spec, use -gnatc
3862 cannot generate code for file @var{fff} (subunit)
3863 to check subunit, use -gnatc
3867 As indicated by the above error messages, if you want to submit
3868 one of these files to the compiler to check for correct semantics
3869 without generating code, then use the @option{-gnatc} switch.
3871 The basic command for compiling a file containing an Ada unit is
3874 $ gcc -c @ovar{switches} @file{file name}
3878 where @var{file name} is the name of the Ada file (usually
3880 @file{.ads} for a spec or @file{.adb} for a body).
3883 @option{-c} switch to tell @command{gcc} to compile, but not link, the file.
3885 The result of a successful compilation is an object file, which has the
3886 same name as the source file but an extension of @file{.o} and an Ada
3887 Library Information (ALI) file, which also has the same name as the
3888 source file, but with @file{.ali} as the extension. GNAT creates these
3889 two output files in the current directory, but you may specify a source
3890 file in any directory using an absolute or relative path specification
3891 containing the directory information.
3894 @command{gcc} is actually a driver program that looks at the extensions of
3895 the file arguments and loads the appropriate compiler. For example, the
3896 GNU C compiler is @file{cc1}, and the Ada compiler is @file{gnat1}.
3897 These programs are in directories known to the driver program (in some
3898 configurations via environment variables you set), but need not be in
3899 your path. The @command{gcc} driver also calls the assembler and any other
3900 utilities needed to complete the generation of the required object
3903 It is possible to supply several file names on the same @command{gcc}
3904 command. This causes @command{gcc} to call the appropriate compiler for
3905 each file. For example, the following command lists three separate
3906 files to be compiled:
3909 $ gcc -c x.adb y.adb z.c
3913 calls @code{gnat1} (the Ada compiler) twice to compile @file{x.adb} and
3914 @file{y.adb}, and @code{cc1} (the C compiler) once to compile @file{z.c}.
3915 The compiler generates three object files @file{x.o}, @file{y.o} and
3916 @file{z.o} and the two ALI files @file{x.ali} and @file{y.ali} from the
3917 Ada compilations. Any switches apply to all the files ^listed,^listed.^
3920 @option{-gnat@var{x}} switches, which apply only to Ada compilations.
3923 @node Switches for gcc
3924 @section Switches for @command{gcc}
3927 The @command{gcc} command accepts switches that control the
3928 compilation process. These switches are fully described in this section.
3929 First we briefly list all the switches, in alphabetical order, then we
3930 describe the switches in more detail in functionally grouped sections.
3932 More switches exist for GCC than those documented here, especially
3933 for specific targets. However, their use is not recommended as
3934 they may change code generation in ways that are incompatible with
3935 the Ada run-time library, or can cause inconsistencies between
3939 * Output and Error Message Control::
3940 * Warning Message Control::
3941 * Debugging and Assertion Control::
3942 * Validity Checking::
3945 * Using gcc for Syntax Checking::
3946 * Using gcc for Semantic Checking::
3947 * Compiling Different Versions of Ada::
3948 * Character Set Control::
3949 * File Naming Control::
3950 * Subprogram Inlining Control::
3951 * Auxiliary Output Control::
3952 * Debugging Control::
3953 * Exception Handling Control::
3954 * Units to Sources Mapping Files::
3955 * Integrated Preprocessing::
3956 * Code Generation Control::
3965 @cindex @option{-b} (@command{gcc})
3966 @item -b @var{target}
3967 Compile your program to run on @var{target}, which is the name of a
3968 system configuration. You must have a GNAT cross-compiler built if
3969 @var{target} is not the same as your host system.
3972 @cindex @option{-B} (@command{gcc})
3973 Load compiler executables (for example, @code{gnat1}, the Ada compiler)
3974 from @var{dir} instead of the default location. Only use this switch
3975 when multiple versions of the GNAT compiler are available.
3976 @xref{Directory Options,, Options for Directory Search, gcc, Using the
3977 GNU Compiler Collection (GCC)}, for further details. You would normally
3978 use the @option{-b} or @option{-V} switch instead.
3981 @cindex @option{-c} (@command{gcc})
3982 Compile. Always use this switch when compiling Ada programs.
3984 Note: for some other languages when using @command{gcc}, notably in
3985 the case of C and C++, it is possible to use
3986 use @command{gcc} without a @option{-c} switch to
3987 compile and link in one step. In the case of GNAT, you
3988 cannot use this approach, because the binder must be run
3989 and @command{gcc} cannot be used to run the GNAT binder.
3993 @cindex @option{-fno-inline} (@command{gcc})
3994 Suppresses all back-end inlining, even if other optimization or inlining
3996 This includes suppression of inlining that results
3997 from the use of the pragma @code{Inline_Always}.
3998 Any occurrences of pragma @code{Inline} or @code{Inline_Always}
3999 are ignored, and @option{-gnatn} and @option{-gnatN} have no
4000 effect if this switch is present.
4002 @item -fno-inline-functions
4003 @cindex @option{-fno-inline-functions} (@command{gcc})
4004 Suppresses automatic inlining of simple subprograms, which is enabled
4005 if @option{-O3} is used.
4007 @item -fno-inline-small-functions
4008 @cindex @option{-fno-inline-small-functions} (@command{gcc})
4009 Suppresses automatic inlining of small subprograms, which is enabled
4010 if @option{-O2} is used.
4012 @item -fno-inline-functions-called-once
4013 @cindex @option{-fno-inline-functions-called-once} (@command{gcc})
4014 Suppresses inlining of subprograms local to the unit and called once
4015 from within it, which is enabled if @option{-O1} is used.
4018 @cindex @option{-fno-ivopts} (@command{gcc})
4019 Suppresses high-level loop induction variable optimizations, which are
4020 enabled if @option{-O1} is used. These optimizations are generally
4021 profitable but, for some specific cases of loops with numerous uses
4022 of the iteration variable that follow a common pattern, they may end
4023 up destroying the regularity that could be exploited at a lower level
4024 and thus producing inferior code.
4026 @item -fno-strict-aliasing
4027 @cindex @option{-fno-strict-aliasing} (@command{gcc})
4028 Causes the compiler to avoid assumptions regarding non-aliasing
4029 of objects of different types. See
4030 @ref{Optimization and Strict Aliasing} for details.
4033 @cindex @option{-fstack-check} (@command{gcc})
4034 Activates stack checking.
4035 See @ref{Stack Overflow Checking} for details.
4038 @cindex @option{-fstack-usage} (@command{gcc})
4039 Makes the compiler output stack usage information for the program, on a
4040 per-function basis. See @ref{Static Stack Usage Analysis} for details.
4042 @item -fcallgraph-info@r{[}=su@r{]}
4043 @cindex @option{-fcallgraph-info} (@command{gcc})
4044 Makes the compiler output callgraph information for the program, on a
4045 per-file basis. The information is generated in the VCG format. It can
4046 be decorated with stack-usage per-node information.
4049 @cindex @option{^-g^/DEBUG^} (@command{gcc})
4050 Generate debugging information. This information is stored in the object
4051 file and copied from there to the final executable file by the linker,
4052 where it can be read by the debugger. You must use the
4053 @option{^-g^/DEBUG^} switch if you plan on using the debugger.
4056 @cindex @option{-gnat83} (@command{gcc})
4057 Enforce Ada 83 restrictions.
4060 @cindex @option{-gnat95} (@command{gcc})
4061 Enforce Ada 95 restrictions.
4064 @cindex @option{-gnat05} (@command{gcc})
4065 Allow full Ada 2005 features.
4068 @cindex @option{-gnata} (@command{gcc})
4069 Assertions enabled. @code{Pragma Assert} and @code{pragma Debug} to be
4070 activated. Note that these pragmas can also be controlled using the
4071 configuration pragmas @code{Assertion_Policy} and @code{Debug_Policy}.
4072 It also activates pragmas @code{Check}, @code{Precondition}, and
4073 @code{Postcondition}. Note that these pragmas can also be controlled
4074 using the configuration pragma @code{Check_Policy}.
4077 @cindex @option{-gnatA} (@command{gcc})
4078 Avoid processing @file{gnat.adc}. If a @file{gnat.adc} file is present,
4082 @cindex @option{-gnatb} (@command{gcc})
4083 Generate brief messages to @file{stderr} even if verbose mode set.
4086 @cindex @option{-gnatB} (@command{gcc})
4087 Assume no invalid (bad) values except for 'Valid attribute use.
4090 @cindex @option{-gnatc} (@command{gcc})
4091 Check syntax and semantics only (no code generation attempted).
4094 @cindex @option{-gnatd} (@command{gcc})
4095 Specify debug options for the compiler. The string of characters after
4096 the @option{-gnatd} specify the specific debug options. The possible
4097 characters are 0-9, a-z, A-Z, optionally preceded by a dot. See
4098 compiler source file @file{debug.adb} for details of the implemented
4099 debug options. Certain debug options are relevant to applications
4100 programmers, and these are documented at appropriate points in this
4105 @cindex @option{-gnatD[nn]} (@command{gcc})
4108 @item /XDEBUG /LXDEBUG=nnn
4110 Create expanded source files for source level debugging. This switch
4111 also suppress generation of cross-reference information
4112 (see @option{-gnatx}).
4114 @item -gnatec=@var{path}
4115 @cindex @option{-gnatec} (@command{gcc})
4116 Specify a configuration pragma file
4118 (the equal sign is optional)
4120 (@pxref{The Configuration Pragmas Files}).
4122 @item ^-gnateD^/DATA_PREPROCESSING=^symbol@r{[}=@var{value}@r{]}
4123 @cindex @option{-gnateD} (@command{gcc})
4124 Defines a symbol, associated with @var{value}, for preprocessing.
4125 (@pxref{Integrated Preprocessing}).
4128 @cindex @option{-gnatef} (@command{gcc})
4129 Display full source path name in brief error messages.
4132 @cindex @option{-gnateG} (@command{gcc})
4133 Save result of preprocessing in a text file.
4135 @item -gnatem=@var{path}
4136 @cindex @option{-gnatem} (@command{gcc})
4137 Specify a mapping file
4139 (the equal sign is optional)
4141 (@pxref{Units to Sources Mapping Files}).
4143 @item -gnatep=@var{file}
4144 @cindex @option{-gnatep} (@command{gcc})
4145 Specify a preprocessing data file
4147 (the equal sign is optional)
4149 (@pxref{Integrated Preprocessing}).
4152 @cindex @option{-gnatE} (@command{gcc})
4153 Full dynamic elaboration checks.
4156 @cindex @option{-gnatf} (@command{gcc})
4157 Full errors. Multiple errors per line, all undefined references, do not
4158 attempt to suppress cascaded errors.
4161 @cindex @option{-gnatF} (@command{gcc})
4162 Externals names are folded to all uppercase.
4164 @item ^-gnatg^/GNAT_INTERNAL^
4165 @cindex @option{^-gnatg^/GNAT_INTERNAL^} (@command{gcc})
4166 Internal GNAT implementation mode. This should not be used for
4167 applications programs, it is intended only for use by the compiler
4168 and its run-time library. For documentation, see the GNAT sources.
4169 Note that @option{^-gnatg^/GNAT_INTERNAL^} implies
4170 @option{^-gnatwae^/WARNINGS=ALL,ERRORS^} and
4171 @option{^-gnatyg^/STYLE_CHECKS=GNAT^}
4172 so that all standard warnings and all standard style options are turned on.
4173 All warnings and style error messages are treated as errors.
4177 @cindex @option{-gnatG[nn]} (@command{gcc})
4180 @item /EXPAND_SOURCE, /LEXPAND_SOURCE=nnn
4182 List generated expanded code in source form.
4184 @item ^-gnath^/HELP^
4185 @cindex @option{^-gnath^/HELP^} (@command{gcc})
4186 Output usage information. The output is written to @file{stdout}.
4188 @item ^-gnati^/IDENTIFIER_CHARACTER_SET=^@var{c}
4189 @cindex @option{^-gnati^/IDENTIFIER_CHARACTER_SET^} (@command{gcc})
4190 Identifier character set
4192 (@var{c}=1/2/3/4/8/9/p/f/n/w).
4194 For details of the possible selections for @var{c},
4195 see @ref{Character Set Control}.
4197 @item ^-gnatI^/IGNORE_REP_CLAUSES^
4198 @cindex @option{^-gnatI^IGNORE_REP_CLAUSES^} (@command{gcc})
4199 Ignore representation clauses. When this switch is used,
4200 representation clauses are treated as comments. This is useful
4201 when initially porting code where you want to ignore rep clause
4202 problems, and also for compiling foreign code (particularly
4203 for use with ASIS). The representation clauses that are ignored
4204 are: enumeration_representation_clause, record_representation_clause,
4205 and attribute_definition_clause for the following attributes:
4206 Address, Alignment, Bit_Order, Component_Size, Machine_Radix,
4207 Object_Size, Size, Small, Stream_Size, and Value_Size.
4208 Note that this option should be used only for compiling -- the
4209 code is likely to malfunction at run time.
4212 @cindex @option{-gnatjnn} (@command{gcc})
4213 Reformat error messages to fit on nn character lines
4215 @item -gnatk=@var{n}
4216 @cindex @option{-gnatk} (@command{gcc})
4217 Limit file names to @var{n} (1-999) characters ^(@code{k} = krunch)^^.
4220 @cindex @option{-gnatl} (@command{gcc})
4221 Output full source listing with embedded error messages.
4224 @cindex @option{-gnatL} (@command{gcc})
4225 Used in conjunction with -gnatG or -gnatD to intersperse original
4226 source lines (as comment lines with line numbers) in the expanded
4229 @item -gnatm=@var{n}
4230 @cindex @option{-gnatm} (@command{gcc})
4231 Limit number of detected error or warning messages to @var{n}
4232 where @var{n} is in the range 1..999999. The default setting if
4233 no switch is given is 9999. If the number of warnings reaches this
4234 limit, then a message is output and further warnings are suppressed,
4235 but the compilation is continued. If the number of error messages
4236 reaches this limit, then a message is output and the compilation
4237 is abandoned. The equal sign here is optional. A value of zero
4238 means that no limit applies.
4241 @cindex @option{-gnatn} (@command{gcc})
4242 Activate inlining for subprograms for which
4243 pragma @code{inline} is specified. This inlining is performed
4244 by the GCC back-end.
4247 @cindex @option{-gnatN} (@command{gcc})
4248 Activate front end inlining for subprograms for which
4249 pragma @code{Inline} is specified. This inlining is performed
4250 by the front end and will be visible in the
4251 @option{-gnatG} output.
4253 When using a gcc-based back end (in practice this means using any version
4254 of GNAT other than the JGNAT, .NET or GNAAMP versions), then the use of
4255 @option{-gnatN} is deprecated, and the use of @option{-gnatn} is preferred.
4256 Historically front end inlining was more extensive than the gcc back end
4257 inlining, but that is no longer the case.
4260 @cindex @option{-gnato} (@command{gcc})
4261 Enable numeric overflow checking (which is not normally enabled by
4262 default). Note that division by zero is a separate check that is not
4263 controlled by this switch (division by zero checking is on by default).
4266 @cindex @option{-gnatp} (@command{gcc})
4267 Suppress all checks. See @ref{Run-Time Checks} for details.
4270 @cindex @option{-gnatP} (@command{gcc})
4271 Enable polling. This is required on some systems (notably Windows NT) to
4272 obtain asynchronous abort and asynchronous transfer of control capability.
4273 @xref{Pragma Polling,,, gnat_rm, GNAT Reference Manual}, for full
4277 @cindex @option{-gnatq} (@command{gcc})
4278 Don't quit. Try semantics, even if parse errors.
4281 @cindex @option{-gnatQ} (@command{gcc})
4282 Don't quit. Generate @file{ALI} and tree files even if illegalities.
4285 @cindex @option{-gnatr} (@command{gcc})
4286 Treat pragma Restrictions as Restriction_Warnings.
4288 @item ^-gnatR@r{[}0@r{/}1@r{/}2@r{/}3@r{[}s@r{]]}^/REPRESENTATION_INFO^
4289 @cindex @option{-gnatR} (@command{gcc})
4290 Output representation information for declared types and objects.
4293 @cindex @option{-gnats} (@command{gcc})
4297 @cindex @option{-gnatS} (@command{gcc})
4298 Print package Standard.
4301 @cindex @option{-gnatt} (@command{gcc})
4302 Generate tree output file.
4304 @item ^-gnatT^/TABLE_MULTIPLIER=^@var{nnn}
4305 @cindex @option{^-gnatT^/TABLE_MULTIPLIER^} (@command{gcc})
4306 All compiler tables start at @var{nnn} times usual starting size.
4309 @cindex @option{-gnatu} (@command{gcc})
4310 List units for this compilation.
4313 @cindex @option{-gnatU} (@command{gcc})
4314 Tag all error messages with the unique string ``error:''
4317 @cindex @option{-gnatv} (@command{gcc})
4318 Verbose mode. Full error output with source lines to @file{stdout}.
4321 @cindex @option{-gnatV} (@command{gcc})
4322 Control level of validity checking. See separate section describing
4325 @item ^-gnatw@var{xxx}^/WARNINGS=(@var{option}@r{[},@dots{}@r{]})^
4326 @cindex @option{^-gnatw^/WARNINGS^} (@command{gcc})
4328 ^@var{xxx} is a string of option letters that^the list of options^ denotes
4329 the exact warnings that
4330 are enabled or disabled (@pxref{Warning Message Control}).
4332 @item ^-gnatW^/WIDE_CHARACTER_ENCODING=^@var{e}
4333 @cindex @option{^-gnatW^/WIDE_CHARACTER_ENCODING^} (@command{gcc})
4334 Wide character encoding method
4336 (@var{e}=n/h/u/s/e/8).
4339 (@var{e}=@code{BRACKETS, NONE, HEX, UPPER, SHIFT_JIS, EUC, UTF8})
4343 @cindex @option{-gnatx} (@command{gcc})
4344 Suppress generation of cross-reference information.
4346 @item ^-gnaty^/STYLE_CHECKS=(option,option@dots{})^
4347 @cindex @option{^-gnaty^/STYLE_CHECKS^} (@command{gcc})
4348 Enable built-in style checks (@pxref{Style Checking}).
4350 @item ^-gnatz^/DISTRIBUTION_STUBS=^@var{m}
4351 @cindex @option{^-gnatz^/DISTRIBUTION_STUBS^} (@command{gcc})
4352 Distribution stub generation and compilation
4354 (@var{m}=r/c for receiver/caller stubs).
4357 (@var{m}=@code{RECEIVER} or @code{CALLER} to specify the type of stubs
4358 to be generated and compiled).
4361 @item ^-I^/SEARCH=^@var{dir}
4362 @cindex @option{^-I^/SEARCH^} (@command{gcc})
4364 Direct GNAT to search the @var{dir} directory for source files needed by
4365 the current compilation
4366 (@pxref{Search Paths and the Run-Time Library (RTL)}).
4368 @item ^-I-^/NOCURRENT_DIRECTORY^
4369 @cindex @option{^-I-^/NOCURRENT_DIRECTORY^} (@command{gcc})
4371 Except for the source file named in the command line, do not look for source
4372 files in the directory containing the source file named in the command line
4373 (@pxref{Search Paths and the Run-Time Library (RTL)}).
4377 @cindex @option{-mbig-switch} (@command{gcc})
4378 @cindex @code{case} statement (effect of @option{-mbig-switch} option)
4379 This standard gcc switch causes the compiler to use larger offsets in its
4380 jump table representation for @code{case} statements.
4381 This may result in less efficient code, but is sometimes necessary
4382 (for example on HP-UX targets)
4383 @cindex HP-UX and @option{-mbig-switch} option
4384 in order to compile large and/or nested @code{case} statements.
4387 @cindex @option{-o} (@command{gcc})
4388 This switch is used in @command{gcc} to redirect the generated object file
4389 and its associated ALI file. Beware of this switch with GNAT, because it may
4390 cause the object file and ALI file to have different names which in turn
4391 may confuse the binder and the linker.
4395 @cindex @option{-nostdinc} (@command{gcc})
4396 Inhibit the search of the default location for the GNAT Run Time
4397 Library (RTL) source files.
4400 @cindex @option{-nostdlib} (@command{gcc})
4401 Inhibit the search of the default location for the GNAT Run Time
4402 Library (RTL) ALI files.
4406 @cindex @option{-O} (@command{gcc})
4407 @var{n} controls the optimization level.
4411 No optimization, the default setting if no @option{-O} appears
4414 Normal optimization, the default if you specify @option{-O} without
4415 an operand. A good compromise between code quality and compilation
4419 Extensive optimization, may improve execution time, possibly at the cost of
4420 substantially increased compilation time.
4423 Same as @option{-O2}, and also includes inline expansion for small subprograms
4427 Optimize space usage
4431 See also @ref{Optimization Levels}.
4436 @cindex @option{/NOOPTIMIZE} (@code{GNAT COMPILE})
4437 Equivalent to @option{/OPTIMIZE=NONE}.
4438 This is the default behavior in the absence of an @option{/OPTIMIZE}
4441 @item /OPTIMIZE@r{[}=(keyword@r{[},@dots{}@r{]})@r{]}
4442 @cindex @option{/OPTIMIZE} (@code{GNAT COMPILE})
4443 Selects the level of optimization for your program. The supported
4444 keywords are as follows:
4447 Perform most optimizations, including those that
4449 This is the default if the @option{/OPTIMIZE} qualifier is supplied
4450 without keyword options.
4453 Do not do any optimizations. Same as @code{/NOOPTIMIZE}.
4456 Perform some optimizations, but omit ones that are costly.
4459 Same as @code{SOME}.
4462 Full optimization as in @option{/OPTIMIZE=ALL}, and also attempts
4463 automatic inlining of small subprograms within a unit
4466 Try to unroll loops. This keyword may be specified together with
4467 any keyword above other than @code{NONE}. Loop unrolling
4468 usually, but not always, improves the performance of programs.
4471 Optimize space usage
4475 See also @ref{Optimization Levels}.
4479 @item -pass-exit-codes
4480 @cindex @option{-pass-exit-codes} (@command{gcc})
4481 Catch exit codes from the compiler and use the most meaningful as
4485 @item --RTS=@var{rts-path}
4486 @cindex @option{--RTS} (@command{gcc})
4487 Specifies the default location of the runtime library. Same meaning as the
4488 equivalent @command{gnatmake} flag (@pxref{Switches for gnatmake}).
4491 @cindex @option{^-S^/ASM^} (@command{gcc})
4492 ^Used in place of @option{-c} to^Used to^
4493 cause the assembler source file to be
4494 generated, using @file{^.s^.S^} as the extension,
4495 instead of the object file.
4496 This may be useful if you need to examine the generated assembly code.
4498 @item ^-fverbose-asm^/VERBOSE_ASM^
4499 @cindex @option{^-fverbose-asm^/VERBOSE_ASM^} (@command{gcc})
4500 ^Used in conjunction with @option{-S}^Used in place of @option{/ASM}^
4501 to cause the generated assembly code file to be annotated with variable
4502 names, making it significantly easier to follow.
4505 @cindex @option{^-v^/VERBOSE^} (@command{gcc})
4506 Show commands generated by the @command{gcc} driver. Normally used only for
4507 debugging purposes or if you need to be sure what version of the
4508 compiler you are executing.
4512 @cindex @option{-V} (@command{gcc})
4513 Execute @var{ver} version of the compiler. This is the @command{gcc}
4514 version, not the GNAT version.
4517 @item ^-w^/NO_BACK_END_WARNINGS^
4518 @cindex @option{-w} (@command{gcc})
4519 Turn off warnings generated by the back end of the compiler. Use of
4520 this switch also causes the default for front end warnings to be set
4521 to suppress (as though @option{-gnatws} had appeared at the start of
4527 @c Combining qualifiers does not work on VMS
4528 You may combine a sequence of GNAT switches into a single switch. For
4529 example, the combined switch
4531 @cindex Combining GNAT switches
4537 is equivalent to specifying the following sequence of switches:
4540 -gnato -gnatf -gnati3
4545 The following restrictions apply to the combination of switches
4550 The switch @option{-gnatc} if combined with other switches must come
4551 first in the string.
4554 The switch @option{-gnats} if combined with other switches must come
4555 first in the string.
4559 @option{^-gnatz^/DISTRIBUTION_STUBS^}, @option{-gnatzc}, and @option{-gnatzr}
4560 may not be combined with any other switches.
4564 Once a ``y'' appears in the string (that is a use of the @option{-gnaty}
4565 switch), then all further characters in the switch are interpreted
4566 as style modifiers (see description of @option{-gnaty}).
4569 Once a ``d'' appears in the string (that is a use of the @option{-gnatd}
4570 switch), then all further characters in the switch are interpreted
4571 as debug flags (see description of @option{-gnatd}).
4574 Once a ``w'' appears in the string (that is a use of the @option{-gnatw}
4575 switch), then all further characters in the switch are interpreted
4576 as warning mode modifiers (see description of @option{-gnatw}).
4579 Once a ``V'' appears in the string (that is a use of the @option{-gnatV}
4580 switch), then all further characters in the switch are interpreted
4581 as validity checking options (see description of @option{-gnatV}).
4585 @node Output and Error Message Control
4586 @subsection Output and Error Message Control
4590 The standard default format for error messages is called ``brief format''.
4591 Brief format messages are written to @file{stderr} (the standard error
4592 file) and have the following form:
4595 e.adb:3:04: Incorrect spelling of keyword "function"
4596 e.adb:4:20: ";" should be "is"
4600 The first integer after the file name is the line number in the file,
4601 and the second integer is the column number within the line.
4603 @code{GPS} can parse the error messages
4604 and point to the referenced character.
4606 The following switches provide control over the error message
4612 @cindex @option{-gnatv} (@command{gcc})
4615 The v stands for verbose.
4617 The effect of this setting is to write long-format error
4618 messages to @file{stdout} (the standard output file.
4619 The same program compiled with the
4620 @option{-gnatv} switch would generate:
4624 3. funcion X (Q : Integer)
4626 >>> Incorrect spelling of keyword "function"
4629 >>> ";" should be "is"
4634 The vertical bar indicates the location of the error, and the @samp{>>>}
4635 prefix can be used to search for error messages. When this switch is
4636 used the only source lines output are those with errors.
4639 @cindex @option{-gnatl} (@command{gcc})
4641 The @code{l} stands for list.
4643 This switch causes a full listing of
4644 the file to be generated. In the case where a body is
4645 compiled, the corresponding spec is also listed, along
4646 with any subunits. Typical output from compiling a package
4647 body @file{p.adb} might look like:
4649 @smallexample @c ada
4653 1. package body p is
4655 3. procedure a is separate;
4666 2. pragma Elaborate_Body
4690 When you specify the @option{-gnatv} or @option{-gnatl} switches and
4691 standard output is redirected, a brief summary is written to
4692 @file{stderr} (standard error) giving the number of error messages and
4693 warning messages generated.
4695 @item -^gnatl^OUTPUT_FILE^=file
4696 @cindex @option{^-gnatl^OUTPUT_FILE^=fname} (@command{gcc})
4697 This has the same effect as @option{-gnatl} except that the output is
4698 written to a file instead of to standard output. If the given name
4699 @file{fname} does not start with a period, then it is the full name
4700 of the file to be written. If @file{fname} is an extension, it is
4701 appended to the name of the file being compiled. For example, if
4702 file @file{xyz.adb} is compiled with @option{^-gnatl^OUTPUT_FILE^=.lst},
4703 then the output is written to file ^xyz.adb.lst^xyz.adb_lst^.
4706 @cindex @option{-gnatU} (@command{gcc})
4707 This switch forces all error messages to be preceded by the unique
4708 string ``error:''. This means that error messages take a few more
4709 characters in space, but allows easy searching for and identification
4713 @cindex @option{-gnatb} (@command{gcc})
4715 The @code{b} stands for brief.
4717 This switch causes GNAT to generate the
4718 brief format error messages to @file{stderr} (the standard error
4719 file) as well as the verbose
4720 format message or full listing (which as usual is written to
4721 @file{stdout} (the standard output file).
4723 @item -gnatm=@var{n}
4724 @cindex @option{-gnatm} (@command{gcc})
4726 The @code{m} stands for maximum.
4728 @var{n} is a decimal integer in the
4729 range of 1 to 999999 and limits the number of error or warning
4730 messages to be generated. For example, using
4731 @option{-gnatm2} might yield
4734 e.adb:3:04: Incorrect spelling of keyword "function"
4735 e.adb:5:35: missing ".."
4736 fatal error: maximum number of errors detected
4737 compilation abandoned
4741 The default setting if
4742 no switch is given is 9999. If the number of warnings reaches this
4743 limit, then a message is output and further warnings are suppressed,
4744 but the compilation is continued. If the number of error messages
4745 reaches this limit, then a message is output and the compilation
4746 is abandoned. A value of zero means that no limit applies.
4749 Note that the equal sign is optional, so the switches
4750 @option{-gnatm2} and @option{-gnatm=2} are equivalent.
4753 @cindex @option{-gnatf} (@command{gcc})
4754 @cindex Error messages, suppressing
4756 The @code{f} stands for full.
4758 Normally, the compiler suppresses error messages that are likely to be
4759 redundant. This switch causes all error
4760 messages to be generated. In particular, in the case of
4761 references to undefined variables. If a given variable is referenced
4762 several times, the normal format of messages is
4764 e.adb:7:07: "V" is undefined (more references follow)
4768 where the parenthetical comment warns that there are additional
4769 references to the variable @code{V}. Compiling the same program with the
4770 @option{-gnatf} switch yields
4773 e.adb:7:07: "V" is undefined
4774 e.adb:8:07: "V" is undefined
4775 e.adb:8:12: "V" is undefined
4776 e.adb:8:16: "V" is undefined
4777 e.adb:9:07: "V" is undefined
4778 e.adb:9:12: "V" is undefined
4782 The @option{-gnatf} switch also generates additional information for
4783 some error messages. Some examples are:
4787 Full details on entities not available in high integrity mode
4789 Details on possibly non-portable unchecked conversion
4791 List possible interpretations for ambiguous calls
4793 Additional details on incorrect parameters
4797 @cindex @option{-gnatjnn} (@command{gcc})
4798 In normal operation mode (or if @option{-gnatj0} is used, then error messages
4799 with continuation lines are treated as though the continuation lines were
4800 separate messages (and so a warning with two continuation lines counts as
4801 three warnings, and is listed as three separate messages).
4803 If the @option{-gnatjnn} switch is used with a positive value for nn, then
4804 messages are output in a different manner. A message and all its continuation
4805 lines are treated as a unit, and count as only one warning or message in the
4806 statistics totals. Furthermore, the message is reformatted so that no line
4807 is longer than nn characters.
4810 @cindex @option{-gnatq} (@command{gcc})
4812 The @code{q} stands for quit (really ``don't quit'').
4814 In normal operation mode, the compiler first parses the program and
4815 determines if there are any syntax errors. If there are, appropriate
4816 error messages are generated and compilation is immediately terminated.
4818 GNAT to continue with semantic analysis even if syntax errors have been
4819 found. This may enable the detection of more errors in a single run. On
4820 the other hand, the semantic analyzer is more likely to encounter some
4821 internal fatal error when given a syntactically invalid tree.
4824 @cindex @option{-gnatQ} (@command{gcc})
4825 In normal operation mode, the @file{ALI} file is not generated if any
4826 illegalities are detected in the program. The use of @option{-gnatQ} forces
4827 generation of the @file{ALI} file. This file is marked as being in
4828 error, so it cannot be used for binding purposes, but it does contain
4829 reasonably complete cross-reference information, and thus may be useful
4830 for use by tools (e.g., semantic browsing tools or integrated development
4831 environments) that are driven from the @file{ALI} file. This switch
4832 implies @option{-gnatq}, since the semantic phase must be run to get a
4833 meaningful ALI file.
4835 In addition, if @option{-gnatt} is also specified, then the tree file is
4836 generated even if there are illegalities. It may be useful in this case
4837 to also specify @option{-gnatq} to ensure that full semantic processing
4838 occurs. The resulting tree file can be processed by ASIS, for the purpose
4839 of providing partial information about illegal units, but if the error
4840 causes the tree to be badly malformed, then ASIS may crash during the
4843 When @option{-gnatQ} is used and the generated @file{ALI} file is marked as
4844 being in error, @command{gnatmake} will attempt to recompile the source when it
4845 finds such an @file{ALI} file, including with switch @option{-gnatc}.
4847 Note that @option{-gnatQ} has no effect if @option{-gnats} is specified,
4848 since ALI files are never generated if @option{-gnats} is set.
4852 @node Warning Message Control
4853 @subsection Warning Message Control
4854 @cindex Warning messages
4856 In addition to error messages, which correspond to illegalities as defined
4857 in the Ada Reference Manual, the compiler detects two kinds of warning
4860 First, the compiler considers some constructs suspicious and generates a
4861 warning message to alert you to a possible error. Second, if the
4862 compiler detects a situation that is sure to raise an exception at
4863 run time, it generates a warning message. The following shows an example
4864 of warning messages:
4866 e.adb:4:24: warning: creation of object may raise Storage_Error
4867 e.adb:10:17: warning: static value out of range
4868 e.adb:10:17: warning: "Constraint_Error" will be raised at run time
4872 GNAT considers a large number of situations as appropriate
4873 for the generation of warning messages. As always, warnings are not
4874 definite indications of errors. For example, if you do an out-of-range
4875 assignment with the deliberate intention of raising a
4876 @code{Constraint_Error} exception, then the warning that may be
4877 issued does not indicate an error. Some of the situations for which GNAT
4878 issues warnings (at least some of the time) are given in the following
4879 list. This list is not complete, and new warnings are often added to
4880 subsequent versions of GNAT. The list is intended to give a general idea
4881 of the kinds of warnings that are generated.
4885 Possible infinitely recursive calls
4888 Out-of-range values being assigned
4891 Possible order of elaboration problems
4894 Assertions (pragma Assert) that are sure to fail
4900 Address clauses with possibly unaligned values, or where an attempt is
4901 made to overlay a smaller variable with a larger one.
4904 Fixed-point type declarations with a null range
4907 Direct_IO or Sequential_IO instantiated with a type that has access values
4910 Variables that are never assigned a value
4913 Variables that are referenced before being initialized
4916 Task entries with no corresponding @code{accept} statement
4919 Duplicate accepts for the same task entry in a @code{select}
4922 Objects that take too much storage
4925 Unchecked conversion between types of differing sizes
4928 Missing @code{return} statement along some execution path in a function
4931 Incorrect (unrecognized) pragmas
4934 Incorrect external names
4937 Allocation from empty storage pool
4940 Potentially blocking operation in protected type
4943 Suspicious parenthesization of expressions
4946 Mismatching bounds in an aggregate
4949 Attempt to return local value by reference
4952 Premature instantiation of a generic body
4955 Attempt to pack aliased components
4958 Out of bounds array subscripts
4961 Wrong length on string assignment
4964 Violations of style rules if style checking is enabled
4967 Unused @code{with} clauses
4970 @code{Bit_Order} usage that does not have any effect
4973 @code{Standard.Duration} used to resolve universal fixed expression
4976 Dereference of possibly null value
4979 Declaration that is likely to cause storage error
4982 Internal GNAT unit @code{with}'ed by application unit
4985 Values known to be out of range at compile time
4988 Unreferenced labels and variables
4991 Address overlays that could clobber memory
4994 Unexpected initialization when address clause present
4997 Bad alignment for address clause
5000 Useless type conversions
5003 Redundant assignment statements and other redundant constructs
5006 Useless exception handlers
5009 Accidental hiding of name by child unit
5012 Access before elaboration detected at compile time
5015 A range in a @code{for} loop that is known to be null or might be null
5020 The following section lists compiler switches that are available
5021 to control the handling of warning messages. It is also possible
5022 to exercise much finer control over what warnings are issued and
5023 suppressed using the GNAT pragma Warnings, @xref{Pragma Warnings,,,
5024 gnat_rm, GNAT Reference manual}.
5029 @emph{Activate all optional errors.}
5030 @cindex @option{-gnatwa} (@command{gcc})
5031 This switch activates most optional warning messages, see remaining list
5032 in this section for details on optional warning messages that can be
5033 individually controlled. The warnings that are not turned on by this
5035 @option{-gnatwd} (implicit dereferencing),
5036 @option{-gnatwh} (hiding),
5037 @option{-gnatwl} (elaboration warnings),
5038 @option{-gnatw.o} (warn on values set by out parameters ignored)
5039 and @option{-gnatwt} (tracking of deleted conditional code).
5040 All other optional warnings are turned on.
5043 @emph{Suppress all optional errors.}
5044 @cindex @option{-gnatwA} (@command{gcc})
5045 This switch suppresses all optional warning messages, see remaining list
5046 in this section for details on optional warning messages that can be
5047 individually controlled.
5050 @emph{Activate warnings on failing assertions.}
5051 @cindex @option{-gnatw.a} (@command{gcc})
5052 @cindex Assert failures
5053 This switch activates warnings for assertions where the compiler can tell at
5054 compile time that the assertion will fail. Note that this warning is given
5055 even if assertions are disabled. The default is that such warnings are
5059 @emph{Suppress warnings on failing assertions.}
5060 @cindex @option{-gnatw.A} (@command{gcc})
5061 @cindex Assert failures
5062 This switch suppresses warnings for assertions where the compiler can tell at
5063 compile time that the assertion will fail.
5066 @emph{Activate warnings on bad fixed values.}
5067 @cindex @option{-gnatwb} (@command{gcc})
5068 @cindex Bad fixed values
5069 @cindex Fixed-point Small value
5071 This switch activates warnings for static fixed-point expressions whose
5072 value is not an exact multiple of Small. Such values are implementation
5073 dependent, since an implementation is free to choose either of the multiples
5074 that surround the value. GNAT always chooses the closer one, but this is not
5075 required behavior, and it is better to specify a value that is an exact
5076 multiple, ensuring predictable execution. The default is that such warnings
5080 @emph{Suppress warnings on bad fixed values.}
5081 @cindex @option{-gnatwB} (@command{gcc})
5082 This switch suppresses warnings for static fixed-point expressions whose
5083 value is not an exact multiple of Small.
5086 @emph{Activate warnings on biased representation.}
5087 @cindex @option{-gnatw.b} (@command{gcc})
5088 @cindex Biased representation
5089 This switch activates warnings when a size clause, value size clause, component
5090 clause, or component size clause forces the use of biased representation for an
5091 integer type (e.g. representing a range of 10..11 in a single bit by using 0/1
5092 to represent 10/11). The default is that such warnings are generated.
5095 @emph{Suppress warnings on biased representation.}
5096 @cindex @option{-gnatwB} (@command{gcc})
5097 This switch suppresses warnings for representation clauses that force the use
5098 of biased representation.
5101 @emph{Activate warnings on conditionals.}
5102 @cindex @option{-gnatwc} (@command{gcc})
5103 @cindex Conditionals, constant
5104 This switch activates warnings for conditional expressions used in
5105 tests that are known to be True or False at compile time. The default
5106 is that such warnings are not generated.
5107 Note that this warning does
5108 not get issued for the use of boolean variables or constants whose
5109 values are known at compile time, since this is a standard technique
5110 for conditional compilation in Ada, and this would generate too many
5111 false positive warnings.
5113 This warning option also activates a special test for comparisons using
5114 the operators ``>='' and`` <=''.
5115 If the compiler can tell that only the equality condition is possible,
5116 then it will warn that the ``>'' or ``<'' part of the test
5117 is useless and that the operator could be replaced by ``=''.
5118 An example would be comparing a @code{Natural} variable <= 0.
5120 This warning option also generates warnings if
5121 one or both tests is optimized away in a membership test for integer
5122 values if the result can be determined at compile time. Range tests on
5123 enumeration types are not included, since it is common for such tests
5124 to include an end point.
5126 This warning can also be turned on using @option{-gnatwa}.
5129 @emph{Suppress warnings on conditionals.}
5130 @cindex @option{-gnatwC} (@command{gcc})
5131 This switch suppresses warnings for conditional expressions used in
5132 tests that are known to be True or False at compile time.
5135 @emph{Activate warnings on missing component clauses.}
5136 @cindex @option{-gnatw.c} (@command{gcc})
5137 @cindex Component clause, missing
5138 This switch activates warnings for record components where a record
5139 representation clause is present and has component clauses for the
5140 majority, but not all, of the components. A warning is given for each
5141 component for which no component clause is present.
5143 This warning can also be turned on using @option{-gnatwa}.
5146 @emph{Suppress warnings on missing component clauses.}
5147 @cindex @option{-gnatwC} (@command{gcc})
5148 This switch suppresses warnings for record components that are
5149 missing a component clause in the situation described above.
5152 @emph{Activate warnings on implicit dereferencing.}
5153 @cindex @option{-gnatwd} (@command{gcc})
5154 If this switch is set, then the use of a prefix of an access type
5155 in an indexed component, slice, or selected component without an
5156 explicit @code{.all} will generate a warning. With this warning
5157 enabled, access checks occur only at points where an explicit
5158 @code{.all} appears in the source code (assuming no warnings are
5159 generated as a result of this switch). The default is that such
5160 warnings are not generated.
5161 Note that @option{-gnatwa} does not affect the setting of
5162 this warning option.
5165 @emph{Suppress warnings on implicit dereferencing.}
5166 @cindex @option{-gnatwD} (@command{gcc})
5167 @cindex Implicit dereferencing
5168 @cindex Dereferencing, implicit
5169 This switch suppresses warnings for implicit dereferences in
5170 indexed components, slices, and selected components.
5173 @emph{Treat warnings as errors.}
5174 @cindex @option{-gnatwe} (@command{gcc})
5175 @cindex Warnings, treat as error
5176 This switch causes warning messages to be treated as errors.
5177 The warning string still appears, but the warning messages are counted
5178 as errors, and prevent the generation of an object file.
5181 @emph{Activate every optional warning}
5182 @cindex @option{-gnatw.e} (@command{gcc})
5183 @cindex Warnings, activate every optional warning
5184 This switch activates all optional warnings, including those which
5185 are not activated by @code{-gnatwa}.
5188 @emph{Activate warnings on unreferenced formals.}
5189 @cindex @option{-gnatwf} (@command{gcc})
5190 @cindex Formals, unreferenced
5191 This switch causes a warning to be generated if a formal parameter
5192 is not referenced in the body of the subprogram. This warning can
5193 also be turned on using @option{-gnatwa} or @option{-gnatwu}. The
5194 default is that these warnings are not generated.
5197 @emph{Suppress warnings on unreferenced formals.}
5198 @cindex @option{-gnatwF} (@command{gcc})
5199 This switch suppresses warnings for unreferenced formal
5200 parameters. Note that the
5201 combination @option{-gnatwu} followed by @option{-gnatwF} has the
5202 effect of warning on unreferenced entities other than subprogram
5206 @emph{Activate warnings on unrecognized pragmas.}
5207 @cindex @option{-gnatwg} (@command{gcc})
5208 @cindex Pragmas, unrecognized
5209 This switch causes a warning to be generated if an unrecognized
5210 pragma is encountered. Apart from issuing this warning, the
5211 pragma is ignored and has no effect. This warning can
5212 also be turned on using @option{-gnatwa}. The default
5213 is that such warnings are issued (satisfying the Ada Reference
5214 Manual requirement that such warnings appear).
5217 @emph{Suppress warnings on unrecognized pragmas.}
5218 @cindex @option{-gnatwG} (@command{gcc})
5219 This switch suppresses warnings for unrecognized pragmas.
5222 @emph{Activate warnings on hiding.}
5223 @cindex @option{-gnatwh} (@command{gcc})
5224 @cindex Hiding of Declarations
5225 This switch activates warnings on hiding declarations.
5226 A declaration is considered hiding
5227 if it is for a non-overloadable entity, and it declares an entity with the
5228 same name as some other entity that is directly or use-visible. The default
5229 is that such warnings are not generated.
5230 Note that @option{-gnatwa} does not affect the setting of this warning option.
5233 @emph{Suppress warnings on hiding.}
5234 @cindex @option{-gnatwH} (@command{gcc})
5235 This switch suppresses warnings on hiding declarations.
5238 @emph{Activate warnings on implementation units.}
5239 @cindex @option{-gnatwi} (@command{gcc})
5240 This switch activates warnings for a @code{with} of an internal GNAT
5241 implementation unit, defined as any unit from the @code{Ada},
5242 @code{Interfaces}, @code{GNAT},
5243 ^^@code{DEC},^ or @code{System}
5244 hierarchies that is not
5245 documented in either the Ada Reference Manual or the GNAT
5246 Programmer's Reference Manual. Such units are intended only
5247 for internal implementation purposes and should not be @code{with}'ed
5248 by user programs. The default is that such warnings are generated
5249 This warning can also be turned on using @option{-gnatwa}.
5252 @emph{Disable warnings on implementation units.}
5253 @cindex @option{-gnatwI} (@command{gcc})
5254 This switch disables warnings for a @code{with} of an internal GNAT
5255 implementation unit.
5258 @emph{Activate warnings on obsolescent features (Annex J).}
5259 @cindex @option{-gnatwj} (@command{gcc})
5260 @cindex Features, obsolescent
5261 @cindex Obsolescent features
5262 If this warning option is activated, then warnings are generated for
5263 calls to subprograms marked with @code{pragma Obsolescent} and
5264 for use of features in Annex J of the Ada Reference Manual. In the
5265 case of Annex J, not all features are flagged. In particular use
5266 of the renamed packages (like @code{Text_IO}) and use of package
5267 @code{ASCII} are not flagged, since these are very common and
5268 would generate many annoying positive warnings. The default is that
5269 such warnings are not generated. This warning is also turned on by
5270 the use of @option{-gnatwa}.
5272 In addition to the above cases, warnings are also generated for
5273 GNAT features that have been provided in past versions but which
5274 have been superseded (typically by features in the new Ada standard).
5275 For example, @code{pragma Ravenscar} will be flagged since its
5276 function is replaced by @code{pragma Profile(Ravenscar)}.
5278 Note that this warning option functions differently from the
5279 restriction @code{No_Obsolescent_Features} in two respects.
5280 First, the restriction applies only to annex J features.
5281 Second, the restriction does flag uses of package @code{ASCII}.
5284 @emph{Suppress warnings on obsolescent features (Annex J).}
5285 @cindex @option{-gnatwJ} (@command{gcc})
5286 This switch disables warnings on use of obsolescent features.
5289 @emph{Activate warnings on variables that could be constants.}
5290 @cindex @option{-gnatwk} (@command{gcc})
5291 This switch activates warnings for variables that are initialized but
5292 never modified, and then could be declared constants. The default is that
5293 such warnings are not given.
5294 This warning can also be turned on using @option{-gnatwa}.
5297 @emph{Suppress warnings on variables that could be constants.}
5298 @cindex @option{-gnatwK} (@command{gcc})
5299 This switch disables warnings on variables that could be declared constants.
5302 @emph{Activate warnings for elaboration pragmas.}
5303 @cindex @option{-gnatwl} (@command{gcc})
5304 @cindex Elaboration, warnings
5305 This switch activates warnings on missing
5306 @code{Elaborate_All} and @code{Elaborate} pragmas.
5307 See the section in this guide on elaboration checking for details on
5308 when such pragmas should be used. In dynamic elaboration mode, this switch
5309 generations warnings about the need to add elaboration pragmas. Note however,
5310 that if you blindly follow these warnings, and add @code{Elaborate_All}
5311 warnings wherever they are recommended, you basically end up with the
5312 equivalent of the static elaboration model, which may not be what you want for
5313 legacy code for which the static model does not work.
5315 For the static model, the messages generated are labeled "info:" (for
5316 information messages). They are not warnings to add elaboration pragmas,
5317 merely informational messages showing what implicit elaboration pragmas
5318 have been added, for use in analyzing elaboration circularity problems.
5320 Warnings are also generated if you
5321 are using the static mode of elaboration, and a @code{pragma Elaborate}
5322 is encountered. The default is that such warnings
5324 This warning is not automatically turned on by the use of @option{-gnatwa}.
5327 @emph{Suppress warnings for elaboration pragmas.}
5328 @cindex @option{-gnatwL} (@command{gcc})
5329 This switch suppresses warnings on missing Elaborate and Elaborate_All pragmas.
5330 See the section in this guide on elaboration checking for details on
5331 when such pragmas should be used.
5334 @emph{Activate warnings on modified but unreferenced variables.}
5335 @cindex @option{-gnatwm} (@command{gcc})
5336 This switch activates warnings for variables that are assigned (using
5337 an initialization value or with one or more assignment statements) but
5338 whose value is never read. The warning is suppressed for volatile
5339 variables and also for variables that are renamings of other variables
5340 or for which an address clause is given.
5341 This warning can also be turned on using @option{-gnatwa}.
5342 The default is that these warnings are not given.
5345 @emph{Disable warnings on modified but unreferenced variables.}
5346 @cindex @option{-gnatwM} (@command{gcc})
5347 This switch disables warnings for variables that are assigned or
5348 initialized, but never read.
5351 @emph{Set normal warnings mode.}
5352 @cindex @option{-gnatwn} (@command{gcc})
5353 This switch sets normal warning mode, in which enabled warnings are
5354 issued and treated as warnings rather than errors. This is the default
5355 mode. the switch @option{-gnatwn} can be used to cancel the effect of
5356 an explicit @option{-gnatws} or
5357 @option{-gnatwe}. It also cancels the effect of the
5358 implicit @option{-gnatwe} that is activated by the
5359 use of @option{-gnatg}.
5362 @emph{Activate warnings on address clause overlays.}
5363 @cindex @option{-gnatwo} (@command{gcc})
5364 @cindex Address Clauses, warnings
5365 This switch activates warnings for possibly unintended initialization
5366 effects of defining address clauses that cause one variable to overlap
5367 another. The default is that such warnings are generated.
5368 This warning can also be turned on using @option{-gnatwa}.
5371 @emph{Suppress warnings on address clause overlays.}
5372 @cindex @option{-gnatwO} (@command{gcc})
5373 This switch suppresses warnings on possibly unintended initialization
5374 effects of defining address clauses that cause one variable to overlap
5378 @emph{Activate warnings on modified but unreferenced out parameters.}
5379 @cindex @option{-gnatw.o} (@command{gcc})
5380 This switch activates warnings for variables that are modified by using
5381 them as actuals for a call to a procedure with an out mode formal, where
5382 the resulting assigned value is never read. It is applicable in the case
5383 where there is more than one out mode formal. If there is only one out
5384 mode formal, the warning is issued by default (controlled by -gnatwu).
5385 The warning is suppressed for volatile
5386 variables and also for variables that are renamings of other variables
5387 or for which an address clause is given.
5388 The default is that these warnings are not given. Note that this warning
5389 is not included in -gnatwa, it must be activated explicitly.
5392 @emph{Disable warnings on modified but unreferenced out parameters.}
5393 @cindex @option{-gnatw.O} (@command{gcc})
5394 This switch suppresses warnings for variables that are modified by using
5395 them as actuals for a call to a procedure with an out mode formal, where
5396 the resulting assigned value is never read.
5399 @emph{Activate warnings on ineffective pragma Inlines.}
5400 @cindex @option{-gnatwp} (@command{gcc})
5401 @cindex Inlining, warnings
5402 This switch activates warnings for failure of front end inlining
5403 (activated by @option{-gnatN}) to inline a particular call. There are
5404 many reasons for not being able to inline a call, including most
5405 commonly that the call is too complex to inline. The default is
5406 that such warnings are not given.
5407 This warning can also be turned on using @option{-gnatwa}.
5408 Warnings on ineffective inlining by the gcc back-end can be activated
5409 separately, using the gcc switch -Winline.
5412 @emph{Suppress warnings on ineffective pragma Inlines.}
5413 @cindex @option{-gnatwP} (@command{gcc})
5414 This switch suppresses warnings on ineffective pragma Inlines. If the
5415 inlining mechanism cannot inline a call, it will simply ignore the
5419 @emph{Activate warnings on parameter ordering.}
5420 @cindex @option{-gnatw.p} (@command{gcc})
5421 @cindex Parameter order, warnings
5422 This switch activates warnings for cases of suspicious parameter
5423 ordering when the list of arguments are all simple identifiers that
5424 match the names of the formals, but are in a different order. The
5425 warning is suppressed if any use of named parameter notation is used,
5426 so this is the appropriate way to suppress a false positive (and
5427 serves to emphasize that the "misordering" is deliberate). The
5429 that such warnings are not given.
5430 This warning can also be turned on using @option{-gnatwa}.
5433 @emph{Suppress warnings on parameter ordering.}
5434 @cindex @option{-gnatw.P} (@command{gcc})
5435 This switch suppresses warnings on cases of suspicious parameter
5439 @emph{Activate warnings on questionable missing parentheses.}
5440 @cindex @option{-gnatwq} (@command{gcc})
5441 @cindex Parentheses, warnings
5442 This switch activates warnings for cases where parentheses are not used and
5443 the result is potential ambiguity from a readers point of view. For example
5444 (not a > b) when a and b are modular means ((not a) > b) and very likely the
5445 programmer intended (not (a > b)). Similarly (-x mod 5) means (-(x mod 5)) and
5446 quite likely ((-x) mod 5) was intended. In such situations it seems best to
5447 follow the rule of always parenthesizing to make the association clear, and
5448 this warning switch warns if such parentheses are not present. The default
5449 is that these warnings are given.
5450 This warning can also be turned on using @option{-gnatwa}.
5453 @emph{Suppress warnings on questionable missing parentheses.}
5454 @cindex @option{-gnatwQ} (@command{gcc})
5455 This switch suppresses warnings for cases where the association is not
5456 clear and the use of parentheses is preferred.
5459 @emph{Activate warnings on redundant constructs.}
5460 @cindex @option{-gnatwr} (@command{gcc})
5461 This switch activates warnings for redundant constructs. The following
5462 is the current list of constructs regarded as redundant:
5466 Assignment of an item to itself.
5468 Type conversion that converts an expression to its own type.
5470 Use of the attribute @code{Base} where @code{typ'Base} is the same
5473 Use of pragma @code{Pack} when all components are placed by a record
5474 representation clause.
5476 Exception handler containing only a reraise statement (raise with no
5477 operand) which has no effect.
5479 Use of the operator abs on an operand that is known at compile time
5482 Comparison of boolean expressions to an explicit True value.
5485 This warning can also be turned on using @option{-gnatwa}.
5486 The default is that warnings for redundant constructs are not given.
5489 @emph{Suppress warnings on redundant constructs.}
5490 @cindex @option{-gnatwR} (@command{gcc})
5491 This switch suppresses warnings for redundant constructs.
5494 @emph{Activate warnings for object renaming function.}
5495 @cindex @option{-gnatw.r} (@command{gcc})
5496 This switch activates warnings for an object renaming that renames a
5497 function call, which is equivalent to a constant declaration (as
5498 opposed to renaming the function itself). The default is that these
5499 warnings are given. This warning can also be turned on using
5503 @emph{Suppress warnings for object renaming function.}
5504 @cindex @option{-gnatwT} (@command{gcc})
5505 This switch suppresses warnings for object renaming function.
5508 @emph{Suppress all warnings.}
5509 @cindex @option{-gnatws} (@command{gcc})
5510 This switch completely suppresses the
5511 output of all warning messages from the GNAT front end.
5512 Note that it does not suppress warnings from the @command{gcc} back end.
5513 To suppress these back end warnings as well, use the switch @option{-w}
5514 in addition to @option{-gnatws}.
5517 @emph{Activate warnings for tracking of deleted conditional code.}
5518 @cindex @option{-gnatwt} (@command{gcc})
5519 @cindex Deactivated code, warnings
5520 @cindex Deleted code, warnings
5521 This switch activates warnings for tracking of code in conditionals (IF and
5522 CASE statements) that is detected to be dead code which cannot be executed, and
5523 which is removed by the front end. This warning is off by default, and is not
5524 turned on by @option{-gnatwa}, it has to be turned on explicitly. This may be
5525 useful for detecting deactivated code in certified applications.
5528 @emph{Suppress warnings for tracking of deleted conditional code.}
5529 @cindex @option{-gnatwT} (@command{gcc})
5530 This switch suppresses warnings for tracking of deleted conditional code.
5533 @emph{Activate warnings on unused entities.}
5534 @cindex @option{-gnatwu} (@command{gcc})
5535 This switch activates warnings to be generated for entities that
5536 are declared but not referenced, and for units that are @code{with}'ed
5538 referenced. In the case of packages, a warning is also generated if
5539 no entities in the package are referenced. This means that if the package
5540 is referenced but the only references are in @code{use}
5541 clauses or @code{renames}
5542 declarations, a warning is still generated. A warning is also generated
5543 for a generic package that is @code{with}'ed but never instantiated.
5544 In the case where a package or subprogram body is compiled, and there
5545 is a @code{with} on the corresponding spec
5546 that is only referenced in the body,
5547 a warning is also generated, noting that the
5548 @code{with} can be moved to the body. The default is that
5549 such warnings are not generated.
5550 This switch also activates warnings on unreferenced formals
5551 (it includes the effect of @option{-gnatwf}).
5552 This warning can also be turned on using @option{-gnatwa}.
5555 @emph{Suppress warnings on unused entities.}
5556 @cindex @option{-gnatwU} (@command{gcc})
5557 This switch suppresses warnings for unused entities and packages.
5558 It also turns off warnings on unreferenced formals (and thus includes
5559 the effect of @option{-gnatwF}).
5562 @emph{Activate warnings on unassigned variables.}
5563 @cindex @option{-gnatwv} (@command{gcc})
5564 @cindex Unassigned variable warnings
5565 This switch activates warnings for access to variables which
5566 may not be properly initialized. The default is that
5567 such warnings are generated.
5568 This warning can also be turned on using @option{-gnatwa}.
5571 @emph{Suppress warnings on unassigned variables.}
5572 @cindex @option{-gnatwV} (@command{gcc})
5573 This switch suppresses warnings for access to variables which
5574 may not be properly initialized.
5575 For variables of a composite type, the warning can also be suppressed in
5576 Ada 2005 by using a default initialization with a box. For example, if
5577 Table is an array of records whose components are only partially uninitialized,
5578 then the following code:
5580 @smallexample @c ada
5581 Tab : Table := (others => <>);
5584 will suppress warnings on subsequent statements that access components
5588 @emph{Activate warnings on wrong low bound assumption.}
5589 @cindex @option{-gnatww} (@command{gcc})
5590 @cindex String indexing warnings
5591 This switch activates warnings for indexing an unconstrained string parameter
5592 with a literal or S'Length. This is a case where the code is assuming that the
5593 low bound is one, which is in general not true (for example when a slice is
5594 passed). The default is that such warnings are generated.
5595 This warning can also be turned on using @option{-gnatwa}.
5598 @emph{Suppress warnings on wrong low bound assumption.}
5599 @cindex @option{-gnatwW} (@command{gcc})
5600 This switch suppresses warnings for indexing an unconstrained string parameter
5601 with a literal or S'Length. Note that this warning can also be suppressed
5602 in a particular case by adding an
5603 assertion that the lower bound is 1,
5604 as shown in the following example.
5606 @smallexample @c ada
5607 procedure K (S : String) is
5608 pragma Assert (S'First = 1);
5613 @emph{Activate warnings on unnecessary Warnings Off pragmas}
5614 @cindex @option{-gnatw.w} (@command{gcc})
5615 @cindex Warnings Off control
5616 This switch activates warnings for use of @code{pragma Warnings (Off, entity}
5617 where either the pragma is entirely useless (because it suppresses no
5618 warnings), or it could be replaced by @code{pragma Unreferenced} or
5619 @code{pragma Unmodified}.The default is that these warnings are not given.
5620 Note that this warning is not included in -gnatwa, it must be
5621 activated explicitly.
5624 @emph{Suppress warnings on unnecessary Warnings Off pragmas}
5625 @cindex @option{-gnatw.W} (@command{gcc})
5626 This switch suppresses warnings for use of @code{pragma Warnings (Off, entity}.
5629 @emph{Activate warnings on Export/Import pragmas.}
5630 @cindex @option{-gnatwx} (@command{gcc})
5631 @cindex Export/Import pragma warnings
5632 This switch activates warnings on Export/Import pragmas when
5633 the compiler detects a possible conflict between the Ada and
5634 foreign language calling sequences. For example, the use of
5635 default parameters in a convention C procedure is dubious
5636 because the C compiler cannot supply the proper default, so
5637 a warning is issued. The default is that such warnings are
5639 This warning can also be turned on using @option{-gnatwa}.
5642 @emph{Suppress warnings on Export/Import pragmas.}
5643 @cindex @option{-gnatwX} (@command{gcc})
5644 This switch suppresses warnings on Export/Import pragmas.
5645 The sense of this is that you are telling the compiler that
5646 you know what you are doing in writing the pragma, and it
5647 should not complain at you.
5650 @emph{Activate warnings for No_Exception_Propagation mode.}
5651 @cindex @option{-gnatwm} (@command{gcc})
5652 This switch activates warnings for exception usage when pragma Restrictions
5653 (No_Exception_Propagation) is in effect. Warnings are given for implicit or
5654 explicit exception raises which are not covered by a local handler, and for
5655 exception handlers which do not cover a local raise. The default is that these
5656 warnings are not given.
5659 @emph{Disable warnings for No_Exception_Propagation mode.}
5660 This switch disables warnings for exception usage when pragma Restrictions
5661 (No_Exception_Propagation) is in effect.
5664 @emph{Activate warnings for Ada 2005 compatibility issues.}
5665 @cindex @option{-gnatwy} (@command{gcc})
5666 @cindex Ada 2005 compatibility issues warnings
5667 For the most part Ada 2005 is upwards compatible with Ada 95,
5668 but there are some exceptions (for example the fact that
5669 @code{interface} is now a reserved word in Ada 2005). This
5670 switch activates several warnings to help in identifying
5671 and correcting such incompatibilities. The default is that
5672 these warnings are generated. Note that at one point Ada 2005
5673 was called Ada 0Y, hence the choice of character.
5674 This warning can also be turned on using @option{-gnatwa}.
5677 @emph{Disable warnings for Ada 2005 compatibility issues.}
5678 @cindex @option{-gnatwY} (@command{gcc})
5679 @cindex Ada 2005 compatibility issues warnings
5680 This switch suppresses several warnings intended to help in identifying
5681 incompatibilities between Ada 95 and Ada 2005.
5684 @emph{Activate warnings on unchecked conversions.}
5685 @cindex @option{-gnatwz} (@command{gcc})
5686 @cindex Unchecked_Conversion warnings
5687 This switch activates warnings for unchecked conversions
5688 where the types are known at compile time to have different
5690 is that such warnings are generated. Warnings are also
5691 generated for subprogram pointers with different conventions,
5692 and, on VMS only, for data pointers with different conventions.
5693 This warning can also be turned on using @option{-gnatwa}.
5696 @emph{Suppress warnings on unchecked conversions.}
5697 @cindex @option{-gnatwZ} (@command{gcc})
5698 This switch suppresses warnings for unchecked conversions
5699 where the types are known at compile time to have different
5700 sizes or conventions.
5702 @item ^-Wunused^WARNINGS=UNUSED^
5703 @cindex @option{-Wunused}
5704 The warnings controlled by the @option{-gnatw} switch are generated by
5705 the front end of the compiler. The @option{GCC} back end can provide
5706 additional warnings and they are controlled by the @option{-W} switch.
5707 For example, @option{^-Wunused^WARNINGS=UNUSED^} activates back end
5708 warnings for entities that are declared but not referenced.
5710 @item ^-Wuninitialized^WARNINGS=UNINITIALIZED^
5711 @cindex @option{-Wuninitialized}
5712 Similarly, @option{^-Wuninitialized^WARNINGS=UNINITIALIZED^} activates
5713 the back end warning for uninitialized variables. This switch must be
5714 used in conjunction with an optimization level greater than zero.
5716 @item ^-Wall^/ALL_BACK_END_WARNINGS^
5717 @cindex @option{-Wall}
5718 This switch enables all the above warnings from the @option{GCC} back end.
5719 The code generator detects a number of warning situations that are missed
5720 by the @option{GNAT} front end, and this switch can be used to activate them.
5721 The use of this switch also sets the default front end warning mode to
5722 @option{-gnatwa}, that is, most front end warnings activated as well.
5724 @item ^-w^/NO_BACK_END_WARNINGS^
5726 Conversely, this switch suppresses warnings from the @option{GCC} back end.
5727 The use of this switch also sets the default front end warning mode to
5728 @option{-gnatws}, that is, front end warnings suppressed as well.
5734 A string of warning parameters can be used in the same parameter. For example:
5741 will turn on all optional warnings except for elaboration pragma warnings,
5742 and also specify that warnings should be treated as errors.
5744 When no switch @option{^-gnatw^/WARNINGS^} is used, this is equivalent to:
5769 @node Debugging and Assertion Control
5770 @subsection Debugging and Assertion Control
5774 @cindex @option{-gnata} (@command{gcc})
5780 The pragmas @code{Assert} and @code{Debug} normally have no effect and
5781 are ignored. This switch, where @samp{a} stands for assert, causes
5782 @code{Assert} and @code{Debug} pragmas to be activated.
5784 The pragmas have the form:
5788 @b{pragma} Assert (@var{Boolean-expression} @r{[},
5789 @var{static-string-expression}@r{]})
5790 @b{pragma} Debug (@var{procedure call})
5795 The @code{Assert} pragma causes @var{Boolean-expression} to be tested.
5796 If the result is @code{True}, the pragma has no effect (other than
5797 possible side effects from evaluating the expression). If the result is
5798 @code{False}, the exception @code{Assert_Failure} declared in the package
5799 @code{System.Assertions} is
5800 raised (passing @var{static-string-expression}, if present, as the
5801 message associated with the exception). If no string expression is
5802 given the default is a string giving the file name and line number
5805 The @code{Debug} pragma causes @var{procedure} to be called. Note that
5806 @code{pragma Debug} may appear within a declaration sequence, allowing
5807 debugging procedures to be called between declarations.
5810 @item /DEBUG@r{[}=debug-level@r{]}
5812 Specifies how much debugging information is to be included in
5813 the resulting object file where 'debug-level' is one of the following:
5816 Include both debugger symbol records and traceback
5818 This is the default setting.
5820 Include both debugger symbol records and traceback in
5823 Excludes both debugger symbol records and traceback
5824 the object file. Same as /NODEBUG.
5826 Includes only debugger symbol records in the object
5827 file. Note that this doesn't include traceback information.
5832 @node Validity Checking
5833 @subsection Validity Checking
5834 @findex Validity Checking
5837 The Ada Reference Manual has specific requirements for checking
5838 for invalid values. In particular, RM 13.9.1 requires that the
5839 evaluation of invalid values (for example from unchecked conversions),
5840 not result in erroneous execution. In GNAT, the result of such an
5841 evaluation in normal default mode is to either use the value
5842 unmodified, or to raise Constraint_Error in those cases where use
5843 of the unmodified value would cause erroneous execution. The cases
5844 where unmodified values might lead to erroneous execution are case
5845 statements (where a wild jump might result from an invalid value),
5846 and subscripts on the left hand side (where memory corruption could
5847 occur as a result of an invalid value).
5849 The @option{-gnatB} switch tells the compiler to assume that all
5850 values are valid (that is, within their declared subtype range)
5851 except in the context of a use of the Valid attribute. This means
5852 the compiler can generate more efficient code, since the range
5853 of values is better known at compile time.
5855 The @option{-gnatV^@var{x}^^} switch allows more control over the validity
5858 The @code{x} argument is a string of letters that
5859 indicate validity checks that are performed or not performed in addition
5860 to the default checks described above.
5863 The options allowed for this qualifier
5864 indicate validity checks that are performed or not performed in addition
5865 to the default checks described above.
5871 @emph{All validity checks.}
5872 @cindex @option{-gnatVa} (@command{gcc})
5873 All validity checks are turned on.
5875 That is, @option{-gnatVa} is
5876 equivalent to @option{gnatVcdfimorst}.
5880 @emph{Validity checks for copies.}
5881 @cindex @option{-gnatVc} (@command{gcc})
5882 The right hand side of assignments, and the initializing values of
5883 object declarations are validity checked.
5886 @emph{Default (RM) validity checks.}
5887 @cindex @option{-gnatVd} (@command{gcc})
5888 Some validity checks are done by default following normal Ada semantics
5890 A check is done in case statements that the expression is within the range
5891 of the subtype. If it is not, Constraint_Error is raised.
5892 For assignments to array components, a check is done that the expression used
5893 as index is within the range. If it is not, Constraint_Error is raised.
5894 Both these validity checks may be turned off using switch @option{-gnatVD}.
5895 They are turned on by default. If @option{-gnatVD} is specified, a subsequent
5896 switch @option{-gnatVd} will leave the checks turned on.
5897 Switch @option{-gnatVD} should be used only if you are sure that all such
5898 expressions have valid values. If you use this switch and invalid values
5899 are present, then the program is erroneous, and wild jumps or memory
5900 overwriting may occur.
5903 @emph{Validity checks for elementary components.}
5904 @cindex @option{-gnatVe} (@command{gcc})
5905 In the absence of this switch, assignments to record or array components are
5906 not validity checked, even if validity checks for assignments generally
5907 (@option{-gnatVc}) are turned on. In Ada, assignment of composite values do not
5908 require valid data, but assignment of individual components does. So for
5909 example, there is a difference between copying the elements of an array with a
5910 slice assignment, compared to assigning element by element in a loop. This
5911 switch allows you to turn off validity checking for components, even when they
5912 are assigned component by component.
5915 @emph{Validity checks for floating-point values.}
5916 @cindex @option{-gnatVf} (@command{gcc})
5917 In the absence of this switch, validity checking occurs only for discrete
5918 values. If @option{-gnatVf} is specified, then validity checking also applies
5919 for floating-point values, and NaNs and infinities are considered invalid,
5920 as well as out of range values for constrained types. Note that this means
5921 that standard IEEE infinity mode is not allowed. The exact contexts
5922 in which floating-point values are checked depends on the setting of other
5923 options. For example,
5924 @option{^-gnatVif^VALIDITY_CHECKING=(IN_PARAMS,FLOATS)^} or
5925 @option{^-gnatVfi^VALIDITY_CHECKING=(FLOATS,IN_PARAMS)^}
5926 (the order does not matter) specifies that floating-point parameters of mode
5927 @code{in} should be validity checked.
5930 @emph{Validity checks for @code{in} mode parameters}
5931 @cindex @option{-gnatVi} (@command{gcc})
5932 Arguments for parameters of mode @code{in} are validity checked in function
5933 and procedure calls at the point of call.
5936 @emph{Validity checks for @code{in out} mode parameters.}
5937 @cindex @option{-gnatVm} (@command{gcc})
5938 Arguments for parameters of mode @code{in out} are validity checked in
5939 procedure calls at the point of call. The @code{'m'} here stands for
5940 modify, since this concerns parameters that can be modified by the call.
5941 Note that there is no specific option to test @code{out} parameters,
5942 but any reference within the subprogram will be tested in the usual
5943 manner, and if an invalid value is copied back, any reference to it
5944 will be subject to validity checking.
5947 @emph{No validity checks.}
5948 @cindex @option{-gnatVn} (@command{gcc})
5949 This switch turns off all validity checking, including the default checking
5950 for case statements and left hand side subscripts. Note that the use of
5951 the switch @option{-gnatp} suppresses all run-time checks, including
5952 validity checks, and thus implies @option{-gnatVn}. When this switch
5953 is used, it cancels any other @option{-gnatV} previously issued.
5956 @emph{Validity checks for operator and attribute operands.}
5957 @cindex @option{-gnatVo} (@command{gcc})
5958 Arguments for predefined operators and attributes are validity checked.
5959 This includes all operators in package @code{Standard},
5960 the shift operators defined as intrinsic in package @code{Interfaces}
5961 and operands for attributes such as @code{Pos}. Checks are also made
5962 on individual component values for composite comparisons, and on the
5963 expressions in type conversions and qualified expressions. Checks are
5964 also made on explicit ranges using @samp{..} (e.g.@: slices, loops etc).
5967 @emph{Validity checks for parameters.}
5968 @cindex @option{-gnatVp} (@command{gcc})
5969 This controls the treatment of parameters within a subprogram (as opposed
5970 to @option{-gnatVi} and @option{-gnatVm} which control validity testing
5971 of parameters on a call. If either of these call options is used, then
5972 normally an assumption is made within a subprogram that the input arguments
5973 have been validity checking at the point of call, and do not need checking
5974 again within a subprogram). If @option{-gnatVp} is set, then this assumption
5975 is not made, and parameters are not assumed to be valid, so their validity
5976 will be checked (or rechecked) within the subprogram.
5979 @emph{Validity checks for function returns.}
5980 @cindex @option{-gnatVr} (@command{gcc})
5981 The expression in @code{return} statements in functions is validity
5985 @emph{Validity checks for subscripts.}
5986 @cindex @option{-gnatVs} (@command{gcc})
5987 All subscripts expressions are checked for validity, whether they appear
5988 on the right side or left side (in default mode only left side subscripts
5989 are validity checked).
5992 @emph{Validity checks for tests.}
5993 @cindex @option{-gnatVt} (@command{gcc})
5994 Expressions used as conditions in @code{if}, @code{while} or @code{exit}
5995 statements are checked, as well as guard expressions in entry calls.
6000 The @option{-gnatV} switch may be followed by
6001 ^a string of letters^a list of options^
6002 to turn on a series of validity checking options.
6004 @option{^-gnatVcr^/VALIDITY_CHECKING=(COPIES, RETURNS)^}
6005 specifies that in addition to the default validity checking, copies and
6006 function return expressions are to be validity checked.
6007 In order to make it easier
6008 to specify the desired combination of effects,
6010 the upper case letters @code{CDFIMORST} may
6011 be used to turn off the corresponding lower case option.
6014 the prefix @code{NO} on an option turns off the corresponding validity
6017 @item @code{NOCOPIES}
6018 @item @code{NODEFAULT}
6019 @item @code{NOFLOATS}
6020 @item @code{NOIN_PARAMS}
6021 @item @code{NOMOD_PARAMS}
6022 @item @code{NOOPERANDS}
6023 @item @code{NORETURNS}
6024 @item @code{NOSUBSCRIPTS}
6025 @item @code{NOTESTS}
6029 @option{^-gnatVaM^/VALIDITY_CHECKING=(ALL, NOMOD_PARAMS)^}
6030 turns on all validity checking options except for
6031 checking of @code{@b{in out}} procedure arguments.
6033 The specification of additional validity checking generates extra code (and
6034 in the case of @option{-gnatVa} the code expansion can be substantial).
6035 However, these additional checks can be very useful in detecting
6036 uninitialized variables, incorrect use of unchecked conversion, and other
6037 errors leading to invalid values. The use of pragma @code{Initialize_Scalars}
6038 is useful in conjunction with the extra validity checking, since this
6039 ensures that wherever possible uninitialized variables have invalid values.
6041 See also the pragma @code{Validity_Checks} which allows modification of
6042 the validity checking mode at the program source level, and also allows for
6043 temporary disabling of validity checks.
6045 @node Style Checking
6046 @subsection Style Checking
6047 @findex Style checking
6050 The @option{-gnaty^x^(option,option,@dots{})^} switch
6051 @cindex @option{-gnaty} (@command{gcc})
6052 causes the compiler to
6053 enforce specified style rules. A limited set of style rules has been used
6054 in writing the GNAT sources themselves. This switch allows user programs
6055 to activate all or some of these checks. If the source program fails a
6056 specified style check, an appropriate warning message is given, preceded by
6057 the character sequence ``(style)''.
6059 @code{(option,option,@dots{})} is a sequence of keywords
6062 The string @var{x} is a sequence of letters or digits
6064 indicating the particular style
6065 checks to be performed. The following checks are defined:
6070 @emph{Specify indentation level.}
6071 If a digit from 1-9 appears
6072 ^in the string after @option{-gnaty}^as an option for /STYLE_CHECKS^
6073 then proper indentation is checked, with the digit indicating the
6074 indentation level required. A value of zero turns off this style check.
6075 The general style of required indentation is as specified by
6076 the examples in the Ada Reference Manual. Full line comments must be
6077 aligned with the @code{--} starting on a column that is a multiple of
6078 the alignment level, or they may be aligned the same way as the following
6079 non-blank line (this is useful when full line comments appear in the middle
6083 @emph{Check attribute casing.}
6084 Attribute names, including the case of keywords such as @code{digits}
6085 used as attributes names, must be written in mixed case, that is, the
6086 initial letter and any letter following an underscore must be uppercase.
6087 All other letters must be lowercase.
6089 @item ^A^ARRAY_INDEXES^
6090 @emph{Use of array index numbers in array attributes.}
6091 When using the array attributes First, Last, Range,
6092 or Length, the index number must be omitted for one-dimensional arrays
6093 and is required for multi-dimensional arrays.
6096 @emph{Blanks not allowed at statement end.}
6097 Trailing blanks are not allowed at the end of statements. The purpose of this
6098 rule, together with h (no horizontal tabs), is to enforce a canonical format
6099 for the use of blanks to separate source tokens.
6102 @emph{Check comments.}
6103 Comments must meet the following set of rules:
6108 The ``@code{--}'' that starts the column must either start in column one,
6109 or else at least one blank must precede this sequence.
6112 Comments that follow other tokens on a line must have at least one blank
6113 following the ``@code{--}'' at the start of the comment.
6116 Full line comments must have two blanks following the ``@code{--}'' that
6117 starts the comment, with the following exceptions.
6120 A line consisting only of the ``@code{--}'' characters, possibly preceded
6121 by blanks is permitted.
6124 A comment starting with ``@code{--x}'' where @code{x} is a special character
6126 This allows proper processing of the output generated by specialized tools
6127 including @command{gnatprep} (where ``@code{--!}'' is used) and the SPARK
6129 language (where ``@code{--#}'' is used). For the purposes of this rule, a
6130 special character is defined as being in one of the ASCII ranges
6131 @code{16#21#@dots{}16#2F#} or @code{16#3A#@dots{}16#3F#}.
6132 Note that this usage is not permitted
6133 in GNAT implementation units (i.e., when @option{-gnatg} is used).
6136 A line consisting entirely of minus signs, possibly preceded by blanks, is
6137 permitted. This allows the construction of box comments where lines of minus
6138 signs are used to form the top and bottom of the box.
6141 A comment that starts and ends with ``@code{--}'' is permitted as long as at
6142 least one blank follows the initial ``@code{--}''. Together with the preceding
6143 rule, this allows the construction of box comments, as shown in the following
6146 ---------------------------
6147 -- This is a box comment --
6148 -- with two text lines. --
6149 ---------------------------
6153 @item ^d^DOS_LINE_ENDINGS^
6154 @emph{Check no DOS line terminators present.}
6155 All lines must be terminated by a single ASCII.LF
6156 character (in particular the DOS line terminator sequence CR/LF is not
6160 @emph{Check end/exit labels.}
6161 Optional labels on @code{end} statements ending subprograms and on
6162 @code{exit} statements exiting named loops, are required to be present.
6165 @emph{No form feeds or vertical tabs.}
6166 Neither form feeds nor vertical tab characters are permitted
6170 @emph{GNAT style mode}
6171 The set of style check switches is set to match that used by the GNAT sources.
6172 This may be useful when developing code that is eventually intended to be
6173 incorporated into GNAT. For further details, see GNAT sources.
6176 @emph{No horizontal tabs.}
6177 Horizontal tab characters are not permitted in the source text.
6178 Together with the b (no blanks at end of line) check, this
6179 enforces a canonical form for the use of blanks to separate
6183 @emph{Check if-then layout.}
6184 The keyword @code{then} must appear either on the same
6185 line as corresponding @code{if}, or on a line on its own, lined
6186 up under the @code{if} with at least one non-blank line in between
6187 containing all or part of the condition to be tested.
6190 @emph{check mode IN keywords}
6191 Mode @code{in} (the default mode) is not
6192 allowed to be given explicitly. @code{in out} is fine,
6193 but not @code{in} on its own.
6196 @emph{Check keyword casing.}
6197 All keywords must be in lower case (with the exception of keywords
6198 such as @code{digits} used as attribute names to which this check
6202 @emph{Check layout.}
6203 Layout of statement and declaration constructs must follow the
6204 recommendations in the Ada Reference Manual, as indicated by the
6205 form of the syntax rules. For example an @code{else} keyword must
6206 be lined up with the corresponding @code{if} keyword.
6208 There are two respects in which the style rule enforced by this check
6209 option are more liberal than those in the Ada Reference Manual. First
6210 in the case of record declarations, it is permissible to put the
6211 @code{record} keyword on the same line as the @code{type} keyword, and
6212 then the @code{end} in @code{end record} must line up under @code{type}.
6213 This is also permitted when the type declaration is split on two lines.
6214 For example, any of the following three layouts is acceptable:
6216 @smallexample @c ada
6239 Second, in the case of a block statement, a permitted alternative
6240 is to put the block label on the same line as the @code{declare} or
6241 @code{begin} keyword, and then line the @code{end} keyword up under
6242 the block label. For example both the following are permitted:
6244 @smallexample @c ada
6262 The same alternative format is allowed for loops. For example, both of
6263 the following are permitted:
6265 @smallexample @c ada
6267 Clear : while J < 10 loop
6278 @item ^Lnnn^MAX_NESTING=nnn^
6279 @emph{Set maximum nesting level}
6280 The maximum level of nesting of constructs (including subprograms, loops,
6281 blocks, packages, and conditionals) may not exceed the given value
6282 @option{nnn}. A value of zero disconnects this style check.
6284 @item ^m^LINE_LENGTH^
6285 @emph{Check maximum line length.}
6286 The length of source lines must not exceed 79 characters, including
6287 any trailing blanks. The value of 79 allows convenient display on an
6288 80 character wide device or window, allowing for possible special
6289 treatment of 80 character lines. Note that this count is of
6290 characters in the source text. This means that a tab character counts
6291 as one character in this count but a wide character sequence counts as
6292 a single character (however many bytes are needed in the encoding).
6294 @item ^Mnnn^MAX_LENGTH=nnn^
6295 @emph{Set maximum line length.}
6296 The length of lines must not exceed the
6297 given value @option{nnn}. The maximum value that can be specified is 32767.
6299 @item ^n^STANDARD_CASING^
6300 @emph{Check casing of entities in Standard.}
6301 Any identifier from Standard must be cased
6302 to match the presentation in the Ada Reference Manual (for example,
6303 @code{Integer} and @code{ASCII.NUL}).
6306 @emph{Turn off all style checks}
6307 All style check options are turned off.
6309 @item ^o^ORDERED_SUBPROGRAMS^
6310 @emph{Check order of subprogram bodies.}
6311 All subprogram bodies in a given scope
6312 (e.g.@: a package body) must be in alphabetical order. The ordering
6313 rule uses normal Ada rules for comparing strings, ignoring casing
6314 of letters, except that if there is a trailing numeric suffix, then
6315 the value of this suffix is used in the ordering (e.g.@: Junk2 comes
6318 @item ^O^OVERRIDING_INDICATORS^
6319 @emph{Check that overriding subprograms are explicitly marked as such.}
6320 The declaration of a primitive operation of a type extension that overrides
6321 an inherited operation must carry an overriding indicator.
6324 @emph{Check pragma casing.}
6325 Pragma names must be written in mixed case, that is, the
6326 initial letter and any letter following an underscore must be uppercase.
6327 All other letters must be lowercase.
6329 @item ^r^REFERENCES^
6330 @emph{Check references.}
6331 All identifier references must be cased in the same way as the
6332 corresponding declaration. No specific casing style is imposed on
6333 identifiers. The only requirement is for consistency of references
6336 @item ^S^STATEMENTS_AFTER_THEN_ELSE^
6337 @emph{Check no statements after THEN/ELSE.}
6338 No statements are allowed
6339 on the same line as a THEN or ELSE keyword following the
6340 keyword in an IF statement. OR ELSE and AND THEN are not affected,
6341 and a special exception allows a pragma to appear after ELSE.
6344 @emph{Check separate specs.}
6345 Separate declarations (``specs'') are required for subprograms (a
6346 body is not allowed to serve as its own declaration). The only
6347 exception is that parameterless library level procedures are
6348 not required to have a separate declaration. This exception covers
6349 the most frequent form of main program procedures.
6352 @emph{Check token spacing.}
6353 The following token spacing rules are enforced:
6358 The keywords @code{@b{abs}} and @code{@b{not}} must be followed by a space.
6361 The token @code{=>} must be surrounded by spaces.
6364 The token @code{<>} must be preceded by a space or a left parenthesis.
6367 Binary operators other than @code{**} must be surrounded by spaces.
6368 There is no restriction on the layout of the @code{**} binary operator.
6371 Colon must be surrounded by spaces.
6374 Colon-equal (assignment, initialization) must be surrounded by spaces.
6377 Comma must be the first non-blank character on the line, or be
6378 immediately preceded by a non-blank character, and must be followed
6382 If the token preceding a left parenthesis ends with a letter or digit, then
6383 a space must separate the two tokens.
6386 A right parenthesis must either be the first non-blank character on
6387 a line, or it must be preceded by a non-blank character.
6390 A semicolon must not be preceded by a space, and must not be followed by
6391 a non-blank character.
6394 A unary plus or minus may not be followed by a space.
6397 A vertical bar must be surrounded by spaces.
6400 @item ^u^UNNECESSARY_BLANK_LINES^
6401 @emph{Check unnecessary blank lines.}
6402 Unnecessary blank lines are not allowed. A blank line is considered
6403 unnecessary if it appears at the end of the file, or if more than
6404 one blank line occurs in sequence.
6406 @item ^x^XTRA_PARENS^
6407 @emph{Check extra parentheses.}
6408 Unnecessary extra level of parentheses (C-style) are not allowed
6409 around conditions in @code{if} statements, @code{while} statements and
6410 @code{exit} statements.
6412 @item ^y^ALL_BUILTIN^
6413 @emph{Set all standard style check options}
6414 This is equivalent to @code{gnaty3aAbcefhiklmnprst}, that is all checking
6415 options enabled with the exception of @option{-gnatyo}, @option{-gnatyI},
6416 @option{-gnatyS}, @option{-gnatyLnnn},
6417 @option{-gnatyd}, @option{-gnatyu}, and @option{-gnatyx}.
6421 @emph{Remove style check options}
6422 This causes any subsequent options in the string to act as canceling the
6423 corresponding style check option. To cancel maximum nesting level control,
6424 use @option{L} parameter witout any integer value after that, because any
6425 digit following @option{-} in the parameter string of the @option{-gnaty}
6426 option will be threated as canceling indentation check. The same is true
6427 for @option{M} parameter. @option{y} and @option{N} parameters are not
6428 allowed after @option{-}.
6431 This causes any subsequent options in the string to enable the corresponding
6432 style check option. That is, it cancels the effect of a previous ^-^REMOVE^,
6438 @emph{Removing style check options}
6439 If the name of a style check is preceded by @option{NO} then the corresponding
6440 style check is turned off. For example @option{NOCOMMENTS} turns off style
6441 checking for comments.
6446 In the above rules, appearing in column one is always permitted, that is,
6447 counts as meeting either a requirement for a required preceding space,
6448 or as meeting a requirement for no preceding space.
6450 Appearing at the end of a line is also always permitted, that is, counts
6451 as meeting either a requirement for a following space, or as meeting
6452 a requirement for no following space.
6455 If any of these style rules is violated, a message is generated giving
6456 details on the violation. The initial characters of such messages are
6457 always ``@code{(style)}''. Note that these messages are treated as warning
6458 messages, so they normally do not prevent the generation of an object
6459 file. The @option{-gnatwe} switch can be used to treat warning messages,
6460 including style messages, as fatal errors.
6464 @option{-gnaty} on its own (that is not
6465 followed by any letters or digits), then the effect is equivalent
6466 to the use of @option{-gnatyy}, as described above, that is all
6467 built-in standard style check options are enabled.
6471 /STYLE_CHECKS=ALL_BUILTIN enables all checking options with
6472 the exception of ORDERED_SUBPROGRAMS, UNNECESSARY_BLANK_LINES,
6473 XTRA_PARENS, and DOS_LINE_ENDINGS. In addition
6485 clears any previously set style checks.
6487 @node Run-Time Checks
6488 @subsection Run-Time Checks
6489 @cindex Division by zero
6490 @cindex Access before elaboration
6491 @cindex Checks, division by zero
6492 @cindex Checks, access before elaboration
6493 @cindex Checks, stack overflow checking
6496 By default, the following checks are suppressed: integer overflow
6497 checks, stack overflow checks, and checks for access before
6498 elaboration on subprogram calls. All other checks, including range
6499 checks and array bounds checks, are turned on by default. The
6500 following @command{gcc} switches refine this default behavior.
6505 @cindex @option{-gnatp} (@command{gcc})
6506 @cindex Suppressing checks
6507 @cindex Checks, suppressing
6509 Suppress all run-time checks as though @code{pragma Suppress (All_checks)}
6510 had been present in the source. Validity checks are also suppressed (in
6511 other words @option{-gnatp} also implies @option{-gnatVn}.
6512 Use this switch to improve the performance
6513 of the code at the expense of safety in the presence of invalid data or
6516 Note that when checks are suppressed, the compiler is allowed, but not
6517 required, to omit the checking code. If the run-time cost of the
6518 checking code is zero or near-zero, the compiler will generate it even
6519 if checks are suppressed. In particular, if the compiler can prove
6520 that a certain check will necessarily fail, it will generate code to
6521 do an unconditional ``raise'', even if checks are suppressed. The
6522 compiler warns in this case.
6524 Of course, run-time checks are omitted whenever the compiler can prove
6525 that they will not fail, whether or not checks are suppressed.
6527 Note that if you suppress a check that would have failed, program
6528 execution is erroneous, which means the behavior is totally
6529 unpredictable. The program might crash, or print wrong answers, or
6530 do anything else. It might even do exactly what you wanted it to do
6531 (and then it might start failing mysteriously next week or next
6532 year). The compiler will generate code based on the assumption that
6533 the condition being checked is true, which can result in disaster if
6534 that assumption is wrong.
6537 @cindex @option{-gnato} (@command{gcc})
6538 @cindex Overflow checks
6539 @cindex Check, overflow
6540 Enables overflow checking for integer operations.
6541 This causes GNAT to generate slower and larger executable
6542 programs by adding code to check for overflow (resulting in raising
6543 @code{Constraint_Error} as required by standard Ada
6544 semantics). These overflow checks correspond to situations in which
6545 the true value of the result of an operation may be outside the base
6546 range of the result type. The following example shows the distinction:
6548 @smallexample @c ada
6549 X1 : Integer := "Integer'Last";
6550 X2 : Integer range 1 .. 5 := "5";
6551 X3 : Integer := "Integer'Last";
6552 X4 : Integer range 1 .. 5 := "5";
6553 F : Float := "2.0E+20";
6562 Note that if explicit values are assigned at compile time, the
6563 compiler may be able to detect overflow at compile time, in which case
6564 no actual run-time checking code is required, and Constraint_Error
6565 will be raised unconditionally, with or without
6566 @option{-gnato}. That's why the assigned values in the above fragment
6567 are in quotes, the meaning is "assign a value not known to the
6568 compiler that happens to be equal to ...". The remaining discussion
6569 assumes that the compiler cannot detect the values at compile time.
6571 Here the first addition results in a value that is outside the base range
6572 of Integer, and hence requires an overflow check for detection of the
6573 constraint error. Thus the first assignment to @code{X1} raises a
6574 @code{Constraint_Error} exception only if @option{-gnato} is set.
6576 The second increment operation results in a violation of the explicit
6577 range constraint; such range checks are performed by default, and are
6578 unaffected by @option{-gnato}.
6580 The two conversions of @code{F} both result in values that are outside
6581 the base range of type @code{Integer} and thus will raise
6582 @code{Constraint_Error} exceptions only if @option{-gnato} is used.
6583 The fact that the result of the second conversion is assigned to
6584 variable @code{X4} with a restricted range is irrelevant, since the problem
6585 is in the conversion, not the assignment.
6587 Basically the rule is that in the default mode (@option{-gnato} not
6588 used), the generated code assures that all integer variables stay
6589 within their declared ranges, or within the base range if there is
6590 no declared range. This prevents any serious problems like indexes
6591 out of range for array operations.
6593 What is not checked in default mode is an overflow that results in
6594 an in-range, but incorrect value. In the above example, the assignments
6595 to @code{X1}, @code{X2}, @code{X3} all give results that are within the
6596 range of the target variable, but the result is wrong in the sense that
6597 it is too large to be represented correctly. Typically the assignment
6598 to @code{X1} will result in wrap around to the largest negative number.
6599 The conversions of @code{F} will result in some @code{Integer} value
6600 and if that integer value is out of the @code{X4} range then the
6601 subsequent assignment would generate an exception.
6603 @findex Machine_Overflows
6604 Note that the @option{-gnato} switch does not affect the code generated
6605 for any floating-point operations; it applies only to integer
6607 For floating-point, GNAT has the @code{Machine_Overflows}
6608 attribute set to @code{False} and the normal mode of operation is to
6609 generate IEEE NaN and infinite values on overflow or invalid operations
6610 (such as dividing 0.0 by 0.0).
6612 The reason that we distinguish overflow checking from other kinds of
6613 range constraint checking is that a failure of an overflow check, unlike
6614 for example the failure of a range check, can result in an incorrect
6615 value, but cannot cause random memory destruction (like an out of range
6616 subscript), or a wild jump (from an out of range case value). Overflow
6617 checking is also quite expensive in time and space, since in general it
6618 requires the use of double length arithmetic.
6620 Note again that @option{-gnato} is off by default, so overflow checking is
6621 not performed in default mode. This means that out of the box, with the
6622 default settings, GNAT does not do all the checks expected from the
6623 language description in the Ada Reference Manual. If you want all constraint
6624 checks to be performed, as described in this Manual, then you must
6625 explicitly use the -gnato switch either on the @command{gnatmake} or
6626 @command{gcc} command.
6629 @cindex @option{-gnatE} (@command{gcc})
6630 @cindex Elaboration checks
6631 @cindex Check, elaboration
6632 Enables dynamic checks for access-before-elaboration
6633 on subprogram calls and generic instantiations.
6634 Note that @option{-gnatE} is not necessary for safety, because in the
6635 default mode, GNAT ensures statically that the checks would not fail.
6636 For full details of the effect and use of this switch,
6637 @xref{Compiling Using gcc}.
6640 @cindex @option{-fstack-check} (@command{gcc})
6641 @cindex Stack Overflow Checking
6642 @cindex Checks, stack overflow checking
6643 Activates stack overflow checking. For full details of the effect and use of
6644 this switch see @ref{Stack Overflow Checking}.
6649 The setting of these switches only controls the default setting of the
6650 checks. You may modify them using either @code{Suppress} (to remove
6651 checks) or @code{Unsuppress} (to add back suppressed checks) pragmas in
6654 @node Using gcc for Syntax Checking
6655 @subsection Using @command{gcc} for Syntax Checking
6658 @cindex @option{-gnats} (@command{gcc})
6662 The @code{s} stands for ``syntax''.
6665 Run GNAT in syntax checking only mode. For
6666 example, the command
6669 $ gcc -c -gnats x.adb
6673 compiles file @file{x.adb} in syntax-check-only mode. You can check a
6674 series of files in a single command
6676 , and can use wild cards to specify such a group of files.
6677 Note that you must specify the @option{-c} (compile
6678 only) flag in addition to the @option{-gnats} flag.
6681 You may use other switches in conjunction with @option{-gnats}. In
6682 particular, @option{-gnatl} and @option{-gnatv} are useful to control the
6683 format of any generated error messages.
6685 When the source file is empty or contains only empty lines and/or comments,
6686 the output is a warning:
6689 $ gcc -c -gnats -x ada toto.txt
6690 toto.txt:1:01: warning: empty file, contains no compilation units
6694 Otherwise, the output is simply the error messages, if any. No object file or
6695 ALI file is generated by a syntax-only compilation. Also, no units other
6696 than the one specified are accessed. For example, if a unit @code{X}
6697 @code{with}'s a unit @code{Y}, compiling unit @code{X} in syntax
6698 check only mode does not access the source file containing unit
6701 @cindex Multiple units, syntax checking
6702 Normally, GNAT allows only a single unit in a source file. However, this
6703 restriction does not apply in syntax-check-only mode, and it is possible
6704 to check a file containing multiple compilation units concatenated
6705 together. This is primarily used by the @code{gnatchop} utility
6706 (@pxref{Renaming Files Using gnatchop}).
6709 @node Using gcc for Semantic Checking
6710 @subsection Using @command{gcc} for Semantic Checking
6713 @cindex @option{-gnatc} (@command{gcc})
6717 The @code{c} stands for ``check''.
6719 Causes the compiler to operate in semantic check mode,
6720 with full checking for all illegalities specified in the
6721 Ada Reference Manual, but without generation of any object code
6722 (no object file is generated).
6724 Because dependent files must be accessed, you must follow the GNAT
6725 semantic restrictions on file structuring to operate in this mode:
6729 The needed source files must be accessible
6730 (@pxref{Search Paths and the Run-Time Library (RTL)}).
6733 Each file must contain only one compilation unit.
6736 The file name and unit name must match (@pxref{File Naming Rules}).
6739 The output consists of error messages as appropriate. No object file is
6740 generated. An @file{ALI} file is generated for use in the context of
6741 cross-reference tools, but this file is marked as not being suitable
6742 for binding (since no object file is generated).
6743 The checking corresponds exactly to the notion of
6744 legality in the Ada Reference Manual.
6746 Any unit can be compiled in semantics-checking-only mode, including
6747 units that would not normally be compiled (subunits,
6748 and specifications where a separate body is present).
6751 @node Compiling Different Versions of Ada
6752 @subsection Compiling Different Versions of Ada
6755 The switches described in this section allow you to explicitly specify
6756 the version of the Ada language that your programs are written in.
6757 By default @value{EDITION} assumes @value{DEFAULTLANGUAGEVERSION},
6758 but you can also specify @value{NONDEFAULTLANGUAGEVERSION} or
6759 indicate Ada 83 compatibility mode.
6762 @cindex Compatibility with Ada 83
6764 @item -gnat83 (Ada 83 Compatibility Mode)
6765 @cindex @option{-gnat83} (@command{gcc})
6766 @cindex ACVC, Ada 83 tests
6770 Although GNAT is primarily an Ada 95 / Ada 2005 compiler, this switch
6771 specifies that the program is to be compiled in Ada 83 mode. With
6772 @option{-gnat83}, GNAT rejects most post-Ada 83 extensions and applies Ada 83
6773 semantics where this can be done easily.
6774 It is not possible to guarantee this switch does a perfect
6775 job; some subtle tests, such as are
6776 found in earlier ACVC tests (and that have been removed from the ACATS suite
6777 for Ada 95), might not compile correctly.
6778 Nevertheless, this switch may be useful in some circumstances, for example
6779 where, due to contractual reasons, existing code needs to be maintained
6780 using only Ada 83 features.
6782 With few exceptions (most notably the need to use @code{<>} on
6783 @cindex Generic formal parameters
6784 unconstrained generic formal parameters, the use of the new Ada 95 / Ada 2005
6785 reserved words, and the use of packages
6786 with optional bodies), it is not necessary to specify the
6787 @option{-gnat83} switch when compiling Ada 83 programs, because, with rare
6788 exceptions, Ada 95 and Ada 2005 are upwardly compatible with Ada 83. Thus
6789 a correct Ada 83 program is usually also a correct program
6790 in these later versions of the language standard.
6791 For further information, please refer to @ref{Compatibility and Porting Guide}.
6793 @item -gnat95 (Ada 95 mode)
6794 @cindex @option{-gnat95} (@command{gcc})
6798 This switch directs the compiler to implement the Ada 95 version of the
6800 Since Ada 95 is almost completely upwards
6801 compatible with Ada 83, Ada 83 programs may generally be compiled using
6802 this switch (see the description of the @option{-gnat83} switch for further
6803 information about Ada 83 mode).
6804 If an Ada 2005 program is compiled in Ada 95 mode,
6805 uses of the new Ada 2005 features will cause error
6806 messages or warnings.
6808 This switch also can be used to cancel the effect of a previous
6809 @option{-gnat83} or @option{-gnat05} switch earlier in the command line.
6811 @item -gnat05 (Ada 2005 mode)
6812 @cindex @option{-gnat05} (@command{gcc})
6813 @cindex Ada 2005 mode
6816 This switch directs the compiler to implement the Ada 2005 version of the
6818 Since Ada 2005 is almost completely upwards
6819 compatible with Ada 95 (and thus also with Ada 83), Ada 83 and Ada 95 programs
6820 may generally be compiled using this switch (see the description of the
6821 @option{-gnat83} and @option{-gnat95} switches for further
6824 For information about the approved ``Ada Issues'' that have been incorporated
6825 into Ada 2005, see @url{http://www.ada-auth.org/cgi-bin/cvsweb.cgi/AIs}.
6826 Included with GNAT releases is a file @file{features-ada0y} that describes
6827 the set of implemented Ada 2005 features.
6831 @node Character Set Control
6832 @subsection Character Set Control
6834 @item ^-gnati^/IDENTIFIER_CHARACTER_SET=^@var{c}
6835 @cindex @option{^-gnati^/IDENTIFIER_CHARACTER_SET^} (@command{gcc})
6838 Normally GNAT recognizes the Latin-1 character set in source program
6839 identifiers, as described in the Ada Reference Manual.
6841 GNAT to recognize alternate character sets in identifiers. @var{c} is a
6842 single character ^^or word^ indicating the character set, as follows:
6846 ISO 8859-1 (Latin-1) identifiers
6849 ISO 8859-2 (Latin-2) letters allowed in identifiers
6852 ISO 8859-3 (Latin-3) letters allowed in identifiers
6855 ISO 8859-4 (Latin-4) letters allowed in identifiers
6858 ISO 8859-5 (Cyrillic) letters allowed in identifiers
6861 ISO 8859-15 (Latin-9) letters allowed in identifiers
6864 IBM PC letters (code page 437) allowed in identifiers
6867 IBM PC letters (code page 850) allowed in identifiers
6869 @item ^f^FULL_UPPER^
6870 Full upper-half codes allowed in identifiers
6873 No upper-half codes allowed in identifiers
6876 Wide-character codes (that is, codes greater than 255)
6877 allowed in identifiers
6880 @xref{Foreign Language Representation}, for full details on the
6881 implementation of these character sets.
6883 @item ^-gnatW^/WIDE_CHARACTER_ENCODING=^@var{e}
6884 @cindex @option{^-gnatW^/WIDE_CHARACTER_ENCODING^} (@command{gcc})
6885 Specify the method of encoding for wide characters.
6886 @var{e} is one of the following:
6891 Hex encoding (brackets coding also recognized)
6894 Upper half encoding (brackets encoding also recognized)
6897 Shift/JIS encoding (brackets encoding also recognized)
6900 EUC encoding (brackets encoding also recognized)
6903 UTF-8 encoding (brackets encoding also recognized)
6906 Brackets encoding only (default value)
6908 For full details on these encoding
6909 methods see @ref{Wide Character Encodings}.
6910 Note that brackets coding is always accepted, even if one of the other
6911 options is specified, so for example @option{-gnatW8} specifies that both
6912 brackets and UTF-8 encodings will be recognized. The units that are
6913 with'ed directly or indirectly will be scanned using the specified
6914 representation scheme, and so if one of the non-brackets scheme is
6915 used, it must be used consistently throughout the program. However,
6916 since brackets encoding is always recognized, it may be conveniently
6917 used in standard libraries, allowing these libraries to be used with
6918 any of the available coding schemes.
6921 If no @option{-gnatW?} parameter is present, then the default
6922 representation is normally Brackets encoding only. However, if the
6923 first three characters of the file are 16#EF# 16#BB# 16#BF# (the standard
6924 byte order mark or BOM for UTF-8), then these three characters are
6925 skipped and the default representation for the file is set to UTF-8.
6927 Note that the wide character representation that is specified (explicitly
6928 or by default) for the main program also acts as the default encoding used
6929 for Wide_Text_IO files if not specifically overridden by a WCEM form
6933 @node File Naming Control
6934 @subsection File Naming Control
6937 @item ^-gnatk^/FILE_NAME_MAX_LENGTH=^@var{n}
6938 @cindex @option{-gnatk} (@command{gcc})
6939 Activates file name ``krunching''. @var{n}, a decimal integer in the range
6940 1-999, indicates the maximum allowable length of a file name (not
6941 including the @file{.ads} or @file{.adb} extension). The default is not
6942 to enable file name krunching.
6944 For the source file naming rules, @xref{File Naming Rules}.
6947 @node Subprogram Inlining Control
6948 @subsection Subprogram Inlining Control
6953 @cindex @option{-gnatn} (@command{gcc})
6955 The @code{n} here is intended to suggest the first syllable of the
6958 GNAT recognizes and processes @code{Inline} pragmas. However, for the
6959 inlining to actually occur, optimization must be enabled. To enable
6960 inlining of subprograms specified by pragma @code{Inline},
6961 you must also specify this switch.
6962 In the absence of this switch, GNAT does not attempt
6963 inlining and does not need to access the bodies of
6964 subprograms for which @code{pragma Inline} is specified if they are not
6965 in the current unit.
6967 If you specify this switch the compiler will access these bodies,
6968 creating an extra source dependency for the resulting object file, and
6969 where possible, the call will be inlined.
6970 For further details on when inlining is possible
6971 see @ref{Inlining of Subprograms}.
6974 @cindex @option{-gnatN} (@command{gcc})
6975 This switch activates front-end inlining which also
6976 generates additional dependencies.
6978 When using a gcc-based back end (in practice this means using any version
6979 of GNAT other than the JGNAT, .NET or GNAAMP versions), then the use of
6980 @option{-gnatN} is deprecated, and the use of @option{-gnatn} is preferred.
6981 Historically front end inlining was more extensive than the gcc back end
6982 inlining, but that is no longer the case.
6985 @node Auxiliary Output Control
6986 @subsection Auxiliary Output Control
6990 @cindex @option{-gnatt} (@command{gcc})
6991 @cindex Writing internal trees
6992 @cindex Internal trees, writing to file
6993 Causes GNAT to write the internal tree for a unit to a file (with the
6994 extension @file{.adt}.
6995 This not normally required, but is used by separate analysis tools.
6997 these tools do the necessary compilations automatically, so you should
6998 not have to specify this switch in normal operation.
7001 @cindex @option{-gnatu} (@command{gcc})
7002 Print a list of units required by this compilation on @file{stdout}.
7003 The listing includes all units on which the unit being compiled depends
7004 either directly or indirectly.
7007 @item -pass-exit-codes
7008 @cindex @option{-pass-exit-codes} (@command{gcc})
7009 If this switch is not used, the exit code returned by @command{gcc} when
7010 compiling multiple files indicates whether all source files have
7011 been successfully used to generate object files or not.
7013 When @option{-pass-exit-codes} is used, @command{gcc} exits with an extended
7014 exit status and allows an integrated development environment to better
7015 react to a compilation failure. Those exit status are:
7019 There was an error in at least one source file.
7021 At least one source file did not generate an object file.
7023 The compiler died unexpectedly (internal error for example).
7025 An object file has been generated for every source file.
7030 @node Debugging Control
7031 @subsection Debugging Control
7035 @cindex Debugging options
7038 @cindex @option{-gnatd} (@command{gcc})
7039 Activate internal debugging switches. @var{x} is a letter or digit, or
7040 string of letters or digits, which specifies the type of debugging
7041 outputs desired. Normally these are used only for internal development
7042 or system debugging purposes. You can find full documentation for these
7043 switches in the body of the @code{Debug} unit in the compiler source
7044 file @file{debug.adb}.
7048 @cindex @option{-gnatG} (@command{gcc})
7049 This switch causes the compiler to generate auxiliary output containing
7050 a pseudo-source listing of the generated expanded code. Like most Ada
7051 compilers, GNAT works by first transforming the high level Ada code into
7052 lower level constructs. For example, tasking operations are transformed
7053 into calls to the tasking run-time routines. A unique capability of GNAT
7054 is to list this expanded code in a form very close to normal Ada source.
7055 This is very useful in understanding the implications of various Ada
7056 usage on the efficiency of the generated code. There are many cases in
7057 Ada (e.g.@: the use of controlled types), where simple Ada statements can
7058 generate a lot of run-time code. By using @option{-gnatG} you can identify
7059 these cases, and consider whether it may be desirable to modify the coding
7060 approach to improve efficiency.
7062 The optional parameter @code{nn} if present after -gnatG specifies an
7063 alternative maximum line length that overrides the normal default of 72.
7064 This value is in the range 40-999999, values less than 40 being silently
7065 reset to 40. The equal sign is optional.
7067 The format of the output is very similar to standard Ada source, and is
7068 easily understood by an Ada programmer. The following special syntactic
7069 additions correspond to low level features used in the generated code that
7070 do not have any exact analogies in pure Ada source form. The following
7071 is a partial list of these special constructions. See the spec
7072 of package @code{Sprint} in file @file{sprint.ads} for a full list.
7074 If the switch @option{-gnatL} is used in conjunction with
7075 @cindex @option{-gnatL} (@command{gcc})
7076 @option{-gnatG}, then the original source lines are interspersed
7077 in the expanded source (as comment lines with the original line number).
7080 @item new @var{xxx} @r{[}storage_pool = @var{yyy}@r{]}
7081 Shows the storage pool being used for an allocator.
7083 @item at end @var{procedure-name};
7084 Shows the finalization (cleanup) procedure for a scope.
7086 @item (if @var{expr} then @var{expr} else @var{expr})
7087 Conditional expression equivalent to the @code{x?y:z} construction in C.
7089 @item @var{target}^^^(@var{source})
7090 A conversion with floating-point truncation instead of rounding.
7092 @item @var{target}?(@var{source})
7093 A conversion that bypasses normal Ada semantic checking. In particular
7094 enumeration types and fixed-point types are treated simply as integers.
7096 @item @var{target}?^^^(@var{source})
7097 Combines the above two cases.
7099 @item @var{x} #/ @var{y}
7100 @itemx @var{x} #mod @var{y}
7101 @itemx @var{x} #* @var{y}
7102 @itemx @var{x} #rem @var{y}
7103 A division or multiplication of fixed-point values which are treated as
7104 integers without any kind of scaling.
7106 @item free @var{expr} @r{[}storage_pool = @var{xxx}@r{]}
7107 Shows the storage pool associated with a @code{free} statement.
7109 @item [subtype or type declaration]
7110 Used to list an equivalent declaration for an internally generated
7111 type that is referenced elsewhere in the listing.
7113 @item freeze @var{type-name} @ovar{actions}
7114 Shows the point at which @var{type-name} is frozen, with possible
7115 associated actions to be performed at the freeze point.
7117 @item reference @var{itype}
7118 Reference (and hence definition) to internal type @var{itype}.
7120 @item @var{function-name}! (@var{arg}, @var{arg}, @var{arg})
7121 Intrinsic function call.
7123 @item @var{label-name} : label
7124 Declaration of label @var{labelname}.
7126 @item #$ @var{subprogram-name}
7127 An implicit call to a run-time support routine
7128 (to meet the requirement of H.3.1(9) in a
7131 @item @var{expr} && @var{expr} && @var{expr} @dots{} && @var{expr}
7132 A multiple concatenation (same effect as @var{expr} & @var{expr} &
7133 @var{expr}, but handled more efficiently).
7135 @item [constraint_error]
7136 Raise the @code{Constraint_Error} exception.
7138 @item @var{expression}'reference
7139 A pointer to the result of evaluating @var{expression}.
7141 @item @var{target-type}!(@var{source-expression})
7142 An unchecked conversion of @var{source-expression} to @var{target-type}.
7144 @item [@var{numerator}/@var{denominator}]
7145 Used to represent internal real literals (that) have no exact
7146 representation in base 2-16 (for example, the result of compile time
7147 evaluation of the expression 1.0/27.0).
7151 @cindex @option{-gnatD} (@command{gcc})
7152 When used in conjunction with @option{-gnatG}, this switch causes
7153 the expanded source, as described above for
7154 @option{-gnatG} to be written to files with names
7155 @file{^xxx.dg^XXX_DG^}, where @file{xxx} is the normal file name,
7156 instead of to the standard output file. For
7157 example, if the source file name is @file{hello.adb}, then a file
7158 @file{^hello.adb.dg^HELLO.ADB_DG^} will be written. The debugging
7159 information generated by the @command{gcc} @option{^-g^/DEBUG^} switch
7160 will refer to the generated @file{^xxx.dg^XXX_DG^} file. This allows
7161 you to do source level debugging using the generated code which is
7162 sometimes useful for complex code, for example to find out exactly
7163 which part of a complex construction raised an exception. This switch
7164 also suppress generation of cross-reference information (see
7165 @option{-gnatx}) since otherwise the cross-reference information
7166 would refer to the @file{^.dg^.DG^} file, which would cause
7167 confusion since this is not the original source file.
7169 Note that @option{-gnatD} actually implies @option{-gnatG}
7170 automatically, so it is not necessary to give both options.
7171 In other words @option{-gnatD} is equivalent to @option{-gnatDG}).
7173 If the switch @option{-gnatL} is used in conjunction with
7174 @cindex @option{-gnatL} (@command{gcc})
7175 @option{-gnatDG}, then the original source lines are interspersed
7176 in the expanded source (as comment lines with the original line number).
7178 The optional parameter @code{nn} if present after -gnatD specifies an
7179 alternative maximum line length that overrides the normal default of 72.
7180 This value is in the range 40-999999, values less than 40 being silently
7181 reset to 40. The equal sign is optional.
7184 @cindex @option{-gnatr} (@command{gcc})
7185 @cindex pragma Restrictions
7186 This switch causes pragma Restrictions to be treated as Restriction_Warnings
7187 so that violation of restrictions causes warnings rather than illegalities.
7188 This is useful during the development process when new restrictions are added
7189 or investigated. The switch also causes pragma Profile to be treated as
7190 Profile_Warnings, and pragma Restricted_Run_Time and pragma Ravenscar set
7191 restriction warnings rather than restrictions.
7194 @item -gnatR@r{[}0@r{|}1@r{|}2@r{|}3@r{[}s@r{]]}
7195 @cindex @option{-gnatR} (@command{gcc})
7196 This switch controls output from the compiler of a listing showing
7197 representation information for declared types and objects. For
7198 @option{-gnatR0}, no information is output (equivalent to omitting
7199 the @option{-gnatR} switch). For @option{-gnatR1} (which is the default,
7200 so @option{-gnatR} with no parameter has the same effect), size and alignment
7201 information is listed for declared array and record types. For
7202 @option{-gnatR2}, size and alignment information is listed for all
7203 declared types and objects. Finally @option{-gnatR3} includes symbolic
7204 expressions for values that are computed at run time for
7205 variant records. These symbolic expressions have a mostly obvious
7206 format with #n being used to represent the value of the n'th
7207 discriminant. See source files @file{repinfo.ads/adb} in the
7208 @code{GNAT} sources for full details on the format of @option{-gnatR3}
7209 output. If the switch is followed by an s (e.g.@: @option{-gnatR2s}), then
7210 the output is to a file with the name @file{^file.rep^file_REP^} where
7211 file is the name of the corresponding source file.
7214 @item /REPRESENTATION_INFO
7215 @cindex @option{/REPRESENTATION_INFO} (@command{gcc})
7216 This qualifier controls output from the compiler of a listing showing
7217 representation information for declared types and objects. For
7218 @option{/REPRESENTATION_INFO=NONE}, no information is output
7219 (equivalent to omitting the @option{/REPRESENTATION_INFO} qualifier).
7220 @option{/REPRESENTATION_INFO} without option is equivalent to
7221 @option{/REPRESENTATION_INFO=ARRAYS}.
7222 For @option{/REPRESENTATION_INFO=ARRAYS}, size and alignment
7223 information is listed for declared array and record types. For
7224 @option{/REPRESENTATION_INFO=OBJECTS}, size and alignment information
7225 is listed for all expression information for values that are computed
7226 at run time for variant records. These symbolic expressions have a mostly
7227 obvious format with #n being used to represent the value of the n'th
7228 discriminant. See source files @file{REPINFO.ADS/ADB} in the
7229 @code{GNAT} sources for full details on the format of
7230 @option{/REPRESENTATION_INFO=SYMBOLIC} output.
7231 If _FILE is added at the end of an option
7232 (e.g.@: @option{/REPRESENTATION_INFO=ARRAYS_FILE}),
7233 then the output is to a file with the name @file{file_REP} where
7234 file is the name of the corresponding source file.
7236 Note that it is possible for record components to have zero size. In
7237 this case, the component clause uses an obvious extension of permitted
7238 Ada syntax, for example @code{at 0 range 0 .. -1}.
7240 Representation information requires that code be generated (since it is the
7241 code generator that lays out complex data structures). If an attempt is made
7242 to output representation information when no code is generated, for example
7243 when a subunit is compiled on its own, then no information can be generated
7244 and the compiler outputs a message to this effect.
7247 @cindex @option{-gnatS} (@command{gcc})
7248 The use of the switch @option{-gnatS} for an
7249 Ada compilation will cause the compiler to output a
7250 representation of package Standard in a form very
7251 close to standard Ada. It is not quite possible to
7252 do this entirely in standard Ada (since new
7253 numeric base types cannot be created in standard
7254 Ada), but the output is easily
7255 readable to any Ada programmer, and is useful to
7256 determine the characteristics of target dependent
7257 types in package Standard.
7260 @cindex @option{-gnatx} (@command{gcc})
7261 Normally the compiler generates full cross-referencing information in
7262 the @file{ALI} file. This information is used by a number of tools,
7263 including @code{gnatfind} and @code{gnatxref}. The @option{-gnatx} switch
7264 suppresses this information. This saves some space and may slightly
7265 speed up compilation, but means that these tools cannot be used.
7268 @node Exception Handling Control
7269 @subsection Exception Handling Control
7272 GNAT uses two methods for handling exceptions at run-time. The
7273 @code{setjmp/longjmp} method saves the context when entering
7274 a frame with an exception handler. Then when an exception is
7275 raised, the context can be restored immediately, without the
7276 need for tracing stack frames. This method provides very fast
7277 exception propagation, but introduces significant overhead for
7278 the use of exception handlers, even if no exception is raised.
7280 The other approach is called ``zero cost'' exception handling.
7281 With this method, the compiler builds static tables to describe
7282 the exception ranges. No dynamic code is required when entering
7283 a frame containing an exception handler. When an exception is
7284 raised, the tables are used to control a back trace of the
7285 subprogram invocation stack to locate the required exception
7286 handler. This method has considerably poorer performance for
7287 the propagation of exceptions, but there is no overhead for
7288 exception handlers if no exception is raised. Note that in this
7289 mode and in the context of mixed Ada and C/C++ programming,
7290 to propagate an exception through a C/C++ code, the C/C++ code
7291 must be compiled with the @option{-funwind-tables} GCC's
7294 The following switches may be used to control which of the
7295 two exception handling methods is used.
7301 @cindex @option{--RTS=sjlj} (@command{gnatmake})
7302 This switch causes the setjmp/longjmp run-time (when available) to be used
7303 for exception handling. If the default
7304 mechanism for the target is zero cost exceptions, then
7305 this switch can be used to modify this default, and must be
7306 used for all units in the partition.
7307 This option is rarely used. One case in which it may be
7308 advantageous is if you have an application where exception
7309 raising is common and the overall performance of the
7310 application is improved by favoring exception propagation.
7313 @cindex @option{--RTS=zcx} (@command{gnatmake})
7314 @cindex Zero Cost Exceptions
7315 This switch causes the zero cost approach to be used
7316 for exception handling. If this is the default mechanism for the
7317 target (see below), then this switch is unneeded. If the default
7318 mechanism for the target is setjmp/longjmp exceptions, then
7319 this switch can be used to modify this default, and must be
7320 used for all units in the partition.
7321 This option can only be used if the zero cost approach
7322 is available for the target in use, otherwise it will generate an error.
7326 The same option @option{--RTS} must be used both for @command{gcc}
7327 and @command{gnatbind}. Passing this option to @command{gnatmake}
7328 (@pxref{Switches for gnatmake}) will ensure the required consistency
7329 through the compilation and binding steps.
7331 @node Units to Sources Mapping Files
7332 @subsection Units to Sources Mapping Files
7336 @item -gnatem^^=^@var{path}
7337 @cindex @option{-gnatem} (@command{gcc})
7338 A mapping file is a way to communicate to the compiler two mappings:
7339 from unit names to file names (without any directory information) and from
7340 file names to path names (with full directory information). These mappings
7341 are used by the compiler to short-circuit the path search.
7343 The use of mapping files is not required for correct operation of the
7344 compiler, but mapping files can improve efficiency, particularly when
7345 sources are read over a slow network connection. In normal operation,
7346 you need not be concerned with the format or use of mapping files,
7347 and the @option{-gnatem} switch is not a switch that you would use
7348 explicitly. it is intended only for use by automatic tools such as
7349 @command{gnatmake} running under the project file facility. The
7350 description here of the format of mapping files is provided
7351 for completeness and for possible use by other tools.
7353 A mapping file is a sequence of sets of three lines. In each set,
7354 the first line is the unit name, in lower case, with ``@code{%s}''
7356 specs and ``@code{%b}'' appended for bodies; the second line is the
7357 file name; and the third line is the path name.
7363 /gnat/project1/sources/main.2.ada
7366 When the switch @option{-gnatem} is specified, the compiler will create
7367 in memory the two mappings from the specified file. If there is any problem
7368 (nonexistent file, truncated file or duplicate entries), no mapping will
7371 Several @option{-gnatem} switches may be specified; however, only the last
7372 one on the command line will be taken into account.
7374 When using a project file, @command{gnatmake} create a temporary mapping file
7375 and communicates it to the compiler using this switch.
7379 @node Integrated Preprocessing
7380 @subsection Integrated Preprocessing
7383 GNAT sources may be preprocessed immediately before compilation.
7384 In this case, the actual
7385 text of the source is not the text of the source file, but is derived from it
7386 through a process called preprocessing. Integrated preprocessing is specified
7387 through switches @option{-gnatep} and/or @option{-gnateD}. @option{-gnatep}
7388 indicates, through a text file, the preprocessing data to be used.
7389 @option{-gnateD} specifies or modifies the values of preprocessing symbol.
7392 Note that when integrated preprocessing is used, the output from the
7393 preprocessor is not written to any external file. Instead it is passed
7394 internally to the compiler. If you need to preserve the result of
7395 preprocessing in a file, then you should use @command{gnatprep}
7396 to perform the desired preprocessing in stand-alone mode.
7399 It is recommended that @command{gnatmake} switch ^-s^/SWITCH_CHECK^ should be
7400 used when Integrated Preprocessing is used. The reason is that preprocessing
7401 with another Preprocessing Data file without changing the sources will
7402 not trigger recompilation without this switch.
7405 Note that @command{gnatmake} switch ^-m^/MINIMAL_RECOMPILATION^ will almost
7406 always trigger recompilation for sources that are preprocessed,
7407 because @command{gnatmake} cannot compute the checksum of the source after
7411 The actual preprocessing function is described in details in section
7412 @ref{Preprocessing Using gnatprep}. This section only describes how integrated
7413 preprocessing is triggered and parameterized.
7417 @item -gnatep=@var{file}
7418 @cindex @option{-gnatep} (@command{gcc})
7419 This switch indicates to the compiler the file name (without directory
7420 information) of the preprocessor data file to use. The preprocessor data file
7421 should be found in the source directories.
7424 A preprocessing data file is a text file with significant lines indicating
7425 how should be preprocessed either a specific source or all sources not
7426 mentioned in other lines. A significant line is a nonempty, non-comment line.
7427 Comments are similar to Ada comments.
7430 Each significant line starts with either a literal string or the character '*'.
7431 A literal string is the file name (without directory information) of the source
7432 to preprocess. A character '*' indicates the preprocessing for all the sources
7433 that are not specified explicitly on other lines (order of the lines is not
7434 significant). It is an error to have two lines with the same file name or two
7435 lines starting with the character '*'.
7438 After the file name or the character '*', another optional literal string
7439 indicating the file name of the definition file to be used for preprocessing
7440 (@pxref{Form of Definitions File}). The definition files are found by the
7441 compiler in one of the source directories. In some cases, when compiling
7442 a source in a directory other than the current directory, if the definition
7443 file is in the current directory, it may be necessary to add the current
7444 directory as a source directory through switch ^-I.^/SEARCH=[]^, otherwise
7445 the compiler would not find the definition file.
7448 Then, optionally, ^switches^switches^ similar to those of @code{gnatprep} may
7449 be found. Those ^switches^switches^ are:
7454 Causes both preprocessor lines and the lines deleted by
7455 preprocessing to be replaced by blank lines, preserving the line number.
7456 This ^switch^switch^ is always implied; however, if specified after @option{-c}
7457 it cancels the effect of @option{-c}.
7460 Causes both preprocessor lines and the lines deleted
7461 by preprocessing to be retained as comments marked
7462 with the special string ``@code{--! }''.
7464 @item -Dsymbol=value
7465 Define or redefine a symbol, associated with value. A symbol is an Ada
7466 identifier, or an Ada reserved word, with the exception of @code{if},
7467 @code{else}, @code{elsif}, @code{end}, @code{and}, @code{or} and @code{then}.
7468 @code{value} is either a literal string, an Ada identifier or any Ada reserved
7469 word. A symbol declared with this ^switch^switch^ replaces a symbol with the
7470 same name defined in a definition file.
7473 Causes a sorted list of symbol names and values to be
7474 listed on the standard output file.
7477 Causes undefined symbols to be treated as having the value @code{FALSE}
7479 of a preprocessor test. In the absence of this option, an undefined symbol in
7480 a @code{#if} or @code{#elsif} test will be treated as an error.
7485 Examples of valid lines in a preprocessor data file:
7488 "toto.adb" "prep.def" -u
7489 -- preprocess "toto.adb", using definition file "prep.def",
7490 -- undefined symbol are False.
7493 -- preprocess all other sources without a definition file;
7494 -- suppressed lined are commented; symbol VERSION has the value V101.
7496 "titi.adb" "prep2.def" -s
7497 -- preprocess "titi.adb", using definition file "prep2.def";
7498 -- list all symbols with their values.
7501 @item ^-gnateD^/DATA_PREPROCESSING=^symbol@r{[}=value@r{]}
7502 @cindex @option{-gnateD} (@command{gcc})
7503 Define or redefine a preprocessing symbol, associated with value. If no value
7504 is given on the command line, then the value of the symbol is @code{True}.
7505 A symbol is an identifier, following normal Ada (case-insensitive)
7506 rules for its syntax, and value is any sequence (including an empty sequence)
7507 of characters from the set (letters, digits, period, underline).
7508 Ada reserved words may be used as symbols, with the exceptions of @code{if},
7509 @code{else}, @code{elsif}, @code{end}, @code{and}, @code{or} and @code{then}.
7512 A symbol declared with this ^switch^switch^ on the command line replaces a
7513 symbol with the same name either in a definition file or specified with a
7514 ^switch^switch^ -D in the preprocessor data file.
7517 This switch is similar to switch @option{^-D^/ASSOCIATE^} of @code{gnatprep}.
7520 When integrated preprocessing is performed and the preprocessor modifies
7521 the source text, write the result of this preprocessing into a file
7522 <source>^.prep^_prep^.
7526 @node Code Generation Control
7527 @subsection Code Generation Control
7531 The GCC technology provides a wide range of target dependent
7532 @option{-m} switches for controlling
7533 details of code generation with respect to different versions of
7534 architectures. This includes variations in instruction sets (e.g.@:
7535 different members of the power pc family), and different requirements
7536 for optimal arrangement of instructions (e.g.@: different members of
7537 the x86 family). The list of available @option{-m} switches may be
7538 found in the GCC documentation.
7540 Use of these @option{-m} switches may in some cases result in improved
7543 The GNAT Pro technology is tested and qualified without any
7544 @option{-m} switches,
7545 so generally the most reliable approach is to avoid the use of these
7546 switches. However, we generally expect most of these switches to work
7547 successfully with GNAT Pro, and many customers have reported successful
7548 use of these options.
7550 Our general advice is to avoid the use of @option{-m} switches unless
7551 special needs lead to requirements in this area. In particular,
7552 there is no point in using @option{-m} switches to improve performance
7553 unless you actually see a performance improvement.
7557 @subsection Return Codes
7558 @cindex Return Codes
7559 @cindex @option{/RETURN_CODES=VMS}
7562 On VMS, GNAT compiled programs return POSIX-style codes by default,
7563 e.g.@: @option{/RETURN_CODES=POSIX}.
7565 To enable VMS style return codes, use GNAT BIND and LINK with the option
7566 @option{/RETURN_CODES=VMS}. For example:
7569 GNAT BIND MYMAIN.ALI /RETURN_CODES=VMS
7570 GNAT LINK MYMAIN.ALI /RETURN_CODES=VMS
7574 Programs built with /RETURN_CODES=VMS are suitable to be called in
7575 VMS DCL scripts. Programs compiled with the default /RETURN_CODES=POSIX
7576 are suitable for spawning with appropriate GNAT RTL routines.
7580 @node Search Paths and the Run-Time Library (RTL)
7581 @section Search Paths and the Run-Time Library (RTL)
7584 With the GNAT source-based library system, the compiler must be able to
7585 find source files for units that are needed by the unit being compiled.
7586 Search paths are used to guide this process.
7588 The compiler compiles one source file whose name must be given
7589 explicitly on the command line. In other words, no searching is done
7590 for this file. To find all other source files that are needed (the most
7591 common being the specs of units), the compiler examines the following
7592 directories, in the following order:
7596 The directory containing the source file of the main unit being compiled
7597 (the file name on the command line).
7600 Each directory named by an @option{^-I^/SOURCE_SEARCH^} switch given on the
7601 @command{gcc} command line, in the order given.
7604 @findex ADA_PRJ_INCLUDE_FILE
7605 Each of the directories listed in the text file whose name is given
7606 by the @env{ADA_PRJ_INCLUDE_FILE} ^environment variable^logical name^.
7609 @env{ADA_PRJ_INCLUDE_FILE} is normally set by gnatmake or by the ^gnat^GNAT^
7610 driver when project files are used. It should not normally be set
7614 @findex ADA_INCLUDE_PATH
7615 Each of the directories listed in the value of the
7616 @env{ADA_INCLUDE_PATH} ^environment variable^logical name^.
7618 Construct this value
7619 exactly as the @env{PATH} environment variable: a list of directory
7620 names separated by colons (semicolons when working with the NT version).
7623 Normally, define this value as a logical name containing a comma separated
7624 list of directory names.
7626 This variable can also be defined by means of an environment string
7627 (an argument to the HP C exec* set of functions).
7631 DEFINE ANOTHER_PATH FOO:[BAG]
7632 DEFINE ADA_INCLUDE_PATH ANOTHER_PATH,FOO:[BAM],FOO:[BAR]
7635 By default, the path includes GNU:[LIB.OPENVMS7_x.2_8_x.DECLIB]
7636 first, followed by the standard Ada
7637 libraries in GNU:[LIB.OPENVMS7_x.2_8_x.ADAINCLUDE].
7638 If this is not redefined, the user will obtain the HP Ada 83 IO packages
7639 (Text_IO, Sequential_IO, etc)
7640 instead of the standard Ada packages. Thus, in order to get the standard Ada
7641 packages by default, ADA_INCLUDE_PATH must be redefined.
7645 The content of the @file{ada_source_path} file which is part of the GNAT
7646 installation tree and is used to store standard libraries such as the
7647 GNAT Run Time Library (RTL) source files.
7649 @ref{Installing a library}
7654 Specifying the switch @option{^-I-^/NOCURRENT_DIRECTORY^}
7655 inhibits the use of the directory
7656 containing the source file named in the command line. You can still
7657 have this directory on your search path, but in this case it must be
7658 explicitly requested with a @option{^-I^/SOURCE_SEARCH^} switch.
7660 Specifying the switch @option{-nostdinc}
7661 inhibits the search of the default location for the GNAT Run Time
7662 Library (RTL) source files.
7664 The compiler outputs its object files and ALI files in the current
7667 Caution: The object file can be redirected with the @option{-o} switch;
7668 however, @command{gcc} and @code{gnat1} have not been coordinated on this
7669 so the @file{ALI} file will not go to the right place. Therefore, you should
7670 avoid using the @option{-o} switch.
7674 The packages @code{Ada}, @code{System}, and @code{Interfaces} and their
7675 children make up the GNAT RTL, together with the simple @code{System.IO}
7676 package used in the @code{"Hello World"} example. The sources for these units
7677 are needed by the compiler and are kept together in one directory. Not
7678 all of the bodies are needed, but all of the sources are kept together
7679 anyway. In a normal installation, you need not specify these directory
7680 names when compiling or binding. Either the environment variables or
7681 the built-in defaults cause these files to be found.
7683 In addition to the language-defined hierarchies (@code{System}, @code{Ada} and
7684 @code{Interfaces}), the GNAT distribution provides a fourth hierarchy,
7685 consisting of child units of @code{GNAT}. This is a collection of generally
7686 useful types, subprograms, etc. @xref{Top, GNAT Reference Manual, About
7687 This Guid, gnat_rm, GNAT Reference Manual}, for further details.
7689 Besides simplifying access to the RTL, a major use of search paths is
7690 in compiling sources from multiple directories. This can make
7691 development environments much more flexible.
7693 @node Order of Compilation Issues
7694 @section Order of Compilation Issues
7697 If, in our earlier example, there was a spec for the @code{hello}
7698 procedure, it would be contained in the file @file{hello.ads}; yet this
7699 file would not have to be explicitly compiled. This is the result of the
7700 model we chose to implement library management. Some of the consequences
7701 of this model are as follows:
7705 There is no point in compiling specs (except for package
7706 specs with no bodies) because these are compiled as needed by clients. If
7707 you attempt a useless compilation, you will receive an error message.
7708 It is also useless to compile subunits because they are compiled as needed
7712 There are no order of compilation requirements: performing a
7713 compilation never obsoletes anything. The only way you can obsolete
7714 something and require recompilations is to modify one of the
7715 source files on which it depends.
7718 There is no library as such, apart from the ALI files
7719 (@pxref{The Ada Library Information Files}, for information on the format
7720 of these files). For now we find it convenient to create separate ALI files,
7721 but eventually the information therein may be incorporated into the object
7725 When you compile a unit, the source files for the specs of all units
7726 that it @code{with}'s, all its subunits, and the bodies of any generics it
7727 instantiates must be available (reachable by the search-paths mechanism
7728 described above), or you will receive a fatal error message.
7735 The following are some typical Ada compilation command line examples:
7738 @item $ gcc -c xyz.adb
7739 Compile body in file @file{xyz.adb} with all default options.
7742 @item $ gcc -c -O2 -gnata xyz-def.adb
7745 @item $ GNAT COMPILE /OPTIMIZE=ALL -gnata xyz-def.adb
7748 Compile the child unit package in file @file{xyz-def.adb} with extensive
7749 optimizations, and pragma @code{Assert}/@code{Debug} statements
7752 @item $ gcc -c -gnatc abc-def.adb
7753 Compile the subunit in file @file{abc-def.adb} in semantic-checking-only
7757 @node Binding Using gnatbind
7758 @chapter Binding Using @code{gnatbind}
7762 * Running gnatbind::
7763 * Switches for gnatbind::
7764 * Command-Line Access::
7765 * Search Paths for gnatbind::
7766 * Examples of gnatbind Usage::
7770 This chapter describes the GNAT binder, @code{gnatbind}, which is used
7771 to bind compiled GNAT objects.
7773 Note: to invoke @code{gnatbind} with a project file, use the @code{gnat}
7774 driver (see @ref{The GNAT Driver and Project Files}).
7776 The @code{gnatbind} program performs four separate functions:
7780 Checks that a program is consistent, in accordance with the rules in
7781 Chapter 10 of the Ada Reference Manual. In particular, error
7782 messages are generated if a program uses inconsistent versions of a
7786 Checks that an acceptable order of elaboration exists for the program
7787 and issues an error message if it cannot find an order of elaboration
7788 that satisfies the rules in Chapter 10 of the Ada Language Manual.
7791 Generates a main program incorporating the given elaboration order.
7792 This program is a small Ada package (body and spec) that
7793 must be subsequently compiled
7794 using the GNAT compiler. The necessary compilation step is usually
7795 performed automatically by @command{gnatlink}. The two most important
7796 functions of this program
7797 are to call the elaboration routines of units in an appropriate order
7798 and to call the main program.
7801 Determines the set of object files required by the given main program.
7802 This information is output in the forms of comments in the generated program,
7803 to be read by the @command{gnatlink} utility used to link the Ada application.
7806 @node Running gnatbind
7807 @section Running @code{gnatbind}
7810 The form of the @code{gnatbind} command is
7813 $ gnatbind @ovar{switches} @var{mainprog}@r{[}.ali@r{]} @ovar{switches}
7817 where @file{@var{mainprog}.adb} is the Ada file containing the main program
7818 unit body. If no switches are specified, @code{gnatbind} constructs an Ada
7819 package in two files whose names are
7820 @file{b~@var{mainprog}.ads}, and @file{b~@var{mainprog}.adb}.
7821 For example, if given the
7822 parameter @file{hello.ali}, for a main program contained in file
7823 @file{hello.adb}, the binder output files would be @file{b~hello.ads}
7824 and @file{b~hello.adb}.
7826 When doing consistency checking, the binder takes into consideration
7827 any source files it can locate. For example, if the binder determines
7828 that the given main program requires the package @code{Pack}, whose
7830 file is @file{pack.ali} and whose corresponding source spec file is
7831 @file{pack.ads}, it attempts to locate the source file @file{pack.ads}
7832 (using the same search path conventions as previously described for the
7833 @command{gcc} command). If it can locate this source file, it checks that
7835 or source checksums of the source and its references to in @file{ALI} files
7836 match. In other words, any @file{ALI} files that mentions this spec must have
7837 resulted from compiling this version of the source file (or in the case
7838 where the source checksums match, a version close enough that the
7839 difference does not matter).
7841 @cindex Source files, use by binder
7842 The effect of this consistency checking, which includes source files, is
7843 that the binder ensures that the program is consistent with the latest
7844 version of the source files that can be located at bind time. Editing a
7845 source file without compiling files that depend on the source file cause
7846 error messages to be generated by the binder.
7848 For example, suppose you have a main program @file{hello.adb} and a
7849 package @code{P}, from file @file{p.ads} and you perform the following
7854 Enter @code{gcc -c hello.adb} to compile the main program.
7857 Enter @code{gcc -c p.ads} to compile package @code{P}.
7860 Edit file @file{p.ads}.
7863 Enter @code{gnatbind hello}.
7867 At this point, the file @file{p.ali} contains an out-of-date time stamp
7868 because the file @file{p.ads} has been edited. The attempt at binding
7869 fails, and the binder generates the following error messages:
7872 error: "hello.adb" must be recompiled ("p.ads" has been modified)
7873 error: "p.ads" has been modified and must be recompiled
7877 Now both files must be recompiled as indicated, and then the bind can
7878 succeed, generating a main program. You need not normally be concerned
7879 with the contents of this file, but for reference purposes a sample
7880 binder output file is given in @ref{Example of Binder Output File}.
7882 In most normal usage, the default mode of @command{gnatbind} which is to
7883 generate the main package in Ada, as described in the previous section.
7884 In particular, this means that any Ada programmer can read and understand
7885 the generated main program. It can also be debugged just like any other
7886 Ada code provided the @option{^-g^/DEBUG^} switch is used for
7887 @command{gnatbind} and @command{gnatlink}.
7889 However for some purposes it may be convenient to generate the main
7890 program in C rather than Ada. This may for example be helpful when you
7891 are generating a mixed language program with the main program in C. The
7892 GNAT compiler itself is an example.
7893 The use of the @option{^-C^/BIND_FILE=C^} switch
7894 for both @code{gnatbind} and @command{gnatlink} will cause the program to
7895 be generated in C (and compiled using the gnu C compiler).
7897 @node Switches for gnatbind
7898 @section Switches for @command{gnatbind}
7901 The following switches are available with @code{gnatbind}; details will
7902 be presented in subsequent sections.
7905 * Consistency-Checking Modes::
7906 * Binder Error Message Control::
7907 * Elaboration Control::
7909 * Binding with Non-Ada Main Programs::
7910 * Binding Programs with No Main Subprogram::
7917 @cindex @option{--version} @command{gnatbind}
7918 Display Copyright and version, then exit disregarding all other options.
7921 @cindex @option{--help} @command{gnatbind}
7922 If @option{--version} was not used, display usage, then exit disregarding
7926 @cindex @option{-a} @command{gnatbind}
7927 Indicates that, if supported by the platform, the adainit procedure should
7928 be treated as an initialisation routine by the linker (a constructor). This
7929 is intended to be used by the Project Manager to automatically initialize
7930 shared Stand-Alone Libraries.
7932 @item ^-aO^/OBJECT_SEARCH^
7933 @cindex @option{^-aO^/OBJECT_SEARCH^} (@command{gnatbind})
7934 Specify directory to be searched for ALI files.
7936 @item ^-aI^/SOURCE_SEARCH^
7937 @cindex @option{^-aI^/SOURCE_SEARCH^} (@command{gnatbind})
7938 Specify directory to be searched for source file.
7940 @item ^-A^/BIND_FILE=ADA^
7941 @cindex @option{^-A^/BIND_FILE=ADA^} (@command{gnatbind})
7942 Generate binder program in Ada (default)
7944 @item ^-b^/REPORT_ERRORS=BRIEF^
7945 @cindex @option{^-b^/REPORT_ERRORS=BRIEF^} (@command{gnatbind})
7946 Generate brief messages to @file{stderr} even if verbose mode set.
7948 @item ^-c^/NOOUTPUT^
7949 @cindex @option{^-c^/NOOUTPUT^} (@command{gnatbind})
7950 Check only, no generation of binder output file.
7952 @item ^-C^/BIND_FILE=C^
7953 @cindex @option{^-C^/BIND_FILE=C^} (@command{gnatbind})
7954 Generate binder program in C
7956 @item ^-d^/DEFAULT_STACK_SIZE=^@var{nn}@r{[}k@r{|}m@r{]}
7957 @cindex @option{^-d^/DEFAULT_STACK_SIZE=^@var{nn}@r{[}k@r{|}m@r{]}} (@command{gnatbind})
7958 This switch can be used to change the default task stack size value
7959 to a specified size @var{nn}, which is expressed in bytes by default, or
7960 in kilobytes when suffixed with @var{k} or in megabytes when suffixed
7962 In the absence of a @samp{@r{[}k@r{|}m@r{]}} suffix, this switch is equivalent,
7963 in effect, to completing all task specs with
7964 @smallexample @c ada
7965 pragma Storage_Size (nn);
7967 When they do not already have such a pragma.
7969 @item ^-D^/DEFAULT_SECONDARY_STACK_SIZE=^@var{nn}@r{[}k@r{|}m@r{]}
7970 @cindex @option{^-D^/DEFAULT_SECONDARY_STACK_SIZE=nnnnn^} (@command{gnatbind})
7971 This switch can be used to change the default secondary stack size value
7972 to a specified size @var{nn}, which is expressed in bytes by default, or
7973 in kilobytes when suffixed with @var{k} or in megabytes when suffixed
7976 The secondary stack is used to deal with functions that return a variable
7977 sized result, for example a function returning an unconstrained
7978 String. There are two ways in which this secondary stack is allocated.
7980 For most targets, the secondary stack is growing on demand and is allocated
7981 as a chain of blocks in the heap. The -D option is not very
7982 relevant. It only give some control over the size of the allocated
7983 blocks (whose size is the minimum of the default secondary stack size value,
7984 and the actual size needed for the current allocation request).
7986 For certain targets, notably VxWorks 653,
7987 the secondary stack is allocated by carving off a fixed ratio chunk of the
7988 primary task stack. The -D option is used to define the
7989 size of the environment task's secondary stack.
7991 @item ^-e^/ELABORATION_DEPENDENCIES^
7992 @cindex @option{^-e^/ELABORATION_DEPENDENCIES^} (@command{gnatbind})
7993 Output complete list of elaboration-order dependencies.
7995 @item ^-E^/STORE_TRACEBACKS^
7996 @cindex @option{^-E^/STORE_TRACEBACKS^} (@command{gnatbind})
7997 Store tracebacks in exception occurrences when the target supports it.
7998 This is the default with the zero cost exception mechanism.
8000 @c The following may get moved to an appendix
8001 This option is currently supported on the following targets:
8002 all x86 ports, Solaris, Windows, HP-UX, AIX, PowerPC VxWorks and Alpha VxWorks.
8004 See also the packages @code{GNAT.Traceback} and
8005 @code{GNAT.Traceback.Symbolic} for more information.
8007 Note that on x86 ports, you must not use @option{-fomit-frame-pointer}
8008 @command{gcc} option.
8011 @item ^-F^/FORCE_ELABS_FLAGS^
8012 @cindex @option{^-F^/FORCE_ELABS_FLAGS^} (@command{gnatbind})
8013 Force the checks of elaboration flags. @command{gnatbind} does not normally
8014 generate checks of elaboration flags for the main executable, except when
8015 a Stand-Alone Library is used. However, there are cases when this cannot be
8016 detected by gnatbind. An example is importing an interface of a Stand-Alone
8017 Library through a pragma Import and only specifying through a linker switch
8018 this Stand-Alone Library. This switch is used to guarantee that elaboration
8019 flag checks are generated.
8022 @cindex @option{^-h^/HELP^} (@command{gnatbind})
8023 Output usage (help) information
8026 @cindex @option{^-I^/SEARCH^} (@command{gnatbind})
8027 Specify directory to be searched for source and ALI files.
8029 @item ^-I-^/NOCURRENT_DIRECTORY^
8030 @cindex @option{^-I-^/NOCURRENT_DIRECTORY^} (@command{gnatbind})
8031 Do not look for sources in the current directory where @code{gnatbind} was
8032 invoked, and do not look for ALI files in the directory containing the
8033 ALI file named in the @code{gnatbind} command line.
8035 @item ^-l^/ORDER_OF_ELABORATION^
8036 @cindex @option{^-l^/ORDER_OF_ELABORATION^} (@command{gnatbind})
8037 Output chosen elaboration order.
8039 @item ^-L@var{xxx}^/BUILD_LIBRARY=@var{xxx}^
8040 @cindex @option{^-L^/BUILD_LIBRARY^} (@command{gnatbind})
8041 Bind the units for library building. In this case the adainit and
8042 adafinal procedures (@pxref{Binding with Non-Ada Main Programs})
8043 are renamed to ^@var{xxx}init^@var{XXX}INIT^ and
8044 ^@var{xxx}final^@var{XXX}FINAL^.
8045 Implies ^-n^/NOCOMPILE^.
8047 (@xref{GNAT and Libraries}, for more details.)
8050 On OpenVMS, these init and final procedures are exported in uppercase
8051 letters. For example if /BUILD_LIBRARY=toto is used, the exported name of
8052 the init procedure will be "TOTOINIT" and the exported name of the final
8053 procedure will be "TOTOFINAL".
8056 @item ^-Mxyz^/RENAME_MAIN=xyz^
8057 @cindex @option{^-M^/RENAME_MAIN^} (@command{gnatbind})
8058 Rename generated main program from main to xyz. This option is
8059 supported on cross environments only.
8061 @item ^-m^/ERROR_LIMIT=^@var{n}
8062 @cindex @option{^-m^/ERROR_LIMIT^} (@command{gnatbind})
8063 Limit number of detected errors or warnings to @var{n}, where @var{n} is
8064 in the range 1..999999. The default value if no switch is
8065 given is 9999. If the number of warnings reaches this limit, then a
8066 message is output and further warnings are suppressed, the bind
8067 continues in this case. If the number of errors reaches this
8068 limit, then a message is output and the bind is abandoned.
8069 A value of zero means that no limit is enforced. The equal
8073 Furthermore, under Windows, the sources pointed to by the libraries path
8074 set in the registry are not searched for.
8078 @cindex @option{^-n^/NOMAIN^} (@command{gnatbind})
8082 @cindex @option{-nostdinc} (@command{gnatbind})
8083 Do not look for sources in the system default directory.
8086 @cindex @option{-nostdlib} (@command{gnatbind})
8087 Do not look for library files in the system default directory.
8089 @item --RTS=@var{rts-path}
8090 @cindex @option{--RTS} (@code{gnatbind})
8091 Specifies the default location of the runtime library. Same meaning as the
8092 equivalent @command{gnatmake} flag (@pxref{Switches for gnatmake}).
8094 @item ^-o ^/OUTPUT=^@var{file}
8095 @cindex @option{^-o ^/OUTPUT^} (@command{gnatbind})
8096 Name the output file @var{file} (default is @file{b~@var{xxx}.adb}).
8097 Note that if this option is used, then linking must be done manually,
8098 gnatlink cannot be used.
8100 @item ^-O^/OBJECT_LIST^
8101 @cindex @option{^-O^/OBJECT_LIST^} (@command{gnatbind})
8104 @item ^-p^/PESSIMISTIC_ELABORATION^
8105 @cindex @option{^-p^/PESSIMISTIC_ELABORATION^} (@command{gnatbind})
8106 Pessimistic (worst-case) elaboration order
8109 @cindex @option{^-R^-R^} (@command{gnatbind})
8110 Output closure source list.
8112 @item ^-s^/READ_SOURCES=ALL^
8113 @cindex @option{^-s^/READ_SOURCES=ALL^} (@command{gnatbind})
8114 Require all source files to be present.
8116 @item ^-S@var{xxx}^/INITIALIZE_SCALARS=@var{xxx}^
8117 @cindex @option{^-S^/INITIALIZE_SCALARS^} (@command{gnatbind})
8118 Specifies the value to be used when detecting uninitialized scalar
8119 objects with pragma Initialize_Scalars.
8120 The @var{xxx} ^string specified with the switch^option^ may be either
8122 @item ``@option{^in^INVALID^}'' requesting an invalid value where possible
8123 @item ``@option{^lo^LOW^}'' for the lowest possible value
8124 @item ``@option{^hi^HIGH^}'' for the highest possible value
8125 @item ``@option{@var{xx}}'' for a value consisting of repeated bytes with the
8126 value @code{16#@var{xx}#} (i.e., @var{xx} is a string of two hexadecimal digits).
8129 In addition, you can specify @option{-Sev} to indicate that the value is
8130 to be set at run time. In this case, the program will look for an environment
8131 @cindex GNAT_INIT_SCALARS
8132 variable of the form @env{GNAT_INIT_SCALARS=@var{xx}}, where @var{xx} is one
8133 of @option{in/lo/hi/@var{xx}} with the same meanings as above.
8134 If no environment variable is found, or if it does not have a valid value,
8135 then the default is @option{in} (invalid values).
8139 @cindex @option{-static} (@code{gnatbind})
8140 Link against a static GNAT run time.
8143 @cindex @option{-shared} (@code{gnatbind})
8144 Link against a shared GNAT run time when available.
8147 @item ^-t^/NOTIME_STAMP_CHECK^
8148 @cindex @option{^-t^/NOTIME_STAMP_CHECK^} (@code{gnatbind})
8149 Tolerate time stamp and other consistency errors
8151 @item ^-T@var{n}^/TIME_SLICE=@var{n}^
8152 @cindex @option{^-T^/TIME_SLICE^} (@code{gnatbind})
8153 Set the time slice value to @var{n} milliseconds. If the system supports
8154 the specification of a specific time slice value, then the indicated value
8155 is used. If the system does not support specific time slice values, but
8156 does support some general notion of round-robin scheduling, then any
8157 nonzero value will activate round-robin scheduling.
8159 A value of zero is treated specially. It turns off time
8160 slicing, and in addition, indicates to the tasking run time that the
8161 semantics should match as closely as possible the Annex D
8162 requirements of the Ada RM, and in particular sets the default
8163 scheduling policy to @code{FIFO_Within_Priorities}.
8165 @item ^-u@var{n}^/DYNAMIC_STACK_USAGE=@var{n}^
8166 @cindex @option{^-u^/DYNAMIC_STACK_USAGE^} (@code{gnatbind})
8167 Enable dynamic stack usage, with @var{n} results stored and displayed
8168 at program termination. A result is generated when a task
8169 terminates. Results that can't be stored are displayed on the fly, at
8170 task termination. This option is currently not supported on Itanium
8171 platforms. (See @ref{Dynamic Stack Usage Analysis} for details.)
8173 @item ^-v^/REPORT_ERRORS=VERBOSE^
8174 @cindex @option{^-v^/REPORT_ERRORS=VERBOSE^} (@code{gnatbind})
8175 Verbose mode. Write error messages, header, summary output to
8180 @cindex @option{-w} (@code{gnatbind})
8181 Warning mode (@var{x}=s/e for suppress/treat as error)
8185 @item /WARNINGS=NORMAL
8186 @cindex @option{/WARNINGS} (@code{gnatbind})
8187 Normal warnings mode. Warnings are issued but ignored
8189 @item /WARNINGS=SUPPRESS
8190 @cindex @option{/WARNINGS} (@code{gnatbind})
8191 All warning messages are suppressed
8193 @item /WARNINGS=ERROR
8194 @cindex @option{/WARNINGS} (@code{gnatbind})
8195 Warning messages are treated as fatal errors
8198 @item ^-Wx^/WIDE_CHARACTER_ENCODING=^@var{e}
8199 @cindex @option{^-Wx^/WIDE_CHARACTER_ENCODING^} (@code{gnatbind})
8200 Override default wide character encoding for standard Text_IO files.
8202 @item ^-x^/READ_SOURCES=NONE^
8203 @cindex @option{^-x^/READ_SOURCES^} (@code{gnatbind})
8204 Exclude source files (check object consistency only).
8207 @item /READ_SOURCES=AVAILABLE
8208 @cindex @option{/READ_SOURCES} (@code{gnatbind})
8209 Default mode, in which sources are checked for consistency only if
8213 @item ^-y^/ENABLE_LEAP_SECONDS^
8214 @cindex @option{^-y^/ENABLE_LEAP_SECONDS^} (@code{gnatbind})
8215 Enable leap seconds support in @code{Ada.Calendar} and its children.
8217 @item ^-z^/ZERO_MAIN^
8218 @cindex @option{^-z^/ZERO_MAIN^} (@code{gnatbind})
8224 You may obtain this listing of switches by running @code{gnatbind} with
8228 @node Consistency-Checking Modes
8229 @subsection Consistency-Checking Modes
8232 As described earlier, by default @code{gnatbind} checks
8233 that object files are consistent with one another and are consistent
8234 with any source files it can locate. The following switches control binder
8239 @item ^-s^/READ_SOURCES=ALL^
8240 @cindex @option{^-s^/READ_SOURCES=ALL^} (@code{gnatbind})
8241 Require source files to be present. In this mode, the binder must be
8242 able to locate all source files that are referenced, in order to check
8243 their consistency. In normal mode, if a source file cannot be located it
8244 is simply ignored. If you specify this switch, a missing source
8247 @item ^-Wx^/WIDE_CHARACTER_ENCODING=^@var{e}
8248 @cindex @option{^-Wx^/WIDE_CHARACTER_ENCODING^} (@code{gnatbind})
8249 Override default wide character encoding for standard Text_IO files.
8250 Normally the default wide character encoding method used for standard
8251 [Wide_[Wide_]]Text_IO files is taken from the encoding specified for
8252 the main source input (see description of switch
8253 @option{^-gnatWx^/WIDE_CHARACTER_ENCODING^} for the compiler). The
8254 use of this switch for the binder (which has the same set of
8255 possible arguments) overrides this default as specified.
8257 @item ^-x^/READ_SOURCES=NONE^
8258 @cindex @option{^-x^/READ_SOURCES=NONE^} (@code{gnatbind})
8259 Exclude source files. In this mode, the binder only checks that ALI
8260 files are consistent with one another. Source files are not accessed.
8261 The binder runs faster in this mode, and there is still a guarantee that
8262 the resulting program is self-consistent.
8263 If a source file has been edited since it was last compiled, and you
8264 specify this switch, the binder will not detect that the object
8265 file is out of date with respect to the source file. Note that this is the
8266 mode that is automatically used by @command{gnatmake} because in this
8267 case the checking against sources has already been performed by
8268 @command{gnatmake} in the course of compilation (i.e.@: before binding).
8271 @item /READ_SOURCES=AVAILABLE
8272 @cindex @code{/READ_SOURCES=AVAILABLE} (@code{gnatbind})
8273 This is the default mode in which source files are checked if they are
8274 available, and ignored if they are not available.
8278 @node Binder Error Message Control
8279 @subsection Binder Error Message Control
8282 The following switches provide control over the generation of error
8283 messages from the binder:
8287 @item ^-v^/REPORT_ERRORS=VERBOSE^
8288 @cindex @option{^-v^/REPORT_ERRORS=VERBOSE^} (@code{gnatbind})
8289 Verbose mode. In the normal mode, brief error messages are generated to
8290 @file{stderr}. If this switch is present, a header is written
8291 to @file{stdout} and any error messages are directed to @file{stdout}.
8292 All that is written to @file{stderr} is a brief summary message.
8294 @item ^-b^/REPORT_ERRORS=BRIEF^
8295 @cindex @option{^-b^/REPORT_ERRORS=BRIEF^} (@code{gnatbind})
8296 Generate brief error messages to @file{stderr} even if verbose mode is
8297 specified. This is relevant only when used with the
8298 @option{^-v^/REPORT_ERRORS=VERBOSE^} switch.
8302 @cindex @option{-m} (@code{gnatbind})
8303 Limits the number of error messages to @var{n}, a decimal integer in the
8304 range 1-999. The binder terminates immediately if this limit is reached.
8307 @cindex @option{-M} (@code{gnatbind})
8308 Renames the generated main program from @code{main} to @code{xxx}.
8309 This is useful in the case of some cross-building environments, where
8310 the actual main program is separate from the one generated
8314 @item ^-ws^/WARNINGS=SUPPRESS^
8315 @cindex @option{^-ws^/WARNINGS=SUPPRESS^} (@code{gnatbind})
8317 Suppress all warning messages.
8319 @item ^-we^/WARNINGS=ERROR^
8320 @cindex @option{^-we^/WARNINGS=ERROR^} (@code{gnatbind})
8321 Treat any warning messages as fatal errors.
8324 @item /WARNINGS=NORMAL
8325 Standard mode with warnings generated, but warnings do not get treated
8329 @item ^-t^/NOTIME_STAMP_CHECK^
8330 @cindex @option{^-t^/NOTIME_STAMP_CHECK^} (@code{gnatbind})
8331 @cindex Time stamp checks, in binder
8332 @cindex Binder consistency checks
8333 @cindex Consistency checks, in binder
8334 The binder performs a number of consistency checks including:
8338 Check that time stamps of a given source unit are consistent
8340 Check that checksums of a given source unit are consistent
8342 Check that consistent versions of @code{GNAT} were used for compilation
8344 Check consistency of configuration pragmas as required
8348 Normally failure of such checks, in accordance with the consistency
8349 requirements of the Ada Reference Manual, causes error messages to be
8350 generated which abort the binder and prevent the output of a binder
8351 file and subsequent link to obtain an executable.
8353 The @option{^-t^/NOTIME_STAMP_CHECK^} switch converts these error messages
8354 into warnings, so that
8355 binding and linking can continue to completion even in the presence of such
8356 errors. The result may be a failed link (due to missing symbols), or a
8357 non-functional executable which has undefined semantics.
8358 @emph{This means that
8359 @option{^-t^/NOTIME_STAMP_CHECK^} should be used only in unusual situations,
8363 @node Elaboration Control
8364 @subsection Elaboration Control
8367 The following switches provide additional control over the elaboration
8368 order. For full details see @ref{Elaboration Order Handling in GNAT}.
8371 @item ^-p^/PESSIMISTIC_ELABORATION^
8372 @cindex @option{^-p^/PESSIMISTIC_ELABORATION^} (@code{gnatbind})
8373 Normally the binder attempts to choose an elaboration order that is
8374 likely to minimize the likelihood of an elaboration order error resulting
8375 in raising a @code{Program_Error} exception. This switch reverses the
8376 action of the binder, and requests that it deliberately choose an order
8377 that is likely to maximize the likelihood of an elaboration error.
8378 This is useful in ensuring portability and avoiding dependence on
8379 accidental fortuitous elaboration ordering.
8381 Normally it only makes sense to use the @option{^-p^/PESSIMISTIC_ELABORATION^}
8383 elaboration checking is used (@option{-gnatE} switch used for compilation).
8384 This is because in the default static elaboration mode, all necessary
8385 @code{Elaborate} and @code{Elaborate_All} pragmas are implicitly inserted.
8386 These implicit pragmas are still respected by the binder in
8387 @option{^-p^/PESSIMISTIC_ELABORATION^} mode, so a
8388 safe elaboration order is assured.
8391 @node Output Control
8392 @subsection Output Control
8395 The following switches allow additional control over the output
8396 generated by the binder.
8401 @item ^-A^/BIND_FILE=ADA^
8402 @cindex @option{^-A^/BIND_FILE=ADA^} (@code{gnatbind})
8403 Generate binder program in Ada (default). The binder program is named
8404 @file{b~@var{mainprog}.adb} by default. This can be changed with
8405 @option{^-o^/OUTPUT^} @code{gnatbind} option.
8407 @item ^-c^/NOOUTPUT^
8408 @cindex @option{^-c^/NOOUTPUT^} (@code{gnatbind})
8409 Check only. Do not generate the binder output file. In this mode the
8410 binder performs all error checks but does not generate an output file.
8412 @item ^-C^/BIND_FILE=C^
8413 @cindex @option{^-C^/BIND_FILE=C^} (@code{gnatbind})
8414 Generate binder program in C. The binder program is named
8415 @file{b_@var{mainprog}.c}.
8416 This can be changed with @option{^-o^/OUTPUT^} @code{gnatbind}
8419 @item ^-e^/ELABORATION_DEPENDENCIES^
8420 @cindex @option{^-e^/ELABORATION_DEPENDENCIES^} (@code{gnatbind})
8421 Output complete list of elaboration-order dependencies, showing the
8422 reason for each dependency. This output can be rather extensive but may
8423 be useful in diagnosing problems with elaboration order. The output is
8424 written to @file{stdout}.
8427 @cindex @option{^-h^/HELP^} (@code{gnatbind})
8428 Output usage information. The output is written to @file{stdout}.
8430 @item ^-K^/LINKER_OPTION_LIST^
8431 @cindex @option{^-K^/LINKER_OPTION_LIST^} (@code{gnatbind})
8432 Output linker options to @file{stdout}. Includes library search paths,
8433 contents of pragmas Ident and Linker_Options, and libraries added
8436 @item ^-l^/ORDER_OF_ELABORATION^
8437 @cindex @option{^-l^/ORDER_OF_ELABORATION^} (@code{gnatbind})
8438 Output chosen elaboration order. The output is written to @file{stdout}.
8440 @item ^-O^/OBJECT_LIST^
8441 @cindex @option{^-O^/OBJECT_LIST^} (@code{gnatbind})
8442 Output full names of all the object files that must be linked to provide
8443 the Ada component of the program. The output is written to @file{stdout}.
8444 This list includes the files explicitly supplied and referenced by the user
8445 as well as implicitly referenced run-time unit files. The latter are
8446 omitted if the corresponding units reside in shared libraries. The
8447 directory names for the run-time units depend on the system configuration.
8449 @item ^-o ^/OUTPUT=^@var{file}
8450 @cindex @option{^-o^/OUTPUT^} (@code{gnatbind})
8451 Set name of output file to @var{file} instead of the normal
8452 @file{b~@var{mainprog}.adb} default. Note that @var{file} denote the Ada
8453 binder generated body filename. In C mode you would normally give
8454 @var{file} an extension of @file{.c} because it will be a C source program.
8455 Note that if this option is used, then linking must be done manually.
8456 It is not possible to use gnatlink in this case, since it cannot locate
8459 @item ^-r^/RESTRICTION_LIST^
8460 @cindex @option{^-r^/RESTRICTION_LIST^} (@code{gnatbind})
8461 Generate list of @code{pragma Restrictions} that could be applied to
8462 the current unit. This is useful for code audit purposes, and also may
8463 be used to improve code generation in some cases.
8467 @node Binding with Non-Ada Main Programs
8468 @subsection Binding with Non-Ada Main Programs
8471 In our description so far we have assumed that the main
8472 program is in Ada, and that the task of the binder is to generate a
8473 corresponding function @code{main} that invokes this Ada main
8474 program. GNAT also supports the building of executable programs where
8475 the main program is not in Ada, but some of the called routines are
8476 written in Ada and compiled using GNAT (@pxref{Mixed Language Programming}).
8477 The following switch is used in this situation:
8481 @cindex @option{^-n^/NOMAIN^} (@code{gnatbind})
8482 No main program. The main program is not in Ada.
8486 In this case, most of the functions of the binder are still required,
8487 but instead of generating a main program, the binder generates a file
8488 containing the following callable routines:
8493 You must call this routine to initialize the Ada part of the program by
8494 calling the necessary elaboration routines. A call to @code{adainit} is
8495 required before the first call to an Ada subprogram.
8497 Note that it is assumed that the basic execution environment must be setup
8498 to be appropriate for Ada execution at the point where the first Ada
8499 subprogram is called. In particular, if the Ada code will do any
8500 floating-point operations, then the FPU must be setup in an appropriate
8501 manner. For the case of the x86, for example, full precision mode is
8502 required. The procedure GNAT.Float_Control.Reset may be used to ensure
8503 that the FPU is in the right state.
8507 You must call this routine to perform any library-level finalization
8508 required by the Ada subprograms. A call to @code{adafinal} is required
8509 after the last call to an Ada subprogram, and before the program
8514 If the @option{^-n^/NOMAIN^} switch
8515 @cindex @option{^-n^/NOMAIN^} (@command{gnatbind})
8516 @cindex Binder, multiple input files
8517 is given, more than one ALI file may appear on
8518 the command line for @code{gnatbind}. The normal @dfn{closure}
8519 calculation is performed for each of the specified units. Calculating
8520 the closure means finding out the set of units involved by tracing
8521 @code{with} references. The reason it is necessary to be able to
8522 specify more than one ALI file is that a given program may invoke two or
8523 more quite separate groups of Ada units.
8525 The binder takes the name of its output file from the last specified ALI
8526 file, unless overridden by the use of the @option{^-o file^/OUTPUT=file^}.
8527 @cindex @option{^-o^/OUTPUT^} (@command{gnatbind})
8528 The output is an Ada unit in source form that can
8529 be compiled with GNAT unless the -C switch is used in which case the
8530 output is a C source file, which must be compiled using the C compiler.
8531 This compilation occurs automatically as part of the @command{gnatlink}
8534 Currently the GNAT run time requires a FPU using 80 bits mode
8535 precision. Under targets where this is not the default it is required to
8536 call GNAT.Float_Control.Reset before using floating point numbers (this
8537 include float computation, float input and output) in the Ada code. A
8538 side effect is that this could be the wrong mode for the foreign code
8539 where floating point computation could be broken after this call.
8541 @node Binding Programs with No Main Subprogram
8542 @subsection Binding Programs with No Main Subprogram
8545 It is possible to have an Ada program which does not have a main
8546 subprogram. This program will call the elaboration routines of all the
8547 packages, then the finalization routines.
8549 The following switch is used to bind programs organized in this manner:
8552 @item ^-z^/ZERO_MAIN^
8553 @cindex @option{^-z^/ZERO_MAIN^} (@code{gnatbind})
8554 Normally the binder checks that the unit name given on the command line
8555 corresponds to a suitable main subprogram. When this switch is used,
8556 a list of ALI files can be given, and the execution of the program
8557 consists of elaboration of these units in an appropriate order. Note
8558 that the default wide character encoding method for standard Text_IO
8559 files is always set to Brackets if this switch is set (you can use
8561 @option{^-Wx^WIDE_CHARACTER_ENCODING^} to override this default).
8564 @node Command-Line Access
8565 @section Command-Line Access
8568 The package @code{Ada.Command_Line} provides access to the command-line
8569 arguments and program name. In order for this interface to operate
8570 correctly, the two variables
8582 are declared in one of the GNAT library routines. These variables must
8583 be set from the actual @code{argc} and @code{argv} values passed to the
8584 main program. With no @option{^n^/NOMAIN^} present, @code{gnatbind}
8585 generates the C main program to automatically set these variables.
8586 If the @option{^n^/NOMAIN^} switch is used, there is no automatic way to
8587 set these variables. If they are not set, the procedures in
8588 @code{Ada.Command_Line} will not be available, and any attempt to use
8589 them will raise @code{Constraint_Error}. If command line access is
8590 required, your main program must set @code{gnat_argc} and
8591 @code{gnat_argv} from the @code{argc} and @code{argv} values passed to
8594 @node Search Paths for gnatbind
8595 @section Search Paths for @code{gnatbind}
8598 The binder takes the name of an ALI file as its argument and needs to
8599 locate source files as well as other ALI files to verify object consistency.
8601 For source files, it follows exactly the same search rules as @command{gcc}
8602 (@pxref{Search Paths and the Run-Time Library (RTL)}). For ALI files the
8603 directories searched are:
8607 The directory containing the ALI file named in the command line, unless
8608 the switch @option{^-I-^/NOCURRENT_DIRECTORY^} is specified.
8611 All directories specified by @option{^-I^/SEARCH^}
8612 switches on the @code{gnatbind}
8613 command line, in the order given.
8616 @findex ADA_PRJ_OBJECTS_FILE
8617 Each of the directories listed in the text file whose name is given
8618 by the @env{ADA_PRJ_OBJECTS_FILE} ^environment variable^logical name^.
8621 @env{ADA_PRJ_OBJECTS_FILE} is normally set by gnatmake or by the ^gnat^GNAT^
8622 driver when project files are used. It should not normally be set
8626 @findex ADA_OBJECTS_PATH
8627 Each of the directories listed in the value of the
8628 @env{ADA_OBJECTS_PATH} ^environment variable^logical name^.
8630 Construct this value
8631 exactly as the @env{PATH} environment variable: a list of directory
8632 names separated by colons (semicolons when working with the NT version
8636 Normally, define this value as a logical name containing a comma separated
8637 list of directory names.
8639 This variable can also be defined by means of an environment string
8640 (an argument to the HP C exec* set of functions).
8644 DEFINE ANOTHER_PATH FOO:[BAG]
8645 DEFINE ADA_OBJECTS_PATH ANOTHER_PATH,FOO:[BAM],FOO:[BAR]
8648 By default, the path includes GNU:[LIB.OPENVMS7_x.2_8_x.DECLIB]
8649 first, followed by the standard Ada
8650 libraries in GNU:[LIB.OPENVMS7_x.2_8_x.ADALIB].
8651 If this is not redefined, the user will obtain the HP Ada 83 IO packages
8652 (Text_IO, Sequential_IO, etc)
8653 instead of the standard Ada packages. Thus, in order to get the standard Ada
8654 packages by default, ADA_OBJECTS_PATH must be redefined.
8658 The content of the @file{ada_object_path} file which is part of the GNAT
8659 installation tree and is used to store standard libraries such as the
8660 GNAT Run Time Library (RTL) unless the switch @option{-nostdlib} is
8663 @ref{Installing a library}
8668 In the binder the switch @option{^-I^/SEARCH^}
8669 @cindex @option{^-I^/SEARCH^} (@command{gnatbind})
8670 is used to specify both source and
8671 library file paths. Use @option{^-aI^/SOURCE_SEARCH^}
8672 @cindex @option{^-aI^/SOURCE_SEARCH^} (@command{gnatbind})
8673 instead if you want to specify
8674 source paths only, and @option{^-aO^/LIBRARY_SEARCH^}
8675 @cindex @option{^-aO^/LIBRARY_SEARCH^} (@command{gnatbind})
8676 if you want to specify library paths
8677 only. This means that for the binder
8678 @option{^-I^/SEARCH=^}@var{dir} is equivalent to
8679 @option{^-aI^/SOURCE_SEARCH=^}@var{dir}
8680 @option{^-aO^/OBJECT_SEARCH=^}@var{dir}.
8681 The binder generates the bind file (a C language source file) in the
8682 current working directory.
8688 The packages @code{Ada}, @code{System}, and @code{Interfaces} and their
8689 children make up the GNAT Run-Time Library, together with the package
8690 GNAT and its children, which contain a set of useful additional
8691 library functions provided by GNAT. The sources for these units are
8692 needed by the compiler and are kept together in one directory. The ALI
8693 files and object files generated by compiling the RTL are needed by the
8694 binder and the linker and are kept together in one directory, typically
8695 different from the directory containing the sources. In a normal
8696 installation, you need not specify these directory names when compiling
8697 or binding. Either the environment variables or the built-in defaults
8698 cause these files to be found.
8700 Besides simplifying access to the RTL, a major use of search paths is
8701 in compiling sources from multiple directories. This can make
8702 development environments much more flexible.
8704 @node Examples of gnatbind Usage
8705 @section Examples of @code{gnatbind} Usage
8708 This section contains a number of examples of using the GNAT binding
8709 utility @code{gnatbind}.
8712 @item gnatbind hello
8713 The main program @code{Hello} (source program in @file{hello.adb}) is
8714 bound using the standard switch settings. The generated main program is
8715 @file{b~hello.adb}. This is the normal, default use of the binder.
8718 @item gnatbind hello -o mainprog.adb
8721 @item gnatbind HELLO.ALI /OUTPUT=Mainprog.ADB
8723 The main program @code{Hello} (source program in @file{hello.adb}) is
8724 bound using the standard switch settings. The generated main program is
8725 @file{mainprog.adb} with the associated spec in
8726 @file{mainprog.ads}. Note that you must specify the body here not the
8727 spec, in the case where the output is in Ada. Note that if this option
8728 is used, then linking must be done manually, since gnatlink will not
8729 be able to find the generated file.
8732 @item gnatbind main -C -o mainprog.c -x
8735 @item gnatbind MAIN.ALI /BIND_FILE=C /OUTPUT=Mainprog.C /READ_SOURCES=NONE
8737 The main program @code{Main} (source program in
8738 @file{main.adb}) is bound, excluding source files from the
8739 consistency checking, generating
8740 the file @file{mainprog.c}.
8743 @item gnatbind -x main_program -C -o mainprog.c
8744 This command is exactly the same as the previous example. Switches may
8745 appear anywhere in the command line, and single letter switches may be
8746 combined into a single switch.
8750 @item gnatbind -n math dbase -C -o ada-control.c
8753 @item gnatbind /NOMAIN math dbase /BIND_FILE=C /OUTPUT=ada-control.c
8755 The main program is in a language other than Ada, but calls to
8756 subprograms in packages @code{Math} and @code{Dbase} appear. This call
8757 to @code{gnatbind} generates the file @file{ada-control.c} containing
8758 the @code{adainit} and @code{adafinal} routines to be called before and
8759 after accessing the Ada units.
8762 @c ------------------------------------
8763 @node Linking Using gnatlink
8764 @chapter Linking Using @command{gnatlink}
8765 @c ------------------------------------
8769 This chapter discusses @command{gnatlink}, a tool that links
8770 an Ada program and builds an executable file. This utility
8771 invokes the system linker ^(via the @command{gcc} command)^^
8772 with a correct list of object files and library references.
8773 @command{gnatlink} automatically determines the list of files and
8774 references for the Ada part of a program. It uses the binder file
8775 generated by the @command{gnatbind} to determine this list.
8777 Note: to invoke @code{gnatlink} with a project file, use the @code{gnat}
8778 driver (see @ref{The GNAT Driver and Project Files}).
8781 * Running gnatlink::
8782 * Switches for gnatlink::
8785 @node Running gnatlink
8786 @section Running @command{gnatlink}
8789 The form of the @command{gnatlink} command is
8792 $ gnatlink @ovar{switches} @var{mainprog}@r{[}.ali@r{]}
8793 @ovar{non-Ada objects} @ovar{linker options}
8797 The arguments of @command{gnatlink} (switches, main @file{ALI} file,
8799 or linker options) may be in any order, provided that no non-Ada object may
8800 be mistaken for a main @file{ALI} file.
8801 Any file name @file{F} without the @file{.ali}
8802 extension will be taken as the main @file{ALI} file if a file exists
8803 whose name is the concatenation of @file{F} and @file{.ali}.
8806 @file{@var{mainprog}.ali} references the ALI file of the main program.
8807 The @file{.ali} extension of this file can be omitted. From this
8808 reference, @command{gnatlink} locates the corresponding binder file
8809 @file{b~@var{mainprog}.adb} and, using the information in this file along
8810 with the list of non-Ada objects and linker options, constructs a
8811 linker command file to create the executable.
8813 The arguments other than the @command{gnatlink} switches and the main
8814 @file{ALI} file are passed to the linker uninterpreted.
8815 They typically include the names of
8816 object files for units written in other languages than Ada and any library
8817 references required to resolve references in any of these foreign language
8818 units, or in @code{Import} pragmas in any Ada units.
8820 @var{linker options} is an optional list of linker specific
8822 The default linker called by gnatlink is @command{gcc} which in
8823 turn calls the appropriate system linker.
8824 Standard options for the linker such as @option{-lmy_lib} or
8825 @option{-Ldir} can be added as is.
8826 For options that are not recognized by
8827 @command{gcc} as linker options, use the @command{gcc} switches
8828 @option{-Xlinker} or @option{-Wl,}.
8829 Refer to the GCC documentation for
8830 details. Here is an example showing how to generate a linker map:
8833 $ ^gnatlink my_prog -Wl,-Map,MAPFILE^GNAT LINK my_prog.ali /MAP^
8836 Using @var{linker options} it is possible to set the program stack and
8839 See @ref{Setting Stack Size from gnatlink} and
8840 @ref{Setting Heap Size from gnatlink}.
8843 @command{gnatlink} determines the list of objects required by the Ada
8844 program and prepends them to the list of objects passed to the linker.
8845 @command{gnatlink} also gathers any arguments set by the use of
8846 @code{pragma Linker_Options} and adds them to the list of arguments
8847 presented to the linker.
8850 @command{gnatlink} accepts the following types of extra files on the command
8851 line: objects (@file{.OBJ}), libraries (@file{.OLB}), sharable images
8852 (@file{.EXE}), and options files (@file{.OPT}). These are recognized and
8853 handled according to their extension.
8856 @node Switches for gnatlink
8857 @section Switches for @command{gnatlink}
8860 The following switches are available with the @command{gnatlink} utility:
8866 @cindex @option{--version} @command{gnatlink}
8867 Display Copyright and version, then exit disregarding all other options.
8870 @cindex @option{--help} @command{gnatlink}
8871 If @option{--version} was not used, display usage, then exit disregarding
8874 @item ^-A^/BIND_FILE=ADA^
8875 @cindex @option{^-A^/BIND_FILE=ADA^} (@command{gnatlink})
8876 The binder has generated code in Ada. This is the default.
8878 @item ^-C^/BIND_FILE=C^
8879 @cindex @option{^-C^/BIND_FILE=C^} (@command{gnatlink})
8880 If instead of generating a file in Ada, the binder has generated one in
8881 C, then the linker needs to know about it. Use this switch to signal
8882 to @command{gnatlink} that the binder has generated C code rather than
8885 @item ^-f^/FORCE_OBJECT_FILE_LIST^
8886 @cindex Command line length
8887 @cindex @option{^-f^/FORCE_OBJECT_FILE_LIST^} (@command{gnatlink})
8888 On some targets, the command line length is limited, and @command{gnatlink}
8889 will generate a separate file for the linker if the list of object files
8891 The @option{^-f^/FORCE_OBJECT_FILE_LIST^} switch forces this file
8892 to be generated even if
8893 the limit is not exceeded. This is useful in some cases to deal with
8894 special situations where the command line length is exceeded.
8897 @cindex Debugging information, including
8898 @cindex @option{^-g^/DEBUG^} (@command{gnatlink})
8899 The option to include debugging information causes the Ada bind file (in
8900 other words, @file{b~@var{mainprog}.adb}) to be compiled with
8901 @option{^-g^/DEBUG^}.
8902 In addition, the binder does not delete the @file{b~@var{mainprog}.adb},
8903 @file{b~@var{mainprog}.o} and @file{b~@var{mainprog}.ali} files.
8904 Without @option{^-g^/DEBUG^}, the binder removes these files by
8905 default. The same procedure apply if a C bind file was generated using
8906 @option{^-C^/BIND_FILE=C^} @code{gnatbind} option, in this case the filenames
8907 are @file{b_@var{mainprog}.c} and @file{b_@var{mainprog}.o}.
8909 @item ^-n^/NOCOMPILE^
8910 @cindex @option{^-n^/NOCOMPILE^} (@command{gnatlink})
8911 Do not compile the file generated by the binder. This may be used when
8912 a link is rerun with different options, but there is no need to recompile
8916 @cindex @option{^-v^/VERBOSE^} (@command{gnatlink})
8917 Causes additional information to be output, including a full list of the
8918 included object files. This switch option is most useful when you want
8919 to see what set of object files are being used in the link step.
8921 @item ^-v -v^/VERBOSE/VERBOSE^
8922 @cindex @option{^-v -v^/VERBOSE/VERBOSE^} (@command{gnatlink})
8923 Very verbose mode. Requests that the compiler operate in verbose mode when
8924 it compiles the binder file, and that the system linker run in verbose mode.
8926 @item ^-o ^/EXECUTABLE=^@var{exec-name}
8927 @cindex @option{^-o^/EXECUTABLE^} (@command{gnatlink})
8928 @var{exec-name} specifies an alternate name for the generated
8929 executable program. If this switch is omitted, the executable has the same
8930 name as the main unit. For example, @code{gnatlink try.ali} creates
8931 an executable called @file{^try^TRY.EXE^}.
8934 @item -b @var{target}
8935 @cindex @option{-b} (@command{gnatlink})
8936 Compile your program to run on @var{target}, which is the name of a
8937 system configuration. You must have a GNAT cross-compiler built if
8938 @var{target} is not the same as your host system.
8941 @cindex @option{-B} (@command{gnatlink})
8942 Load compiler executables (for example, @code{gnat1}, the Ada compiler)
8943 from @var{dir} instead of the default location. Only use this switch
8944 when multiple versions of the GNAT compiler are available.
8945 @xref{Directory Options,,, gcc, The GNU Compiler Collection},
8946 for further details. You would normally use the @option{-b} or
8947 @option{-V} switch instead.
8949 @item --GCC=@var{compiler_name}
8950 @cindex @option{--GCC=compiler_name} (@command{gnatlink})
8951 Program used for compiling the binder file. The default is
8952 @command{gcc}. You need to use quotes around @var{compiler_name} if
8953 @code{compiler_name} contains spaces or other separator characters.
8954 As an example @option{--GCC="foo -x -y"} will instruct @command{gnatlink} to
8955 use @code{foo -x -y} as your compiler. Note that switch @option{-c} is always
8956 inserted after your command name. Thus in the above example the compiler
8957 command that will be used by @command{gnatlink} will be @code{foo -c -x -y}.
8958 A limitation of this syntax is that the name and path name of the executable
8959 itself must not include any embedded spaces. If the compiler executable is
8960 different from the default one (gcc or <prefix>-gcc), then the back-end
8961 switches in the ALI file are not used to compile the binder generated source.
8962 For example, this is the case with @option{--GCC="foo -x -y"}. But the back end
8963 switches will be used for @option{--GCC="gcc -gnatv"}. If several
8964 @option{--GCC=compiler_name} are used, only the last @var{compiler_name}
8965 is taken into account. However, all the additional switches are also taken
8967 @option{--GCC="foo -x -y" --GCC="bar -z -t"} is equivalent to
8968 @option{--GCC="bar -x -y -z -t"}.
8970 @item --LINK=@var{name}
8971 @cindex @option{--LINK=} (@command{gnatlink})
8972 @var{name} is the name of the linker to be invoked. This is especially
8973 useful in mixed language programs since languages such as C++ require
8974 their own linker to be used. When this switch is omitted, the default
8975 name for the linker is @command{gcc}. When this switch is used, the
8976 specified linker is called instead of @command{gcc} with exactly the same
8977 parameters that would have been passed to @command{gcc} so if the desired
8978 linker requires different parameters it is necessary to use a wrapper
8979 script that massages the parameters before invoking the real linker. It
8980 may be useful to control the exact invocation by using the verbose
8986 @item /DEBUG=TRACEBACK
8987 @cindex @code{/DEBUG=TRACEBACK} (@command{gnatlink})
8988 This qualifier causes sufficient information to be included in the
8989 executable file to allow a traceback, but does not include the full
8990 symbol information needed by the debugger.
8992 @item /IDENTIFICATION="<string>"
8993 @code{"<string>"} specifies the string to be stored in the image file
8994 identification field in the image header.
8995 It overrides any pragma @code{Ident} specified string.
8997 @item /NOINHIBIT-EXEC
8998 Generate the executable file even if there are linker warnings.
9000 @item /NOSTART_FILES
9001 Don't link in the object file containing the ``main'' transfer address.
9002 Used when linking with a foreign language main program compiled with an
9006 Prefer linking with object libraries over sharable images, even without
9012 @node The GNAT Make Program gnatmake
9013 @chapter The GNAT Make Program @command{gnatmake}
9017 * Running gnatmake::
9018 * Switches for gnatmake::
9019 * Mode Switches for gnatmake::
9020 * Notes on the Command Line::
9021 * How gnatmake Works::
9022 * Examples of gnatmake Usage::
9025 A typical development cycle when working on an Ada program consists of
9026 the following steps:
9030 Edit some sources to fix bugs.
9036 Compile all sources affected.
9046 The third step can be tricky, because not only do the modified files
9047 @cindex Dependency rules
9048 have to be compiled, but any files depending on these files must also be
9049 recompiled. The dependency rules in Ada can be quite complex, especially
9050 in the presence of overloading, @code{use} clauses, generics and inlined
9053 @command{gnatmake} automatically takes care of the third and fourth steps
9054 of this process. It determines which sources need to be compiled,
9055 compiles them, and binds and links the resulting object files.
9057 Unlike some other Ada make programs, the dependencies are always
9058 accurately recomputed from the new sources. The source based approach of
9059 the GNAT compilation model makes this possible. This means that if
9060 changes to the source program cause corresponding changes in
9061 dependencies, they will always be tracked exactly correctly by
9064 @node Running gnatmake
9065 @section Running @command{gnatmake}
9068 The usual form of the @command{gnatmake} command is
9071 $ gnatmake @ovar{switches} @var{file_name}
9072 @ovar{file_names} @ovar{mode_switches}
9076 The only required argument is one @var{file_name}, which specifies
9077 a compilation unit that is a main program. Several @var{file_names} can be
9078 specified: this will result in several executables being built.
9079 If @code{switches} are present, they can be placed before the first
9080 @var{file_name}, between @var{file_names} or after the last @var{file_name}.
9081 If @var{mode_switches} are present, they must always be placed after
9082 the last @var{file_name} and all @code{switches}.
9084 If you are using standard file extensions (@file{.adb} and @file{.ads}), then the
9085 extension may be omitted from the @var{file_name} arguments. However, if
9086 you are using non-standard extensions, then it is required that the
9087 extension be given. A relative or absolute directory path can be
9088 specified in a @var{file_name}, in which case, the input source file will
9089 be searched for in the specified directory only. Otherwise, the input
9090 source file will first be searched in the directory where
9091 @command{gnatmake} was invoked and if it is not found, it will be search on
9092 the source path of the compiler as described in
9093 @ref{Search Paths and the Run-Time Library (RTL)}.
9095 All @command{gnatmake} output (except when you specify
9096 @option{^-M^/DEPENDENCIES_LIST^}) is to
9097 @file{stderr}. The output produced by the
9098 @option{^-M^/DEPENDENCIES_LIST^} switch is send to
9101 @node Switches for gnatmake
9102 @section Switches for @command{gnatmake}
9105 You may specify any of the following switches to @command{gnatmake}:
9111 @cindex @option{--version} @command{gnatmake}
9112 Display Copyright and version, then exit disregarding all other options.
9115 @cindex @option{--help} @command{gnatmake}
9116 If @option{--version} was not used, display usage, then exit disregarding
9120 @item --GCC=@var{compiler_name}
9121 @cindex @option{--GCC=compiler_name} (@command{gnatmake})
9122 Program used for compiling. The default is `@command{gcc}'. You need to use
9123 quotes around @var{compiler_name} if @code{compiler_name} contains
9124 spaces or other separator characters. As an example @option{--GCC="foo -x
9125 -y"} will instruct @command{gnatmake} to use @code{foo -x -y} as your
9126 compiler. A limitation of this syntax is that the name and path name of
9127 the executable itself must not include any embedded spaces. Note that
9128 switch @option{-c} is always inserted after your command name. Thus in the
9129 above example the compiler command that will be used by @command{gnatmake}
9130 will be @code{foo -c -x -y}. If several @option{--GCC=compiler_name} are
9131 used, only the last @var{compiler_name} is taken into account. However,
9132 all the additional switches are also taken into account. Thus,
9133 @option{--GCC="foo -x -y" --GCC="bar -z -t"} is equivalent to
9134 @option{--GCC="bar -x -y -z -t"}.
9136 @item --GNATBIND=@var{binder_name}
9137 @cindex @option{--GNATBIND=binder_name} (@command{gnatmake})
9138 Program used for binding. The default is `@code{gnatbind}'. You need to
9139 use quotes around @var{binder_name} if @var{binder_name} contains spaces
9140 or other separator characters. As an example @option{--GNATBIND="bar -x
9141 -y"} will instruct @command{gnatmake} to use @code{bar -x -y} as your
9142 binder. Binder switches that are normally appended by @command{gnatmake}
9143 to `@code{gnatbind}' are now appended to the end of @code{bar -x -y}.
9144 A limitation of this syntax is that the name and path name of the executable
9145 itself must not include any embedded spaces.
9147 @item --GNATLINK=@var{linker_name}
9148 @cindex @option{--GNATLINK=linker_name} (@command{gnatmake})
9149 Program used for linking. The default is `@command{gnatlink}'. You need to
9150 use quotes around @var{linker_name} if @var{linker_name} contains spaces
9151 or other separator characters. As an example @option{--GNATLINK="lan -x
9152 -y"} will instruct @command{gnatmake} to use @code{lan -x -y} as your
9153 linker. Linker switches that are normally appended by @command{gnatmake} to
9154 `@command{gnatlink}' are now appended to the end of @code{lan -x -y}.
9155 A limitation of this syntax is that the name and path name of the executable
9156 itself must not include any embedded spaces.
9160 @item ^-a^/ALL_FILES^
9161 @cindex @option{^-a^/ALL_FILES^} (@command{gnatmake})
9162 Consider all files in the make process, even the GNAT internal system
9163 files (for example, the predefined Ada library files), as well as any
9164 locked files. Locked files are files whose ALI file is write-protected.
9166 @command{gnatmake} does not check these files,
9167 because the assumption is that the GNAT internal files are properly up
9168 to date, and also that any write protected ALI files have been properly
9169 installed. Note that if there is an installation problem, such that one
9170 of these files is not up to date, it will be properly caught by the
9172 You may have to specify this switch if you are working on GNAT
9173 itself. The switch @option{^-a^/ALL_FILES^} is also useful
9174 in conjunction with @option{^-f^/FORCE_COMPILE^}
9175 if you need to recompile an entire application,
9176 including run-time files, using special configuration pragmas,
9177 such as a @code{Normalize_Scalars} pragma.
9180 @code{gnatmake ^-a^/ALL_FILES^} compiles all GNAT
9183 @code{gcc -c -gnatpg} rather than @code{gcc -c}.
9186 the @code{/CHECKS=SUPPRESS_ALL /STYLE_CHECKS=GNAT} switch.
9189 @item ^-b^/ACTIONS=BIND^
9190 @cindex @option{^-b^/ACTIONS=BIND^} (@command{gnatmake})
9191 Bind only. Can be combined with @option{^-c^/ACTIONS=COMPILE^} to do
9192 compilation and binding, but no link.
9193 Can be combined with @option{^-l^/ACTIONS=LINK^}
9194 to do binding and linking. When not combined with
9195 @option{^-c^/ACTIONS=COMPILE^}
9196 all the units in the closure of the main program must have been previously
9197 compiled and must be up to date. The root unit specified by @var{file_name}
9198 may be given without extension, with the source extension or, if no GNAT
9199 Project File is specified, with the ALI file extension.
9201 @item ^-c^/ACTIONS=COMPILE^
9202 @cindex @option{^-c^/ACTIONS=COMPILE^} (@command{gnatmake})
9203 Compile only. Do not perform binding, except when @option{^-b^/ACTIONS=BIND^}
9204 is also specified. Do not perform linking, except if both
9205 @option{^-b^/ACTIONS=BIND^} and
9206 @option{^-l^/ACTIONS=LINK^} are also specified.
9207 If the root unit specified by @var{file_name} is not a main unit, this is the
9208 default. Otherwise @command{gnatmake} will attempt binding and linking
9209 unless all objects are up to date and the executable is more recent than
9213 @cindex @option{^-C^/MAPPING^} (@command{gnatmake})
9214 Use a temporary mapping file. A mapping file is a way to communicate to the
9215 compiler two mappings: from unit names to file names (without any directory
9216 information) and from file names to path names (with full directory
9217 information). These mappings are used by the compiler to short-circuit the path
9218 search. When @command{gnatmake} is invoked with this switch, it will create
9219 a temporary mapping file, initially populated by the project manager,
9220 if @option{^-P^/PROJECT_FILE^} is used, otherwise initially empty.
9221 Each invocation of the compiler will add the newly accessed sources to the
9222 mapping file. This will improve the source search during the next invocation
9225 @item ^-C=^/USE_MAPPING_FILE=^@var{file}
9226 @cindex @option{^-C=^/USE_MAPPING^} (@command{gnatmake})
9227 Use a specific mapping file. The file, specified as a path name (absolute or
9228 relative) by this switch, should already exist, otherwise the switch is
9229 ineffective. The specified mapping file will be communicated to the compiler.
9230 This switch is not compatible with a project file
9231 (^-P^/PROJECT_FILE=^@var{file}) or with multiple compiling processes
9232 (^-j^/PROCESSES=^nnn, when nnn is greater than 1).
9234 @item ^-d^/DISPLAY_PROGRESS^
9235 @cindex @option{^-d^/DISPLAY_PROGRESS^} (@command{gnatmake})
9236 Display progress for each source, up to date or not, as a single line
9239 completed x out of y (zz%)
9242 If the file needs to be compiled this is displayed after the invocation of
9243 the compiler. These lines are displayed even in quiet output mode.
9245 @item ^-D ^/DIRECTORY_OBJECTS=^@var{dir}
9246 @cindex @option{^-D^/DIRECTORY_OBJECTS^} (@command{gnatmake})
9247 Put all object files and ALI file in directory @var{dir}.
9248 If the @option{^-D^/DIRECTORY_OBJECTS^} switch is not used, all object files
9249 and ALI files go in the current working directory.
9251 This switch cannot be used when using a project file.
9255 @cindex @option{-eL} (@command{gnatmake})
9256 Follow all symbolic links when processing project files.
9259 @item ^-eS^/STANDARD_OUTPUT_FOR_COMMANDS^
9260 @cindex @option{^-eS^/STANDARD_OUTPUT_FOR_COMMANDS^} (@command{gnatmake})
9261 Output the commands for the compiler, the binder and the linker
9262 on ^standard output^SYS$OUTPUT^,
9263 instead of ^standard error^SYS$ERROR^.
9265 @item ^-f^/FORCE_COMPILE^
9266 @cindex @option{^-f^/FORCE_COMPILE^} (@command{gnatmake})
9267 Force recompilations. Recompile all sources, even though some object
9268 files may be up to date, but don't recompile predefined or GNAT internal
9269 files or locked files (files with a write-protected ALI file),
9270 unless the @option{^-a^/ALL_FILES^} switch is also specified.
9272 @item ^-F^/FULL_PATH_IN_BRIEF_MESSAGES^
9273 @cindex @option{^-F^/FULL_PATH_IN_BRIEF_MESSAGES^} (@command{gnatmake})
9274 When using project files, if some errors or warnings are detected during
9275 parsing and verbose mode is not in effect (no use of switch
9276 ^-v^/VERBOSE^), then error lines start with the full path name of the project
9277 file, rather than its simple file name.
9280 @cindex @option{^-g^/DEBUG^} (@command{gnatmake})
9281 Enable debugging. This switch is simply passed to the compiler and to the
9284 @item ^-i^/IN_PLACE^
9285 @cindex @option{^-i^/IN_PLACE^} (@command{gnatmake})
9286 In normal mode, @command{gnatmake} compiles all object files and ALI files
9287 into the current directory. If the @option{^-i^/IN_PLACE^} switch is used,
9288 then instead object files and ALI files that already exist are overwritten
9289 in place. This means that once a large project is organized into separate
9290 directories in the desired manner, then @command{gnatmake} will automatically
9291 maintain and update this organization. If no ALI files are found on the
9292 Ada object path (@ref{Search Paths and the Run-Time Library (RTL)}),
9293 the new object and ALI files are created in the
9294 directory containing the source being compiled. If another organization
9295 is desired, where objects and sources are kept in different directories,
9296 a useful technique is to create dummy ALI files in the desired directories.
9297 When detecting such a dummy file, @command{gnatmake} will be forced to
9298 recompile the corresponding source file, and it will be put the resulting
9299 object and ALI files in the directory where it found the dummy file.
9301 @item ^-j^/PROCESSES=^@var{n}
9302 @cindex @option{^-j^/PROCESSES^} (@command{gnatmake})
9303 @cindex Parallel make
9304 Use @var{n} processes to carry out the (re)compilations. On a
9305 multiprocessor machine compilations will occur in parallel. In the
9306 event of compilation errors, messages from various compilations might
9307 get interspersed (but @command{gnatmake} will give you the full ordered
9308 list of failing compiles at the end). If this is problematic, rerun
9309 the make process with n set to 1 to get a clean list of messages.
9311 @item ^-k^/CONTINUE_ON_ERROR^
9312 @cindex @option{^-k^/CONTINUE_ON_ERROR^} (@command{gnatmake})
9313 Keep going. Continue as much as possible after a compilation error. To
9314 ease the programmer's task in case of compilation errors, the list of
9315 sources for which the compile fails is given when @command{gnatmake}
9318 If @command{gnatmake} is invoked with several @file{file_names} and with this
9319 switch, if there are compilation errors when building an executable,
9320 @command{gnatmake} will not attempt to build the following executables.
9322 @item ^-l^/ACTIONS=LINK^
9323 @cindex @option{^-l^/ACTIONS=LINK^} (@command{gnatmake})
9324 Link only. Can be combined with @option{^-b^/ACTIONS=BIND^} to binding
9325 and linking. Linking will not be performed if combined with
9326 @option{^-c^/ACTIONS=COMPILE^}
9327 but not with @option{^-b^/ACTIONS=BIND^}.
9328 When not combined with @option{^-b^/ACTIONS=BIND^}
9329 all the units in the closure of the main program must have been previously
9330 compiled and must be up to date, and the main program needs to have been bound.
9331 The root unit specified by @var{file_name}
9332 may be given without extension, with the source extension or, if no GNAT
9333 Project File is specified, with the ALI file extension.
9335 @item ^-m^/MINIMAL_RECOMPILATION^
9336 @cindex @option{^-m^/MINIMAL_RECOMPILATION^} (@command{gnatmake})
9337 Specify that the minimum necessary amount of recompilations
9338 be performed. In this mode @command{gnatmake} ignores time
9339 stamp differences when the only
9340 modifications to a source file consist in adding/removing comments,
9341 empty lines, spaces or tabs. This means that if you have changed the
9342 comments in a source file or have simply reformatted it, using this
9343 switch will tell @command{gnatmake} not to recompile files that depend on it
9344 (provided other sources on which these files depend have undergone no
9345 semantic modifications). Note that the debugging information may be
9346 out of date with respect to the sources if the @option{-m} switch causes
9347 a compilation to be switched, so the use of this switch represents a
9348 trade-off between compilation time and accurate debugging information.
9350 @item ^-M^/DEPENDENCIES_LIST^
9351 @cindex Dependencies, producing list
9352 @cindex @option{^-M^/DEPENDENCIES_LIST^} (@command{gnatmake})
9353 Check if all objects are up to date. If they are, output the object
9354 dependences to @file{stdout} in a form that can be directly exploited in
9355 a @file{Makefile}. By default, each source file is prefixed with its
9356 (relative or absolute) directory name. This name is whatever you
9357 specified in the various @option{^-aI^/SOURCE_SEARCH^}
9358 and @option{^-I^/SEARCH^} switches. If you use
9359 @code{gnatmake ^-M^/DEPENDENCIES_LIST^}
9360 @option{^-q^/QUIET^}
9361 (see below), only the source file names,
9362 without relative paths, are output. If you just specify the
9363 @option{^-M^/DEPENDENCIES_LIST^}
9364 switch, dependencies of the GNAT internal system files are omitted. This
9365 is typically what you want. If you also specify
9366 the @option{^-a^/ALL_FILES^} switch,
9367 dependencies of the GNAT internal files are also listed. Note that
9368 dependencies of the objects in external Ada libraries (see switch
9369 @option{^-aL^/SKIP_MISSING=^}@var{dir} in the following list)
9372 @item ^-n^/DO_OBJECT_CHECK^
9373 @cindex @option{^-n^/DO_OBJECT_CHECK^} (@command{gnatmake})
9374 Don't compile, bind, or link. Checks if all objects are up to date.
9375 If they are not, the full name of the first file that needs to be
9376 recompiled is printed.
9377 Repeated use of this option, followed by compiling the indicated source
9378 file, will eventually result in recompiling all required units.
9380 @item ^-o ^/EXECUTABLE=^@var{exec_name}
9381 @cindex @option{^-o^/EXECUTABLE^} (@command{gnatmake})
9382 Output executable name. The name of the final executable program will be
9383 @var{exec_name}. If the @option{^-o^/EXECUTABLE^} switch is omitted the default
9384 name for the executable will be the name of the input file in appropriate form
9385 for an executable file on the host system.
9387 This switch cannot be used when invoking @command{gnatmake} with several
9390 @item ^-p or --create-missing-dirs^/CREATE_MISSING_DIRS^
9391 @cindex @option{^-p^/CREATE_MISSING_DIRS^} (@command{gnatmake})
9392 When using project files (^-P^/PROJECT_FILE=^@var{project}), create
9393 automatically missing object directories, library directories and exec
9396 @item ^-P^/PROJECT_FILE=^@var{project}
9397 @cindex @option{^-P^/PROJECT_FILE^} (@command{gnatmake})
9398 Use project file @var{project}. Only one such switch can be used.
9399 @xref{gnatmake and Project Files}.
9402 @cindex @option{^-q^/QUIET^} (@command{gnatmake})
9403 Quiet. When this flag is not set, the commands carried out by
9404 @command{gnatmake} are displayed.
9406 @item ^-s^/SWITCH_CHECK/^
9407 @cindex @option{^-s^/SWITCH_CHECK^} (@command{gnatmake})
9408 Recompile if compiler switches have changed since last compilation.
9409 All compiler switches but -I and -o are taken into account in the
9411 orders between different ``first letter'' switches are ignored, but
9412 orders between same switches are taken into account. For example,
9413 @option{-O -O2} is different than @option{-O2 -O}, but @option{-g -O}
9414 is equivalent to @option{-O -g}.
9416 This switch is recommended when Integrated Preprocessing is used.
9419 @cindex @option{^-u^/UNIQUE^} (@command{gnatmake})
9420 Unique. Recompile at most the main files. It implies -c. Combined with
9421 -f, it is equivalent to calling the compiler directly. Note that using
9422 ^-u^/UNIQUE^ with a project file and no main has a special meaning
9423 (@pxref{Project Files and Main Subprograms}).
9425 @item ^-U^/ALL_PROJECTS^
9426 @cindex @option{^-U^/ALL_PROJECTS^} (@command{gnatmake})
9427 When used without a project file or with one or several mains on the command
9428 line, is equivalent to ^-u^/UNIQUE^. When used with a project file and no main
9429 on the command line, all sources of all project files are checked and compiled
9430 if not up to date, and libraries are rebuilt, if necessary.
9433 @cindex @option{^-v^/REASONS^} (@command{gnatmake})
9434 Verbose. Display the reason for all recompilations @command{gnatmake}
9435 decides are necessary, with the highest verbosity level.
9437 @item ^-vl^/LOW_VERBOSITY^
9438 @cindex @option{^-vl^/LOW_VERBOSITY^} (@command{gnatmake})
9439 Verbosity level Low. Display fewer lines than in verbosity Medium.
9441 @item ^-vm^/MEDIUM_VERBOSITY^
9442 @cindex @option{^-vm^/MEDIUM_VERBOSITY^} (@command{gnatmake})
9443 Verbosity level Medium. Potentially display fewer lines than in verbosity High.
9445 @item ^-vh^/HIGH_VERBOSITY^
9446 @cindex @option{^-vm^/HIGH_VERBOSITY^} (@command{gnatmake})
9447 Verbosity level High. Equivalent to ^-v^/REASONS^.
9449 @item ^-vP^/MESSAGES_PROJECT_FILE=^@emph{x}
9450 Indicate the verbosity of the parsing of GNAT project files.
9451 @xref{Switches Related to Project Files}.
9453 @item ^-x^/NON_PROJECT_UNIT_COMPILATION^
9454 @cindex @option{^-x^/NON_PROJECT_UNIT_COMPILATION^} (@command{gnatmake})
9455 Indicate that sources that are not part of any Project File may be compiled.
9456 Normally, when using Project Files, only sources that are part of a Project
9457 File may be compile. When this switch is used, a source outside of all Project
9458 Files may be compiled. The ALI file and the object file will be put in the
9459 object directory of the main Project. The compilation switches used will only
9460 be those specified on the command line. Even when
9461 @option{^-x^/NON_PROJECT_UNIT_COMPILATION^} is used, mains specified on the
9462 command line need to be sources of a project file.
9464 @item ^-X^/EXTERNAL_REFERENCE=^@var{name=value}
9465 Indicate that external variable @var{name} has the value @var{value}.
9466 The Project Manager will use this value for occurrences of
9467 @code{external(name)} when parsing the project file.
9468 @xref{Switches Related to Project Files}.
9471 @cindex @option{^-z^/NOMAIN^} (@command{gnatmake})
9472 No main subprogram. Bind and link the program even if the unit name
9473 given on the command line is a package name. The resulting executable
9474 will execute the elaboration routines of the package and its closure,
9475 then the finalization routines.
9480 @item @command{gcc} @asis{switches}
9482 Any uppercase or multi-character switch that is not a @command{gnatmake} switch
9483 is passed to @command{gcc} (e.g.@: @option{-O}, @option{-gnato,} etc.)
9486 Any qualifier that cannot be recognized as a qualifier for @code{GNAT MAKE}
9487 but is recognizable as a valid qualifier for @code{GNAT COMPILE} is
9488 automatically treated as a compiler switch, and passed on to all
9489 compilations that are carried out.
9494 Source and library search path switches:
9498 @item ^-aI^/SOURCE_SEARCH=^@var{dir}
9499 @cindex @option{^-aI^/SOURCE_SEARCH^} (@command{gnatmake})
9500 When looking for source files also look in directory @var{dir}.
9501 The order in which source files search is undertaken is
9502 described in @ref{Search Paths and the Run-Time Library (RTL)}.
9504 @item ^-aL^/SKIP_MISSING=^@var{dir}
9505 @cindex @option{^-aL^/SKIP_MISSING^} (@command{gnatmake})
9506 Consider @var{dir} as being an externally provided Ada library.
9507 Instructs @command{gnatmake} to skip compilation units whose @file{.ALI}
9508 files have been located in directory @var{dir}. This allows you to have
9509 missing bodies for the units in @var{dir} and to ignore out of date bodies
9510 for the same units. You still need to specify
9511 the location of the specs for these units by using the switches
9512 @option{^-aI^/SOURCE_SEARCH=^@var{dir}}
9513 or @option{^-I^/SEARCH=^@var{dir}}.
9514 Note: this switch is provided for compatibility with previous versions
9515 of @command{gnatmake}. The easier method of causing standard libraries
9516 to be excluded from consideration is to write-protect the corresponding
9519 @item ^-aO^/OBJECT_SEARCH=^@var{dir}
9520 @cindex @option{^-aO^/OBJECT_SEARCH^} (@command{gnatmake})
9521 When searching for library and object files, look in directory
9522 @var{dir}. The order in which library files are searched is described in
9523 @ref{Search Paths for gnatbind}.
9525 @item ^-A^/CONDITIONAL_SOURCE_SEARCH=^@var{dir}
9526 @cindex Search paths, for @command{gnatmake}
9527 @cindex @option{^-A^/CONDITIONAL_SOURCE_SEARCH^} (@command{gnatmake})
9528 Equivalent to @option{^-aL^/SKIP_MISSING=^@var{dir}
9529 ^-aI^/SOURCE_SEARCH=^@var{dir}}.
9531 @item ^-I^/SEARCH=^@var{dir}
9532 @cindex @option{^-I^/SEARCH^} (@command{gnatmake})
9533 Equivalent to @option{^-aO^/OBJECT_SEARCH=^@var{dir}
9534 ^-aI^/SOURCE_SEARCH=^@var{dir}}.
9536 @item ^-I-^/NOCURRENT_DIRECTORY^
9537 @cindex @option{^-I-^/NOCURRENT_DIRECTORY^} (@command{gnatmake})
9538 @cindex Source files, suppressing search
9539 Do not look for source files in the directory containing the source
9540 file named in the command line.
9541 Do not look for ALI or object files in the directory
9542 where @command{gnatmake} was invoked.
9544 @item ^-L^/LIBRARY_SEARCH=^@var{dir}
9545 @cindex @option{^-L^/LIBRARY_SEARCH^} (@command{gnatmake})
9546 @cindex Linker libraries
9547 Add directory @var{dir} to the list of directories in which the linker
9548 will search for libraries. This is equivalent to
9549 @option{-largs ^-L^/LIBRARY_SEARCH=^}@var{dir}.
9551 Furthermore, under Windows, the sources pointed to by the libraries path
9552 set in the registry are not searched for.
9556 @cindex @option{-nostdinc} (@command{gnatmake})
9557 Do not look for source files in the system default directory.
9560 @cindex @option{-nostdlib} (@command{gnatmake})
9561 Do not look for library files in the system default directory.
9563 @item --RTS=@var{rts-path}
9564 @cindex @option{--RTS} (@command{gnatmake})
9565 Specifies the default location of the runtime library. GNAT looks for the
9567 in the following directories, and stops as soon as a valid runtime is found
9568 (@file{adainclude} or @file{ada_source_path}, and @file{adalib} or
9569 @file{ada_object_path} present):
9572 @item <current directory>/$rts_path
9574 @item <default-search-dir>/$rts_path
9576 @item <default-search-dir>/rts-$rts_path
9580 The selected path is handled like a normal RTS path.
9584 @node Mode Switches for gnatmake
9585 @section Mode Switches for @command{gnatmake}
9588 The mode switches (referred to as @code{mode_switches}) allow the
9589 inclusion of switches that are to be passed to the compiler itself, the
9590 binder or the linker. The effect of a mode switch is to cause all
9591 subsequent switches up to the end of the switch list, or up to the next
9592 mode switch, to be interpreted as switches to be passed on to the
9593 designated component of GNAT.
9597 @item -cargs @var{switches}
9598 @cindex @option{-cargs} (@command{gnatmake})
9599 Compiler switches. Here @var{switches} is a list of switches
9600 that are valid switches for @command{gcc}. They will be passed on to
9601 all compile steps performed by @command{gnatmake}.
9603 @item -bargs @var{switches}
9604 @cindex @option{-bargs} (@command{gnatmake})
9605 Binder switches. Here @var{switches} is a list of switches
9606 that are valid switches for @code{gnatbind}. They will be passed on to
9607 all bind steps performed by @command{gnatmake}.
9609 @item -largs @var{switches}
9610 @cindex @option{-largs} (@command{gnatmake})
9611 Linker switches. Here @var{switches} is a list of switches
9612 that are valid switches for @command{gnatlink}. They will be passed on to
9613 all link steps performed by @command{gnatmake}.
9615 @item -margs @var{switches}
9616 @cindex @option{-margs} (@command{gnatmake})
9617 Make switches. The switches are directly interpreted by @command{gnatmake},
9618 regardless of any previous occurrence of @option{-cargs}, @option{-bargs}
9622 @node Notes on the Command Line
9623 @section Notes on the Command Line
9626 This section contains some additional useful notes on the operation
9627 of the @command{gnatmake} command.
9631 @cindex Recompilation, by @command{gnatmake}
9632 If @command{gnatmake} finds no ALI files, it recompiles the main program
9633 and all other units required by the main program.
9634 This means that @command{gnatmake}
9635 can be used for the initial compile, as well as during subsequent steps of
9636 the development cycle.
9639 If you enter @code{gnatmake @var{file}.adb}, where @file{@var{file}.adb}
9640 is a subunit or body of a generic unit, @command{gnatmake} recompiles
9641 @file{@var{file}.adb} (because it finds no ALI) and stops, issuing a
9645 In @command{gnatmake} the switch @option{^-I^/SEARCH^}
9646 is used to specify both source and
9647 library file paths. Use @option{^-aI^/SOURCE_SEARCH^}
9648 instead if you just want to specify
9649 source paths only and @option{^-aO^/OBJECT_SEARCH^}
9650 if you want to specify library paths
9654 @command{gnatmake} will ignore any files whose ALI file is write-protected.
9655 This may conveniently be used to exclude standard libraries from
9656 consideration and in particular it means that the use of the
9657 @option{^-f^/FORCE_COMPILE^} switch will not recompile these files
9658 unless @option{^-a^/ALL_FILES^} is also specified.
9661 @command{gnatmake} has been designed to make the use of Ada libraries
9662 particularly convenient. Assume you have an Ada library organized
9663 as follows: @i{^obj-dir^[OBJ_DIR]^} contains the objects and ALI files for
9664 of your Ada compilation units,
9665 whereas @i{^include-dir^[INCLUDE_DIR]^} contains the
9666 specs of these units, but no bodies. Then to compile a unit
9667 stored in @code{main.adb}, which uses this Ada library you would just type
9671 $ gnatmake -aI@var{include-dir} -aL@var{obj-dir} main
9674 $ gnatmake /SOURCE_SEARCH=@i{[INCLUDE_DIR]}
9675 /SKIP_MISSING=@i{[OBJ_DIR]} main
9680 Using @command{gnatmake} along with the
9681 @option{^-m (minimal recompilation)^/MINIMAL_RECOMPILATION^}
9682 switch provides a mechanism for avoiding unnecessary recompilations. Using
9684 you can update the comments/format of your
9685 source files without having to recompile everything. Note, however, that
9686 adding or deleting lines in a source files may render its debugging
9687 info obsolete. If the file in question is a spec, the impact is rather
9688 limited, as that debugging info will only be useful during the
9689 elaboration phase of your program. For bodies the impact can be more
9690 significant. In all events, your debugger will warn you if a source file
9691 is more recent than the corresponding object, and alert you to the fact
9692 that the debugging information may be out of date.
9695 @node How gnatmake Works
9696 @section How @command{gnatmake} Works
9699 Generally @command{gnatmake} automatically performs all necessary
9700 recompilations and you don't need to worry about how it works. However,
9701 it may be useful to have some basic understanding of the @command{gnatmake}
9702 approach and in particular to understand how it uses the results of
9703 previous compilations without incorrectly depending on them.
9705 First a definition: an object file is considered @dfn{up to date} if the
9706 corresponding ALI file exists and if all the source files listed in the
9707 dependency section of this ALI file have time stamps matching those in
9708 the ALI file. This means that neither the source file itself nor any
9709 files that it depends on have been modified, and hence there is no need
9710 to recompile this file.
9712 @command{gnatmake} works by first checking if the specified main unit is up
9713 to date. If so, no compilations are required for the main unit. If not,
9714 @command{gnatmake} compiles the main program to build a new ALI file that
9715 reflects the latest sources. Then the ALI file of the main unit is
9716 examined to find all the source files on which the main program depends,
9717 and @command{gnatmake} recursively applies the above procedure on all these
9720 This process ensures that @command{gnatmake} only trusts the dependencies
9721 in an existing ALI file if they are known to be correct. Otherwise it
9722 always recompiles to determine a new, guaranteed accurate set of
9723 dependencies. As a result the program is compiled ``upside down'' from what may
9724 be more familiar as the required order of compilation in some other Ada
9725 systems. In particular, clients are compiled before the units on which
9726 they depend. The ability of GNAT to compile in any order is critical in
9727 allowing an order of compilation to be chosen that guarantees that
9728 @command{gnatmake} will recompute a correct set of new dependencies if
9731 When invoking @command{gnatmake} with several @var{file_names}, if a unit is
9732 imported by several of the executables, it will be recompiled at most once.
9734 Note: when using non-standard naming conventions
9735 (@pxref{Using Other File Names}), changing through a configuration pragmas
9736 file the version of a source and invoking @command{gnatmake} to recompile may
9737 have no effect, if the previous version of the source is still accessible
9738 by @command{gnatmake}. It may be necessary to use the switch
9739 ^-f^/FORCE_COMPILE^.
9741 @node Examples of gnatmake Usage
9742 @section Examples of @command{gnatmake} Usage
9745 @item gnatmake hello.adb
9746 Compile all files necessary to bind and link the main program
9747 @file{hello.adb} (containing unit @code{Hello}) and bind and link the
9748 resulting object files to generate an executable file @file{^hello^HELLO.EXE^}.
9750 @item gnatmake main1 main2 main3
9751 Compile all files necessary to bind and link the main programs
9752 @file{main1.adb} (containing unit @code{Main1}), @file{main2.adb}
9753 (containing unit @code{Main2}) and @file{main3.adb}
9754 (containing unit @code{Main3}) and bind and link the resulting object files
9755 to generate three executable files @file{^main1^MAIN1.EXE^},
9756 @file{^main2^MAIN2.EXE^}
9757 and @file{^main3^MAIN3.EXE^}.
9760 @item gnatmake -q Main_Unit -cargs -O2 -bargs -l
9764 @item gnatmake Main_Unit /QUIET
9765 /COMPILER_QUALIFIERS /OPTIMIZE=ALL
9766 /BINDER_QUALIFIERS /ORDER_OF_ELABORATION
9768 Compile all files necessary to bind and link the main program unit
9769 @code{Main_Unit} (from file @file{main_unit.adb}). All compilations will
9770 be done with optimization level 2 and the order of elaboration will be
9771 listed by the binder. @command{gnatmake} will operate in quiet mode, not
9772 displaying commands it is executing.
9775 @c *************************
9776 @node Improving Performance
9777 @chapter Improving Performance
9778 @cindex Improving performance
9781 This chapter presents several topics related to program performance.
9782 It first describes some of the tradeoffs that need to be considered
9783 and some of the techniques for making your program run faster.
9784 It then documents the @command{gnatelim} tool and unused subprogram/data
9785 elimination feature, which can reduce the size of program executables.
9787 Note: to invoke @command{gnatelim} with a project file, use the @code{gnat}
9788 driver (see @ref{The GNAT Driver and Project Files}).
9792 * Performance Considerations::
9793 * Text_IO Suggestions::
9794 * Reducing Size of Ada Executables with gnatelim::
9795 * Reducing Size of Executables with unused subprogram/data elimination::
9799 @c *****************************
9800 @node Performance Considerations
9801 @section Performance Considerations
9804 The GNAT system provides a number of options that allow a trade-off
9809 performance of the generated code
9812 speed of compilation
9815 minimization of dependences and recompilation
9818 the degree of run-time checking.
9822 The defaults (if no options are selected) aim at improving the speed
9823 of compilation and minimizing dependences, at the expense of performance
9824 of the generated code:
9831 no inlining of subprogram calls
9834 all run-time checks enabled except overflow and elaboration checks
9838 These options are suitable for most program development purposes. This
9839 chapter describes how you can modify these choices, and also provides
9840 some guidelines on debugging optimized code.
9843 * Controlling Run-Time Checks::
9844 * Use of Restrictions::
9845 * Optimization Levels::
9846 * Debugging Optimized Code::
9847 * Inlining of Subprograms::
9848 * Other Optimization Switches::
9849 * Optimization and Strict Aliasing::
9852 * Coverage Analysis::
9856 @node Controlling Run-Time Checks
9857 @subsection Controlling Run-Time Checks
9860 By default, GNAT generates all run-time checks, except integer overflow
9861 checks, stack overflow checks, and checks for access before elaboration on
9862 subprogram calls. The latter are not required in default mode, because all
9863 necessary checking is done at compile time.
9864 @cindex @option{-gnatp} (@command{gcc})
9865 @cindex @option{-gnato} (@command{gcc})
9866 Two gnat switches, @option{-gnatp} and @option{-gnato} allow this default to
9867 be modified. @xref{Run-Time Checks}.
9869 Our experience is that the default is suitable for most development
9872 We treat integer overflow specially because these
9873 are quite expensive and in our experience are not as important as other
9874 run-time checks in the development process. Note that division by zero
9875 is not considered an overflow check, and divide by zero checks are
9876 generated where required by default.
9878 Elaboration checks are off by default, and also not needed by default, since
9879 GNAT uses a static elaboration analysis approach that avoids the need for
9880 run-time checking. This manual contains a full chapter discussing the issue
9881 of elaboration checks, and if the default is not satisfactory for your use,
9882 you should read this chapter.
9884 For validity checks, the minimal checks required by the Ada Reference
9885 Manual (for case statements and assignments to array elements) are on
9886 by default. These can be suppressed by use of the @option{-gnatVn} switch.
9887 Note that in Ada 83, there were no validity checks, so if the Ada 83 mode
9888 is acceptable (or when comparing GNAT performance with an Ada 83 compiler),
9889 it may be reasonable to routinely use @option{-gnatVn}. Validity checks
9890 are also suppressed entirely if @option{-gnatp} is used.
9892 @cindex Overflow checks
9893 @cindex Checks, overflow
9896 @cindex pragma Suppress
9897 @cindex pragma Unsuppress
9898 Note that the setting of the switches controls the default setting of
9899 the checks. They may be modified using either @code{pragma Suppress} (to
9900 remove checks) or @code{pragma Unsuppress} (to add back suppressed
9901 checks) in the program source.
9903 @node Use of Restrictions
9904 @subsection Use of Restrictions
9907 The use of pragma Restrictions allows you to control which features are
9908 permitted in your program. Apart from the obvious point that if you avoid
9909 relatively expensive features like finalization (enforceable by the use
9910 of pragma Restrictions (No_Finalization), the use of this pragma does not
9911 affect the generated code in most cases.
9913 One notable exception to this rule is that the possibility of task abort
9914 results in some distributed overhead, particularly if finalization or
9915 exception handlers are used. The reason is that certain sections of code
9916 have to be marked as non-abortable.
9918 If you use neither the @code{abort} statement, nor asynchronous transfer
9919 of control (@code{select @dots{} then abort}), then this distributed overhead
9920 is removed, which may have a general positive effect in improving
9921 overall performance. Especially code involving frequent use of tasking
9922 constructs and controlled types will show much improved performance.
9923 The relevant restrictions pragmas are
9925 @smallexample @c ada
9926 pragma Restrictions (No_Abort_Statements);
9927 pragma Restrictions (Max_Asynchronous_Select_Nesting => 0);
9931 It is recommended that these restriction pragmas be used if possible. Note
9932 that this also means that you can write code without worrying about the
9933 possibility of an immediate abort at any point.
9935 @node Optimization Levels
9936 @subsection Optimization Levels
9937 @cindex @option{^-O^/OPTIMIZE^} (@command{gcc})
9940 Without any optimization ^option,^qualifier,^
9941 the compiler's goal is to reduce the cost of
9942 compilation and to make debugging produce the expected results.
9943 Statements are independent: if you stop the program with a breakpoint between
9944 statements, you can then assign a new value to any variable or change
9945 the program counter to any other statement in the subprogram and get exactly
9946 the results you would expect from the source code.
9948 Turning on optimization makes the compiler attempt to improve the
9949 performance and/or code size at the expense of compilation time and
9950 possibly the ability to debug the program.
9953 ^-O options, with or without level numbers,^/OPTIMIZE qualifiers,^
9954 the last such option is the one that is effective.
9957 The default is optimization off. This results in the fastest compile
9958 times, but GNAT makes absolutely no attempt to optimize, and the
9959 generated programs are considerably larger and slower than when
9960 optimization is enabled. You can use the
9962 @option{-O} switch (the permitted forms are @option{-O0}, @option{-O1}
9963 @option{-O2}, @option{-O3}, and @option{-Os})
9966 @code{OPTIMIZE} qualifier
9968 to @command{gcc} to control the optimization level:
9971 @item ^-O0^/OPTIMIZE=NONE^
9972 No optimization (the default);
9973 generates unoptimized code but has
9974 the fastest compilation time.
9976 Note that many other compilers do fairly extensive optimization
9977 even if ``no optimization'' is specified. With gcc, it is
9978 very unusual to use ^-O0^/OPTIMIZE=NONE^ for production if
9979 execution time is of any concern, since ^-O0^/OPTIMIZE=NONE^
9980 really does mean no optimization at all. This difference between
9981 gcc and other compilers should be kept in mind when doing
9982 performance comparisons.
9984 @item ^-O1^/OPTIMIZE=SOME^
9985 Moderate optimization;
9986 optimizes reasonably well but does not
9987 degrade compilation time significantly.
9989 @item ^-O2^/OPTIMIZE=ALL^
9991 @itemx /OPTIMIZE=DEVELOPMENT
9994 generates highly optimized code and has
9995 the slowest compilation time.
9997 @item ^-O3^/OPTIMIZE=INLINING^
9998 Full optimization as in @option{-O2},
9999 and also attempts automatic inlining of small
10000 subprograms within a unit (@pxref{Inlining of Subprograms}).
10002 @item ^-Os^/OPTIMIZE=SPACE^
10003 Optimize space usage of resulting program.
10007 Higher optimization levels perform more global transformations on the
10008 program and apply more expensive analysis algorithms in order to generate
10009 faster and more compact code. The price in compilation time, and the
10010 resulting improvement in execution time,
10011 both depend on the particular application and the hardware environment.
10012 You should experiment to find the best level for your application.
10014 Since the precise set of optimizations done at each level will vary from
10015 release to release (and sometime from target to target), it is best to think
10016 of the optimization settings in general terms.
10017 @xref{Optimize Options,, Options That Control Optimization, gcc, Using
10018 the GNU Compiler Collection (GCC)}, for details about
10019 ^the @option{-O} settings and a number of @option{-f} options that^how to^
10020 individually enable or disable specific optimizations.
10022 Unlike some other compilation systems, ^@command{gcc}^GNAT^ has
10023 been tested extensively at all optimization levels. There are some bugs
10024 which appear only with optimization turned on, but there have also been
10025 bugs which show up only in @emph{unoptimized} code. Selecting a lower
10026 level of optimization does not improve the reliability of the code
10027 generator, which in practice is highly reliable at all optimization
10030 Note regarding the use of @option{-O3}: The use of this optimization level
10031 is generally discouraged with GNAT, since it often results in larger
10032 executables which run more slowly. See further discussion of this point
10033 in @ref{Inlining of Subprograms}.
10035 @node Debugging Optimized Code
10036 @subsection Debugging Optimized Code
10037 @cindex Debugging optimized code
10038 @cindex Optimization and debugging
10041 Although it is possible to do a reasonable amount of debugging at
10043 nonzero optimization levels,
10044 the higher the level the more likely that
10047 @option{/OPTIMIZE} settings other than @code{NONE},
10048 such settings will make it more likely that
10050 source-level constructs will have been eliminated by optimization.
10051 For example, if a loop is strength-reduced, the loop
10052 control variable may be completely eliminated and thus cannot be
10053 displayed in the debugger.
10054 This can only happen at @option{-O2} or @option{-O3}.
10055 Explicit temporary variables that you code might be eliminated at
10056 ^level^setting^ @option{-O1} or higher.
10058 The use of the @option{^-g^/DEBUG^} switch,
10059 @cindex @option{^-g^/DEBUG^} (@command{gcc})
10060 which is needed for source-level debugging,
10061 affects the size of the program executable on disk,
10062 and indeed the debugging information can be quite large.
10063 However, it has no effect on the generated code (and thus does not
10064 degrade performance)
10066 Since the compiler generates debugging tables for a compilation unit before
10067 it performs optimizations, the optimizing transformations may invalidate some
10068 of the debugging data. You therefore need to anticipate certain
10069 anomalous situations that may arise while debugging optimized code.
10070 These are the most common cases:
10074 @i{The ``hopping Program Counter'':} Repeated @code{step} or @code{next}
10076 the PC bouncing back and forth in the code. This may result from any of
10077 the following optimizations:
10081 @i{Common subexpression elimination:} using a single instance of code for a
10082 quantity that the source computes several times. As a result you
10083 may not be able to stop on what looks like a statement.
10086 @i{Invariant code motion:} moving an expression that does not change within a
10087 loop, to the beginning of the loop.
10090 @i{Instruction scheduling:} moving instructions so as to
10091 overlap loads and stores (typically) with other code, or in
10092 general to move computations of values closer to their uses. Often
10093 this causes you to pass an assignment statement without the assignment
10094 happening and then later bounce back to the statement when the
10095 value is actually needed. Placing a breakpoint on a line of code
10096 and then stepping over it may, therefore, not always cause all the
10097 expected side-effects.
10101 @i{The ``big leap'':} More commonly known as @emph{cross-jumping}, in which
10102 two identical pieces of code are merged and the program counter suddenly
10103 jumps to a statement that is not supposed to be executed, simply because
10104 it (and the code following) translates to the same thing as the code
10105 that @emph{was} supposed to be executed. This effect is typically seen in
10106 sequences that end in a jump, such as a @code{goto}, a @code{return}, or
10107 a @code{break} in a C @code{^switch^switch^} statement.
10110 @i{The ``roving variable'':} The symptom is an unexpected value in a variable.
10111 There are various reasons for this effect:
10115 In a subprogram prologue, a parameter may not yet have been moved to its
10119 A variable may be dead, and its register re-used. This is
10120 probably the most common cause.
10123 As mentioned above, the assignment of a value to a variable may
10127 A variable may be eliminated entirely by value propagation or
10128 other means. In this case, GCC may incorrectly generate debugging
10129 information for the variable
10133 In general, when an unexpected value appears for a local variable or parameter
10134 you should first ascertain if that value was actually computed by
10135 your program, as opposed to being incorrectly reported by the debugger.
10137 array elements in an object designated by an access value
10138 are generally less of a problem, once you have ascertained that the access
10140 Typically, this means checking variables in the preceding code and in the
10141 calling subprogram to verify that the value observed is explainable from other
10142 values (one must apply the procedure recursively to those
10143 other values); or re-running the code and stopping a little earlier
10144 (perhaps before the call) and stepping to better see how the variable obtained
10145 the value in question; or continuing to step @emph{from} the point of the
10146 strange value to see if code motion had simply moved the variable's
10151 In light of such anomalies, a recommended technique is to use @option{-O0}
10152 early in the software development cycle, when extensive debugging capabilities
10153 are most needed, and then move to @option{-O1} and later @option{-O2} as
10154 the debugger becomes less critical.
10155 Whether to use the @option{^-g^/DEBUG^} switch in the release version is
10156 a release management issue.
10158 Note that if you use @option{-g} you can then use the @command{strip} program
10159 on the resulting executable,
10160 which removes both debugging information and global symbols.
10163 @node Inlining of Subprograms
10164 @subsection Inlining of Subprograms
10167 A call to a subprogram in the current unit is inlined if all the
10168 following conditions are met:
10172 The optimization level is at least @option{-O1}.
10175 The called subprogram is suitable for inlining: It must be small enough
10176 and not contain something that @command{gcc} cannot support in inlined
10180 @cindex pragma Inline
10182 Either @code{pragma Inline} applies to the subprogram, or it is local
10183 to the unit and called once from within it, or it is small and automatic
10184 inlining (optimization level @option{-O3}) is specified.
10188 Calls to subprograms in @code{with}'ed units are normally not inlined.
10189 To achieve actual inlining (that is, replacement of the call by the code
10190 in the body of the subprogram), the following conditions must all be true.
10194 The optimization level is at least @option{-O1}.
10197 The called subprogram is suitable for inlining: It must be small enough
10198 and not contain something that @command{gcc} cannot support in inlined
10202 The call appears in a body (not in a package spec).
10205 There is a @code{pragma Inline} for the subprogram.
10208 @cindex @option{-gnatn} (@command{gcc})
10209 The @option{^-gnatn^/INLINE^} switch
10210 is used in the @command{gcc} command line
10213 Even if all these conditions are met, it may not be possible for
10214 the compiler to inline the call, due to the length of the body,
10215 or features in the body that make it impossible for the compiler
10216 to do the inlining.
10218 Note that specifying the @option{-gnatn} switch causes additional
10219 compilation dependencies. Consider the following:
10221 @smallexample @c ada
10241 With the default behavior (no @option{-gnatn} switch specified), the
10242 compilation of the @code{Main} procedure depends only on its own source,
10243 @file{main.adb}, and the spec of the package in file @file{r.ads}. This
10244 means that editing the body of @code{R} does not require recompiling
10247 On the other hand, the call @code{R.Q} is not inlined under these
10248 circumstances. If the @option{-gnatn} switch is present when @code{Main}
10249 is compiled, the call will be inlined if the body of @code{Q} is small
10250 enough, but now @code{Main} depends on the body of @code{R} in
10251 @file{r.adb} as well as on the spec. This means that if this body is edited,
10252 the main program must be recompiled. Note that this extra dependency
10253 occurs whether or not the call is in fact inlined by @command{gcc}.
10255 The use of front end inlining with @option{-gnatN} generates similar
10256 additional dependencies.
10258 @cindex @option{^-fno-inline^/INLINE=SUPPRESS^} (@command{gcc})
10259 Note: The @option{^-fno-inline^/INLINE=SUPPRESS^} switch
10260 can be used to prevent
10261 all inlining. This switch overrides all other conditions and ensures
10262 that no inlining occurs. The extra dependences resulting from
10263 @option{-gnatn} will still be active, even if
10264 this switch is used to suppress the resulting inlining actions.
10266 @cindex @option{-fno-inline-functions} (@command{gcc})
10267 Note: The @option{-fno-inline-functions} switch can be used to prevent
10268 automatic inlining of small subprograms if @option{-O3} is used.
10270 @cindex @option{-fno-inline-functions-called-once} (@command{gcc})
10271 Note: The @option{-fno-inline-functions-called-once} switch
10272 can be used to prevent inlining of subprograms local to the unit
10273 and called once from within it if @option{-O1} is used.
10275 Note regarding the use of @option{-O3}: There is no difference in inlining
10276 behavior between @option{-O2} and @option{-O3} for subprograms with an explicit
10277 pragma @code{Inline} assuming the use of @option{-gnatn}
10278 or @option{-gnatN} (the switches that activate inlining). If you have used
10279 pragma @code{Inline} in appropriate cases, then it is usually much better
10280 to use @option{-O2} and @option{-gnatn} and avoid the use of @option{-O3} which
10281 in this case only has the effect of inlining subprograms you did not
10282 think should be inlined. We often find that the use of @option{-O3} slows
10283 down code by performing excessive inlining, leading to increased instruction
10284 cache pressure from the increased code size. So the bottom line here is
10285 that you should not automatically assume that @option{-O3} is better than
10286 @option{-O2}, and indeed you should use @option{-O3} only if tests show that
10287 it actually improves performance.
10289 @node Other Optimization Switches
10290 @subsection Other Optimization Switches
10291 @cindex Optimization Switches
10293 Since @code{GNAT} uses the @command{gcc} back end, all the specialized
10294 @command{gcc} optimization switches are potentially usable. These switches
10295 have not been extensively tested with GNAT but can generally be expected
10296 to work. Examples of switches in this category are
10297 @option{-funroll-loops} and
10298 the various target-specific @option{-m} options (in particular, it has been
10299 observed that @option{-march=pentium4} can significantly improve performance
10300 on appropriate machines). For full details of these switches, see
10301 @ref{Submodel Options,, Hardware Models and Configurations, gcc, Using
10302 the GNU Compiler Collection (GCC)}.
10304 @node Optimization and Strict Aliasing
10305 @subsection Optimization and Strict Aliasing
10307 @cindex Strict Aliasing
10308 @cindex No_Strict_Aliasing
10311 The strong typing capabilities of Ada allow an optimizer to generate
10312 efficient code in situations where other languages would be forced to
10313 make worst case assumptions preventing such optimizations. Consider
10314 the following example:
10316 @smallexample @c ada
10319 type Int1 is new Integer;
10320 type Int2 is new Integer;
10321 type Int1A is access Int1;
10322 type Int2A is access Int2;
10329 for J in Data'Range loop
10330 if Data (J) = Int1V.all then
10331 Int2V.all := Int2V.all + 1;
10340 In this example, since the variable @code{Int1V} can only access objects
10341 of type @code{Int1}, and @code{Int2V} can only access objects of type
10342 @code{Int2}, there is no possibility that the assignment to
10343 @code{Int2V.all} affects the value of @code{Int1V.all}. This means that
10344 the compiler optimizer can "know" that the value @code{Int1V.all} is constant
10345 for all iterations of the loop and avoid the extra memory reference
10346 required to dereference it each time through the loop.
10348 This kind of optimization, called strict aliasing analysis, is
10349 triggered by specifying an optimization level of @option{-O2} or
10350 higher or @option{-Os} and allows @code{GNAT} to generate more efficient code
10351 when access values are involved.
10353 However, although this optimization is always correct in terms of
10354 the formal semantics of the Ada Reference Manual, difficulties can
10355 arise if features like @code{Unchecked_Conversion} are used to break
10356 the typing system. Consider the following complete program example:
10358 @smallexample @c ada
10361 type int1 is new integer;
10362 type int2 is new integer;
10363 type a1 is access int1;
10364 type a2 is access int2;
10369 function to_a2 (Input : a1) return a2;
10372 with Unchecked_Conversion;
10374 function to_a2 (Input : a1) return a2 is
10376 new Unchecked_Conversion (a1, a2);
10378 return to_a2u (Input);
10384 with Text_IO; use Text_IO;
10386 v1 : a1 := new int1;
10387 v2 : a2 := to_a2 (v1);
10391 put_line (int1'image (v1.all));
10397 This program prints out 0 in @option{-O0} or @option{-O1}
10398 mode, but it prints out 1 in @option{-O2} mode. That's
10399 because in strict aliasing mode, the compiler can and
10400 does assume that the assignment to @code{v2.all} could not
10401 affect the value of @code{v1.all}, since different types
10404 This behavior is not a case of non-conformance with the standard, since
10405 the Ada RM specifies that an unchecked conversion where the resulting
10406 bit pattern is not a correct value of the target type can result in an
10407 abnormal value and attempting to reference an abnormal value makes the
10408 execution of a program erroneous. That's the case here since the result
10409 does not point to an object of type @code{int2}. This means that the
10410 effect is entirely unpredictable.
10412 However, although that explanation may satisfy a language
10413 lawyer, in practice an applications programmer expects an
10414 unchecked conversion involving pointers to create true
10415 aliases and the behavior of printing 1 seems plain wrong.
10416 In this case, the strict aliasing optimization is unwelcome.
10418 Indeed the compiler recognizes this possibility, and the
10419 unchecked conversion generates a warning:
10422 p2.adb:5:07: warning: possible aliasing problem with type "a2"
10423 p2.adb:5:07: warning: use -fno-strict-aliasing switch for references
10424 p2.adb:5:07: warning: or use "pragma No_Strict_Aliasing (a2);"
10428 Unfortunately the problem is recognized when compiling the body of
10429 package @code{p2}, but the actual "bad" code is generated while
10430 compiling the body of @code{m} and this latter compilation does not see
10431 the suspicious @code{Unchecked_Conversion}.
10433 As implied by the warning message, there are approaches you can use to
10434 avoid the unwanted strict aliasing optimization in a case like this.
10436 One possibility is to simply avoid the use of @option{-O2}, but
10437 that is a bit drastic, since it throws away a number of useful
10438 optimizations that do not involve strict aliasing assumptions.
10440 A less drastic approach is to compile the program using the
10441 option @option{-fno-strict-aliasing}. Actually it is only the
10442 unit containing the dereferencing of the suspicious pointer
10443 that needs to be compiled. So in this case, if we compile
10444 unit @code{m} with this switch, then we get the expected
10445 value of zero printed. Analyzing which units might need
10446 the switch can be painful, so a more reasonable approach
10447 is to compile the entire program with options @option{-O2}
10448 and @option{-fno-strict-aliasing}. If the performance is
10449 satisfactory with this combination of options, then the
10450 advantage is that the entire issue of possible "wrong"
10451 optimization due to strict aliasing is avoided.
10453 To avoid the use of compiler switches, the configuration
10454 pragma @code{No_Strict_Aliasing} with no parameters may be
10455 used to specify that for all access types, the strict
10456 aliasing optimization should be suppressed.
10458 However, these approaches are still overkill, in that they causes
10459 all manipulations of all access values to be deoptimized. A more
10460 refined approach is to concentrate attention on the specific
10461 access type identified as problematic.
10463 First, if a careful analysis of uses of the pointer shows
10464 that there are no possible problematic references, then
10465 the warning can be suppressed by bracketing the
10466 instantiation of @code{Unchecked_Conversion} to turn
10469 @smallexample @c ada
10470 pragma Warnings (Off);
10472 new Unchecked_Conversion (a1, a2);
10473 pragma Warnings (On);
10477 Of course that approach is not appropriate for this particular
10478 example, since indeed there is a problematic reference. In this
10479 case we can take one of two other approaches.
10481 The first possibility is to move the instantiation of unchecked
10482 conversion to the unit in which the type is declared. In
10483 this example, we would move the instantiation of
10484 @code{Unchecked_Conversion} from the body of package
10485 @code{p2} to the spec of package @code{p1}. Now the
10486 warning disappears. That's because any use of the
10487 access type knows there is a suspicious unchecked
10488 conversion, and the strict aliasing optimization
10489 is automatically suppressed for the type.
10491 If it is not practical to move the unchecked conversion to the same unit
10492 in which the destination access type is declared (perhaps because the
10493 source type is not visible in that unit), you may use pragma
10494 @code{No_Strict_Aliasing} for the type. This pragma must occur in the
10495 same declarative sequence as the declaration of the access type:
10497 @smallexample @c ada
10498 type a2 is access int2;
10499 pragma No_Strict_Aliasing (a2);
10503 Here again, the compiler now knows that the strict aliasing optimization
10504 should be suppressed for any reference to type @code{a2} and the
10505 expected behavior is obtained.
10507 Finally, note that although the compiler can generate warnings for
10508 simple cases of unchecked conversions, there are tricker and more
10509 indirect ways of creating type incorrect aliases which the compiler
10510 cannot detect. Examples are the use of address overlays and unchecked
10511 conversions involving composite types containing access types as
10512 components. In such cases, no warnings are generated, but there can
10513 still be aliasing problems. One safe coding practice is to forbid the
10514 use of address clauses for type overlaying, and to allow unchecked
10515 conversion only for primitive types. This is not really a significant
10516 restriction since any possible desired effect can be achieved by
10517 unchecked conversion of access values.
10519 The aliasing analysis done in strict aliasing mode can certainly
10520 have significant benefits. We have seen cases of large scale
10521 application code where the time is increased by up to 5% by turning
10522 this optimization off. If you have code that includes significant
10523 usage of unchecked conversion, you might want to just stick with
10524 @option{-O1} and avoid the entire issue. If you get adequate
10525 performance at this level of optimization level, that's probably
10526 the safest approach. If tests show that you really need higher
10527 levels of optimization, then you can experiment with @option{-O2}
10528 and @option{-O2 -fno-strict-aliasing} to see how much effect this
10529 has on size and speed of the code. If you really need to use
10530 @option{-O2} with strict aliasing in effect, then you should
10531 review any uses of unchecked conversion of access types,
10532 particularly if you are getting the warnings described above.
10535 @node Coverage Analysis
10536 @subsection Coverage Analysis
10539 GNAT supports the HP Performance Coverage Analyzer (PCA), which allows
10540 the user to determine the distribution of execution time across a program,
10541 @pxref{Profiling} for details of usage.
10545 @node Text_IO Suggestions
10546 @section @code{Text_IO} Suggestions
10547 @cindex @code{Text_IO} and performance
10550 The @code{Ada.Text_IO} package has fairly high overheads due in part to
10551 the requirement of maintaining page and line counts. If performance
10552 is critical, a recommendation is to use @code{Stream_IO} instead of
10553 @code{Text_IO} for volume output, since this package has less overhead.
10555 If @code{Text_IO} must be used, note that by default output to the standard
10556 output and standard error files is unbuffered (this provides better
10557 behavior when output statements are used for debugging, or if the
10558 progress of a program is observed by tracking the output, e.g. by
10559 using the Unix @command{tail -f} command to watch redirected output.
10561 If you are generating large volumes of output with @code{Text_IO} and
10562 performance is an important factor, use a designated file instead
10563 of the standard output file, or change the standard output file to
10564 be buffered using @code{Interfaces.C_Streams.setvbuf}.
10568 @node Reducing Size of Ada Executables with gnatelim
10569 @section Reducing Size of Ada Executables with @code{gnatelim}
10573 This section describes @command{gnatelim}, a tool which detects unused
10574 subprograms and helps the compiler to create a smaller executable for your
10579 * Running gnatelim::
10580 * Correcting the List of Eliminate Pragmas::
10581 * Making Your Executables Smaller::
10582 * Summary of the gnatelim Usage Cycle::
10585 @node About gnatelim
10586 @subsection About @code{gnatelim}
10589 When a program shares a set of Ada
10590 packages with other programs, it may happen that this program uses
10591 only a fraction of the subprograms defined in these packages. The code
10592 created for these unused subprograms increases the size of the executable.
10594 @code{gnatelim} tracks unused subprograms in an Ada program and
10595 outputs a list of GNAT-specific pragmas @code{Eliminate} marking all the
10596 subprograms that are declared but never called. By placing the list of
10597 @code{Eliminate} pragmas in the GNAT configuration file @file{gnat.adc} and
10598 recompiling your program, you may decrease the size of its executable,
10599 because the compiler will not generate the code for 'eliminated' subprograms.
10600 @xref{Pragma Eliminate,,, gnat_rm, GNAT Reference Manual}, for more
10601 information about this pragma.
10603 @code{gnatelim} needs as its input data the name of the main subprogram
10604 and a bind file for a main subprogram.
10606 To create a bind file for @code{gnatelim}, run @code{gnatbind} for
10607 the main subprogram. @code{gnatelim} can work with both Ada and C
10608 bind files; when both are present, it uses the Ada bind file.
10609 The following commands will build the program and create the bind file:
10612 $ gnatmake ^-c Main_Prog^/ACTIONS=COMPILE MAIN_PROG^
10613 $ gnatbind main_prog
10616 Note that @code{gnatelim} needs neither object nor ALI files.
10618 @node Running gnatelim
10619 @subsection Running @code{gnatelim}
10622 @code{gnatelim} has the following command-line interface:
10625 $ gnatelim @ovar{options} name
10629 @code{name} should be a name of a source file that contains the main subprogram
10630 of a program (partition).
10632 @code{gnatelim} has the following switches:
10637 @cindex @option{^-q^/QUIET^} (@command{gnatelim})
10638 Quiet mode: by default @code{gnatelim} outputs to the standard error
10639 stream the number of program units left to be processed. This option turns
10642 @item ^-v^/VERBOSE^
10643 @cindex @option{^-v^/VERBOSE^} (@command{gnatelim})
10644 Verbose mode: @code{gnatelim} version information is printed as Ada
10645 comments to the standard output stream. Also, in addition to the number of
10646 program units left @code{gnatelim} will output the name of the current unit
10650 @cindex @option{^-a^/ALL^} (@command{gnatelim})
10651 Also look for subprograms from the GNAT run time that can be eliminated. Note
10652 that when @file{gnat.adc} is produced using this switch, the entire program
10653 must be recompiled with switch @option{^-a^/ALL_FILES^} to @command{gnatmake}.
10655 @item ^-I^/INCLUDE_DIRS=^@var{dir}
10656 @cindex @option{^-I^/INCLUDE_DIRS^} (@command{gnatelim})
10657 When looking for source files also look in directory @var{dir}. Specifying
10658 @option{^-I-^/INCLUDE_DIRS=-^} instructs @code{gnatelim} not to look for
10659 sources in the current directory.
10661 @item ^-b^/BIND_FILE=^@var{bind_file}
10662 @cindex @option{^-b^/BIND_FILE^} (@command{gnatelim})
10663 Specifies @var{bind_file} as the bind file to process. If not set, the name
10664 of the bind file is computed from the full expanded Ada name
10665 of a main subprogram.
10667 @item ^-C^/CONFIG_FILE=^@var{config_file}
10668 @cindex @option{^-C^/CONFIG_FILE^} (@command{gnatelim})
10669 Specifies a file @var{config_file} that contains configuration pragmas. The
10670 file must be specified with full path.
10672 @item ^--GCC^/COMPILER^=@var{compiler_name}
10673 @cindex @option{^-GCC^/COMPILER^} (@command{gnatelim})
10674 Instructs @code{gnatelim} to use specific @command{gcc} compiler instead of one
10675 available on the path.
10677 @item ^--GNATMAKE^/GNATMAKE^=@var{gnatmake_name}
10678 @cindex @option{^--GNATMAKE^/GNATMAKE^} (@command{gnatelim})
10679 Instructs @code{gnatelim} to use specific @command{gnatmake} instead of one
10680 available on the path.
10684 @code{gnatelim} sends its output to the standard output stream, and all the
10685 tracing and debug information is sent to the standard error stream.
10686 In order to produce a proper GNAT configuration file
10687 @file{gnat.adc}, redirection must be used:
10691 $ PIPE GNAT ELIM MAIN_PROG.ADB > GNAT.ADC
10694 $ gnatelim main_prog.adb > gnat.adc
10703 $ gnatelim main_prog.adb >> gnat.adc
10707 in order to append the @code{gnatelim} output to the existing contents of
10711 @node Correcting the List of Eliminate Pragmas
10712 @subsection Correcting the List of Eliminate Pragmas
10715 In some rare cases @code{gnatelim} may try to eliminate
10716 subprograms that are actually called in the program. In this case, the
10717 compiler will generate an error message of the form:
10720 file.adb:106:07: cannot call eliminated subprogram "My_Prog"
10724 You will need to manually remove the wrong @code{Eliminate} pragmas from
10725 the @file{gnat.adc} file. You should recompile your program
10726 from scratch after that, because you need a consistent @file{gnat.adc} file
10727 during the entire compilation.
10729 @node Making Your Executables Smaller
10730 @subsection Making Your Executables Smaller
10733 In order to get a smaller executable for your program you now have to
10734 recompile the program completely with the new @file{gnat.adc} file
10735 created by @code{gnatelim} in your current directory:
10738 $ gnatmake ^-f main_prog^/FORCE_COMPILE MAIN_PROG^
10742 (Use the @option{^-f^/FORCE_COMPILE^} option for @command{gnatmake} to
10743 recompile everything
10744 with the set of pragmas @code{Eliminate} that you have obtained with
10745 @command{gnatelim}).
10747 Be aware that the set of @code{Eliminate} pragmas is specific to each
10748 program. It is not recommended to merge sets of @code{Eliminate}
10749 pragmas created for different programs in one @file{gnat.adc} file.
10751 @node Summary of the gnatelim Usage Cycle
10752 @subsection Summary of the gnatelim Usage Cycle
10755 Here is a quick summary of the steps to be taken in order to reduce
10756 the size of your executables with @code{gnatelim}. You may use
10757 other GNAT options to control the optimization level,
10758 to produce the debugging information, to set search path, etc.
10762 Produce a bind file
10765 $ gnatmake ^-c main_prog^/ACTIONS=COMPILE MAIN_PROG^
10766 $ gnatbind main_prog
10770 Generate a list of @code{Eliminate} pragmas
10773 $ PIPE GNAT ELIM MAIN_PROG > GNAT.ADC
10776 $ gnatelim main_prog >@r{[}>@r{]} gnat.adc
10781 Recompile the application
10784 $ gnatmake ^-f main_prog^/FORCE_COMPILE MAIN_PROG^
10789 @node Reducing Size of Executables with unused subprogram/data elimination
10790 @section Reducing Size of Executables with Unused Subprogram/Data Elimination
10791 @findex unused subprogram/data elimination
10794 This section describes how you can eliminate unused subprograms and data from
10795 your executable just by setting options at compilation time.
10798 * About unused subprogram/data elimination::
10799 * Compilation options::
10800 * Example of unused subprogram/data elimination::
10803 @node About unused subprogram/data elimination
10804 @subsection About unused subprogram/data elimination
10807 By default, an executable contains all code and data of its composing objects
10808 (directly linked or coming from statically linked libraries), even data or code
10809 never used by this executable.
10811 This feature will allow you to eliminate such unused code from your
10812 executable, making it smaller (in disk and in memory).
10814 This functionality is available on all Linux platforms except for the IA-64
10815 architecture and on all cross platforms using the ELF binary file format.
10816 In both cases GNU binutils version 2.16 or later are required to enable it.
10818 @node Compilation options
10819 @subsection Compilation options
10822 The operation of eliminating the unused code and data from the final executable
10823 is directly performed by the linker.
10825 In order to do this, it has to work with objects compiled with the
10827 @option{-ffunction-sections} @option{-fdata-sections}.
10828 @cindex @option{-ffunction-sections} (@command{gcc})
10829 @cindex @option{-fdata-sections} (@command{gcc})
10830 These options are usable with C and Ada files.
10831 They will place respectively each
10832 function or data in a separate section in the resulting object file.
10834 Once the objects and static libraries are created with these options, the
10835 linker can perform the dead code elimination. You can do this by setting
10836 the @option{-Wl,--gc-sections} option to gcc command or in the
10837 @option{-largs} section of @command{gnatmake}. This will perform a
10838 garbage collection of code and data never referenced.
10840 If the linker performs a partial link (@option{-r} ld linker option), then you
10841 will need to provide one or several entry point using the
10842 @option{-e} / @option{--entry} ld option.
10844 Note that objects compiled without the @option{-ffunction-sections} and
10845 @option{-fdata-sections} options can still be linked with the executable.
10846 However, no dead code elimination will be performed on those objects (they will
10849 The GNAT static library is now compiled with -ffunction-sections and
10850 -fdata-sections on some platforms. This allows you to eliminate the unused code
10851 and data of the GNAT library from your executable.
10853 @node Example of unused subprogram/data elimination
10854 @subsection Example of unused subprogram/data elimination
10857 Here is a simple example:
10859 @smallexample @c ada
10868 Used_Data : Integer;
10869 Unused_Data : Integer;
10871 procedure Used (Data : Integer);
10872 procedure Unused (Data : Integer);
10875 package body Aux is
10876 procedure Used (Data : Integer) is
10881 procedure Unused (Data : Integer) is
10883 Unused_Data := Data;
10889 @code{Unused} and @code{Unused_Data} are never referenced in this code
10890 excerpt, and hence they may be safely removed from the final executable.
10895 $ nm test | grep used
10896 020015f0 T aux__unused
10897 02005d88 B aux__unused_data
10898 020015cc T aux__used
10899 02005d84 B aux__used_data
10901 $ gnatmake test -cargs -fdata-sections -ffunction-sections \
10902 -largs -Wl,--gc-sections
10904 $ nm test | grep used
10905 02005350 T aux__used
10906 0201ffe0 B aux__used_data
10910 It can be observed that the procedure @code{Unused} and the object
10911 @code{Unused_Data} are removed by the linker when using the
10912 appropriate options.
10914 @c ********************************
10915 @node Renaming Files Using gnatchop
10916 @chapter Renaming Files Using @code{gnatchop}
10920 This chapter discusses how to handle files with multiple units by using
10921 the @code{gnatchop} utility. This utility is also useful in renaming
10922 files to meet the standard GNAT default file naming conventions.
10925 * Handling Files with Multiple Units::
10926 * Operating gnatchop in Compilation Mode::
10927 * Command Line for gnatchop::
10928 * Switches for gnatchop::
10929 * Examples of gnatchop Usage::
10932 @node Handling Files with Multiple Units
10933 @section Handling Files with Multiple Units
10936 The basic compilation model of GNAT requires that a file submitted to the
10937 compiler have only one unit and there be a strict correspondence
10938 between the file name and the unit name.
10940 The @code{gnatchop} utility allows both of these rules to be relaxed,
10941 allowing GNAT to process files which contain multiple compilation units
10942 and files with arbitrary file names. @code{gnatchop}
10943 reads the specified file and generates one or more output files,
10944 containing one unit per file. The unit and the file name correspond,
10945 as required by GNAT.
10947 If you want to permanently restructure a set of ``foreign'' files so that
10948 they match the GNAT rules, and do the remaining development using the
10949 GNAT structure, you can simply use @command{gnatchop} once, generate the
10950 new set of files and work with them from that point on.
10952 Alternatively, if you want to keep your files in the ``foreign'' format,
10953 perhaps to maintain compatibility with some other Ada compilation
10954 system, you can set up a procedure where you use @command{gnatchop} each
10955 time you compile, regarding the source files that it writes as temporary
10956 files that you throw away.
10958 Note that if your file containing multiple units starts with a byte order
10959 mark (BOM) specifying UTF-8 encoding, then the files generated by gnatchop
10960 will each start with a copy of this BOM, meaning that they can be compiled
10961 automatically in UTF-8 mode without needing to specify an explicit encoding.
10963 @node Operating gnatchop in Compilation Mode
10964 @section Operating gnatchop in Compilation Mode
10967 The basic function of @code{gnatchop} is to take a file with multiple units
10968 and split it into separate files. The boundary between files is reasonably
10969 clear, except for the issue of comments and pragmas. In default mode, the
10970 rule is that any pragmas between units belong to the previous unit, except
10971 that configuration pragmas always belong to the following unit. Any comments
10972 belong to the following unit. These rules
10973 almost always result in the right choice of
10974 the split point without needing to mark it explicitly and most users will
10975 find this default to be what they want. In this default mode it is incorrect to
10976 submit a file containing only configuration pragmas, or one that ends in
10977 configuration pragmas, to @code{gnatchop}.
10979 However, using a special option to activate ``compilation mode'',
10981 can perform another function, which is to provide exactly the semantics
10982 required by the RM for handling of configuration pragmas in a compilation.
10983 In the absence of configuration pragmas (at the main file level), this
10984 option has no effect, but it causes such configuration pragmas to be handled
10985 in a quite different manner.
10987 First, in compilation mode, if @code{gnatchop} is given a file that consists of
10988 only configuration pragmas, then this file is appended to the
10989 @file{gnat.adc} file in the current directory. This behavior provides
10990 the required behavior described in the RM for the actions to be taken
10991 on submitting such a file to the compiler, namely that these pragmas
10992 should apply to all subsequent compilations in the same compilation
10993 environment. Using GNAT, the current directory, possibly containing a
10994 @file{gnat.adc} file is the representation
10995 of a compilation environment. For more information on the
10996 @file{gnat.adc} file, see @ref{Handling of Configuration Pragmas}.
10998 Second, in compilation mode, if @code{gnatchop}
10999 is given a file that starts with
11000 configuration pragmas, and contains one or more units, then these
11001 configuration pragmas are prepended to each of the chopped files. This
11002 behavior provides the required behavior described in the RM for the
11003 actions to be taken on compiling such a file, namely that the pragmas
11004 apply to all units in the compilation, but not to subsequently compiled
11007 Finally, if configuration pragmas appear between units, they are appended
11008 to the previous unit. This results in the previous unit being illegal,
11009 since the compiler does not accept configuration pragmas that follow
11010 a unit. This provides the required RM behavior that forbids configuration
11011 pragmas other than those preceding the first compilation unit of a
11014 For most purposes, @code{gnatchop} will be used in default mode. The
11015 compilation mode described above is used only if you need exactly
11016 accurate behavior with respect to compilations, and you have files
11017 that contain multiple units and configuration pragmas. In this
11018 circumstance the use of @code{gnatchop} with the compilation mode
11019 switch provides the required behavior, and is for example the mode
11020 in which GNAT processes the ACVC tests.
11022 @node Command Line for gnatchop
11023 @section Command Line for @code{gnatchop}
11026 The @code{gnatchop} command has the form:
11029 $ gnatchop switches @var{file name} @r{[}@var{file name} @dots{}@r{]}
11034 The only required argument is the file name of the file to be chopped.
11035 There are no restrictions on the form of this file name. The file itself
11036 contains one or more Ada units, in normal GNAT format, concatenated
11037 together. As shown, more than one file may be presented to be chopped.
11039 When run in default mode, @code{gnatchop} generates one output file in
11040 the current directory for each unit in each of the files.
11042 @var{directory}, if specified, gives the name of the directory to which
11043 the output files will be written. If it is not specified, all files are
11044 written to the current directory.
11046 For example, given a
11047 file called @file{hellofiles} containing
11049 @smallexample @c ada
11054 with Text_IO; use Text_IO;
11057 Put_Line ("Hello");
11067 $ gnatchop ^hellofiles^HELLOFILES.^
11071 generates two files in the current directory, one called
11072 @file{hello.ads} containing the single line that is the procedure spec,
11073 and the other called @file{hello.adb} containing the remaining text. The
11074 original file is not affected. The generated files can be compiled in
11078 When gnatchop is invoked on a file that is empty or that contains only empty
11079 lines and/or comments, gnatchop will not fail, but will not produce any
11082 For example, given a
11083 file called @file{toto.txt} containing
11085 @smallexample @c ada
11097 $ gnatchop ^toto.txt^TOT.TXT^
11101 will not produce any new file and will result in the following warnings:
11104 toto.txt:1:01: warning: empty file, contains no compilation units
11105 no compilation units found
11106 no source files written
11109 @node Switches for gnatchop
11110 @section Switches for @code{gnatchop}
11113 @command{gnatchop} recognizes the following switches:
11119 @cindex @option{--version} @command{gnatchop}
11120 Display Copyright and version, then exit disregarding all other options.
11123 @cindex @option{--help} @command{gnatchop}
11124 If @option{--version} was not used, display usage, then exit disregarding
11127 @item ^-c^/COMPILATION^
11128 @cindex @option{^-c^/COMPILATION^} (@code{gnatchop})
11129 Causes @code{gnatchop} to operate in compilation mode, in which
11130 configuration pragmas are handled according to strict RM rules. See
11131 previous section for a full description of this mode.
11134 @item -gnat@var{xxx}
11135 This passes the given @option{-gnat@var{xxx}} switch to @code{gnat} which is
11136 used to parse the given file. Not all @var{xxx} options make sense,
11137 but for example, the use of @option{-gnati2} allows @code{gnatchop} to
11138 process a source file that uses Latin-2 coding for identifiers.
11142 Causes @code{gnatchop} to generate a brief help summary to the standard
11143 output file showing usage information.
11145 @item ^-k@var{mm}^/FILE_NAME_MAX_LENGTH=@var{mm}^
11146 @cindex @option{^-k^/FILE_NAME_MAX_LENGTH^} (@code{gnatchop})
11147 Limit generated file names to the specified number @code{mm}
11149 This is useful if the
11150 resulting set of files is required to be interoperable with systems
11151 which limit the length of file names.
11153 If no value is given, or
11154 if no @code{/FILE_NAME_MAX_LENGTH} qualifier is given,
11155 a default of 39, suitable for OpenVMS Alpha
11156 Systems, is assumed
11159 No space is allowed between the @option{-k} and the numeric value. The numeric
11160 value may be omitted in which case a default of @option{-k8},
11162 with DOS-like file systems, is used. If no @option{-k} switch
11164 there is no limit on the length of file names.
11167 @item ^-p^/PRESERVE^
11168 @cindex @option{^-p^/PRESERVE^} (@code{gnatchop})
11169 Causes the file ^modification^creation^ time stamp of the input file to be
11170 preserved and used for the time stamp of the output file(s). This may be
11171 useful for preserving coherency of time stamps in an environment where
11172 @code{gnatchop} is used as part of a standard build process.
11175 @cindex @option{^-q^/QUIET^} (@code{gnatchop})
11176 Causes output of informational messages indicating the set of generated
11177 files to be suppressed. Warnings and error messages are unaffected.
11179 @item ^-r^/REFERENCE^
11180 @cindex @option{^-r^/REFERENCE^} (@code{gnatchop})
11181 @findex Source_Reference
11182 Generate @code{Source_Reference} pragmas. Use this switch if the output
11183 files are regarded as temporary and development is to be done in terms
11184 of the original unchopped file. This switch causes
11185 @code{Source_Reference} pragmas to be inserted into each of the
11186 generated files to refers back to the original file name and line number.
11187 The result is that all error messages refer back to the original
11189 In addition, the debugging information placed into the object file (when
11190 the @option{^-g^/DEBUG^} switch of @command{gcc} or @command{gnatmake} is
11192 also refers back to this original file so that tools like profilers and
11193 debuggers will give information in terms of the original unchopped file.
11195 If the original file to be chopped itself contains
11196 a @code{Source_Reference}
11197 pragma referencing a third file, then gnatchop respects
11198 this pragma, and the generated @code{Source_Reference} pragmas
11199 in the chopped file refer to the original file, with appropriate
11200 line numbers. This is particularly useful when @code{gnatchop}
11201 is used in conjunction with @code{gnatprep} to compile files that
11202 contain preprocessing statements and multiple units.
11204 @item ^-v^/VERBOSE^
11205 @cindex @option{^-v^/VERBOSE^} (@code{gnatchop})
11206 Causes @code{gnatchop} to operate in verbose mode. The version
11207 number and copyright notice are output, as well as exact copies of
11208 the gnat1 commands spawned to obtain the chop control information.
11210 @item ^-w^/OVERWRITE^
11211 @cindex @option{^-w^/OVERWRITE^} (@code{gnatchop})
11212 Overwrite existing file names. Normally @code{gnatchop} regards it as a
11213 fatal error if there is already a file with the same name as a
11214 file it would otherwise output, in other words if the files to be
11215 chopped contain duplicated units. This switch bypasses this
11216 check, and causes all but the last instance of such duplicated
11217 units to be skipped.
11220 @item --GCC=@var{xxxx}
11221 @cindex @option{--GCC=} (@code{gnatchop})
11222 Specify the path of the GNAT parser to be used. When this switch is used,
11223 no attempt is made to add the prefix to the GNAT parser executable.
11227 @node Examples of gnatchop Usage
11228 @section Examples of @code{gnatchop} Usage
11232 @item gnatchop /OVERWRITE HELLO_S.ADA [PRERELEASE.FILES]
11235 @item gnatchop -w hello_s.ada prerelease/files
11238 Chops the source file @file{hello_s.ada}. The output files will be
11239 placed in the directory @file{^prerelease/files^[PRERELEASE.FILES]^},
11241 files with matching names in that directory (no files in the current
11242 directory are modified).
11244 @item gnatchop ^archive^ARCHIVE.^
11245 Chops the source file @file{^archive^ARCHIVE.^}
11246 into the current directory. One
11247 useful application of @code{gnatchop} is in sending sets of sources
11248 around, for example in email messages. The required sources are simply
11249 concatenated (for example, using a ^Unix @code{cat}^VMS @code{APPEND/NEW}^
11251 @command{gnatchop} is used at the other end to reconstitute the original
11254 @item gnatchop file1 file2 file3 direc
11255 Chops all units in files @file{file1}, @file{file2}, @file{file3}, placing
11256 the resulting files in the directory @file{direc}. Note that if any units
11257 occur more than once anywhere within this set of files, an error message
11258 is generated, and no files are written. To override this check, use the
11259 @option{^-w^/OVERWRITE^} switch,
11260 in which case the last occurrence in the last file will
11261 be the one that is output, and earlier duplicate occurrences for a given
11262 unit will be skipped.
11265 @node Configuration Pragmas
11266 @chapter Configuration Pragmas
11267 @cindex Configuration pragmas
11268 @cindex Pragmas, configuration
11271 Configuration pragmas include those pragmas described as
11272 such in the Ada Reference Manual, as well as
11273 implementation-dependent pragmas that are configuration pragmas.
11274 @xref{Implementation Defined Pragmas,,, gnat_rm, GNAT Reference Manual},
11275 for details on these additional GNAT-specific configuration pragmas.
11276 Most notably, the pragma @code{Source_File_Name}, which allows
11277 specifying non-default names for source files, is a configuration
11278 pragma. The following is a complete list of configuration pragmas
11279 recognized by GNAT:
11291 Compile_Time_Warning
11293 Component_Alignment
11300 External_Name_Casing
11303 Float_Representation
11316 Priority_Specific_Dispatching
11319 Propagate_Exceptions
11322 Restricted_Run_Time
11324 Restrictions_Warnings
11327 Source_File_Name_Project
11330 Suppress_Exception_Locations
11331 Task_Dispatching_Policy
11337 Wide_Character_Encoding
11342 * Handling of Configuration Pragmas::
11343 * The Configuration Pragmas Files::
11346 @node Handling of Configuration Pragmas
11347 @section Handling of Configuration Pragmas
11349 Configuration pragmas may either appear at the start of a compilation
11350 unit, in which case they apply only to that unit, or they may apply to
11351 all compilations performed in a given compilation environment.
11353 GNAT also provides the @code{gnatchop} utility to provide an automatic
11354 way to handle configuration pragmas following the semantics for
11355 compilations (that is, files with multiple units), described in the RM.
11356 See @ref{Operating gnatchop in Compilation Mode} for details.
11357 However, for most purposes, it will be more convenient to edit the
11358 @file{gnat.adc} file that contains configuration pragmas directly,
11359 as described in the following section.
11361 @node The Configuration Pragmas Files
11362 @section The Configuration Pragmas Files
11363 @cindex @file{gnat.adc}
11366 In GNAT a compilation environment is defined by the current
11367 directory at the time that a compile command is given. This current
11368 directory is searched for a file whose name is @file{gnat.adc}. If
11369 this file is present, it is expected to contain one or more
11370 configuration pragmas that will be applied to the current compilation.
11371 However, if the switch @option{-gnatA} is used, @file{gnat.adc} is not
11374 Configuration pragmas may be entered into the @file{gnat.adc} file
11375 either by running @code{gnatchop} on a source file that consists only of
11376 configuration pragmas, or more conveniently by
11377 direct editing of the @file{gnat.adc} file, which is a standard format
11380 In addition to @file{gnat.adc}, additional files containing configuration
11381 pragmas may be applied to the current compilation using the switch
11382 @option{-gnatec}@var{path}. @var{path} must designate an existing file that
11383 contains only configuration pragmas. These configuration pragmas are
11384 in addition to those found in @file{gnat.adc} (provided @file{gnat.adc}
11385 is present and switch @option{-gnatA} is not used).
11387 It is allowed to specify several switches @option{-gnatec}, all of which
11388 will be taken into account.
11390 If you are using project file, a separate mechanism is provided using
11391 project attributes, see @ref{Specifying Configuration Pragmas} for more
11395 Of special interest to GNAT OpenVMS Alpha is the following
11396 configuration pragma:
11398 @smallexample @c ada
11400 pragma Extend_System (Aux_DEC);
11405 In the presence of this pragma, GNAT adds to the definition of the
11406 predefined package SYSTEM all the additional types and subprograms that are
11407 defined in HP Ada. See @ref{Compatibility with HP Ada} for details.
11410 @node Handling Arbitrary File Naming Conventions Using gnatname
11411 @chapter Handling Arbitrary File Naming Conventions Using @code{gnatname}
11412 @cindex Arbitrary File Naming Conventions
11415 * Arbitrary File Naming Conventions::
11416 * Running gnatname::
11417 * Switches for gnatname::
11418 * Examples of gnatname Usage::
11421 @node Arbitrary File Naming Conventions
11422 @section Arbitrary File Naming Conventions
11425 The GNAT compiler must be able to know the source file name of a compilation
11426 unit. When using the standard GNAT default file naming conventions
11427 (@code{.ads} for specs, @code{.adb} for bodies), the GNAT compiler
11428 does not need additional information.
11431 When the source file names do not follow the standard GNAT default file naming
11432 conventions, the GNAT compiler must be given additional information through
11433 a configuration pragmas file (@pxref{Configuration Pragmas})
11435 When the non-standard file naming conventions are well-defined,
11436 a small number of pragmas @code{Source_File_Name} specifying a naming pattern
11437 (@pxref{Alternative File Naming Schemes}) may be sufficient. However,
11438 if the file naming conventions are irregular or arbitrary, a number
11439 of pragma @code{Source_File_Name} for individual compilation units
11441 To help maintain the correspondence between compilation unit names and
11442 source file names within the compiler,
11443 GNAT provides a tool @code{gnatname} to generate the required pragmas for a
11446 @node Running gnatname
11447 @section Running @code{gnatname}
11450 The usual form of the @code{gnatname} command is
11453 $ gnatname @ovar{switches} @var{naming_pattern} @ovar{naming_patterns}
11454 @r{[}--and @ovar{switches} @var{naming_pattern} @ovar{naming_patterns}@r{]}
11458 All of the arguments are optional. If invoked without any argument,
11459 @code{gnatname} will display its usage.
11462 When used with at least one naming pattern, @code{gnatname} will attempt to
11463 find all the compilation units in files that follow at least one of the
11464 naming patterns. To find these compilation units,
11465 @code{gnatname} will use the GNAT compiler in syntax-check-only mode on all
11469 One or several Naming Patterns may be given as arguments to @code{gnatname}.
11470 Each Naming Pattern is enclosed between double quotes.
11471 A Naming Pattern is a regular expression similar to the wildcard patterns
11472 used in file names by the Unix shells or the DOS prompt.
11475 @code{gnatname} may be called with several sections of directories/patterns.
11476 Sections are separated by switch @code{--and}. In each section, there must be
11477 at least one pattern. If no directory is specified in a section, the current
11478 directory (or the project directory is @code{-P} is used) is implied.
11479 The options other that the directory switches and the patterns apply globally
11480 even if they are in different sections.
11483 Examples of Naming Patterns are
11492 For a more complete description of the syntax of Naming Patterns,
11493 see the second kind of regular expressions described in @file{g-regexp.ads}
11494 (the ``Glob'' regular expressions).
11497 When invoked with no switch @code{-P}, @code{gnatname} will create a
11498 configuration pragmas file @file{gnat.adc} in the current working directory,
11499 with pragmas @code{Source_File_Name} for each file that contains a valid Ada
11502 @node Switches for gnatname
11503 @section Switches for @code{gnatname}
11506 Switches for @code{gnatname} must precede any specified Naming Pattern.
11509 You may specify any of the following switches to @code{gnatname}:
11515 @cindex @option{--version} @command{gnatname}
11516 Display Copyright and version, then exit disregarding all other options.
11519 @cindex @option{--help} @command{gnatname}
11520 If @option{--version} was not used, display usage, then exit disregarding
11524 Start another section of directories/patterns.
11526 @item ^-c^/CONFIG_FILE=^@file{file}
11527 @cindex @option{^-c^/CONFIG_FILE^} (@code{gnatname})
11528 Create a configuration pragmas file @file{file} (instead of the default
11531 There may be zero, one or more space between @option{-c} and
11534 @file{file} may include directory information. @file{file} must be
11535 writable. There may be only one switch @option{^-c^/CONFIG_FILE^}.
11536 When a switch @option{^-c^/CONFIG_FILE^} is
11537 specified, no switch @option{^-P^/PROJECT_FILE^} may be specified (see below).
11539 @item ^-d^/SOURCE_DIRS=^@file{dir}
11540 @cindex @option{^-d^/SOURCE_DIRS^} (@code{gnatname})
11541 Look for source files in directory @file{dir}. There may be zero, one or more
11542 spaces between @option{^-d^/SOURCE_DIRS=^} and @file{dir}.
11543 When a switch @option{^-d^/SOURCE_DIRS^}
11544 is specified, the current working directory will not be searched for source
11545 files, unless it is explicitly specified with a @option{^-d^/SOURCE_DIRS^}
11546 or @option{^-D^/DIR_FILES^} switch.
11547 Several switches @option{^-d^/SOURCE_DIRS^} may be specified.
11548 If @file{dir} is a relative path, it is relative to the directory of
11549 the configuration pragmas file specified with switch
11550 @option{^-c^/CONFIG_FILE^},
11551 or to the directory of the project file specified with switch
11552 @option{^-P^/PROJECT_FILE^} or,
11553 if neither switch @option{^-c^/CONFIG_FILE^}
11554 nor switch @option{^-P^/PROJECT_FILE^} are specified, it is relative to the
11555 current working directory. The directory
11556 specified with switch @option{^-d^/SOURCE_DIRS^} must exist and be readable.
11558 @item ^-D^/DIRS_FILE=^@file{file}
11559 @cindex @option{^-D^/DIRS_FILE^} (@code{gnatname})
11560 Look for source files in all directories listed in text file @file{file}.
11561 There may be zero, one or more spaces between @option{^-D^/DIRS_FILE=^}
11563 @file{file} must be an existing, readable text file.
11564 Each nonempty line in @file{file} must be a directory.
11565 Specifying switch @option{^-D^/DIRS_FILE^} is equivalent to specifying as many
11566 switches @option{^-d^/SOURCE_DIRS^} as there are nonempty lines in
11569 @item ^-f^/FOREIGN_PATTERN=^@file{pattern}
11570 @cindex @option{^-f^/FOREIGN_PATTERN^} (@code{gnatname})
11571 Foreign patterns. Using this switch, it is possible to add sources of languages
11572 other than Ada to the list of sources of a project file.
11573 It is only useful if a ^-P^/PROJECT_FILE^ switch is used.
11576 gnatname ^-Pprj -f"*.c"^/PROJECT_FILE=PRJ /FOREIGN_PATTERN=*.C^ "*.ada"
11579 will look for Ada units in all files with the @file{.ada} extension,
11580 and will add to the list of file for project @file{prj.gpr} the C files
11581 with extension @file{.^c^C^}.
11584 @cindex @option{^-h^/HELP^} (@code{gnatname})
11585 Output usage (help) information. The output is written to @file{stdout}.
11587 @item ^-P^/PROJECT_FILE=^@file{proj}
11588 @cindex @option{^-P^/PROJECT_FILE^} (@code{gnatname})
11589 Create or update project file @file{proj}. There may be zero, one or more space
11590 between @option{-P} and @file{proj}. @file{proj} may include directory
11591 information. @file{proj} must be writable.
11592 There may be only one switch @option{^-P^/PROJECT_FILE^}.
11593 When a switch @option{^-P^/PROJECT_FILE^} is specified,
11594 no switch @option{^-c^/CONFIG_FILE^} may be specified.
11596 @item ^-v^/VERBOSE^
11597 @cindex @option{^-v^/VERBOSE^} (@code{gnatname})
11598 Verbose mode. Output detailed explanation of behavior to @file{stdout}.
11599 This includes name of the file written, the name of the directories to search
11600 and, for each file in those directories whose name matches at least one of
11601 the Naming Patterns, an indication of whether the file contains a unit,
11602 and if so the name of the unit.
11604 @item ^-v -v^/VERBOSE /VERBOSE^
11605 @cindex @option{^-v -v^/VERBOSE /VERBOSE^} (@code{gnatname})
11606 Very Verbose mode. In addition to the output produced in verbose mode,
11607 for each file in the searched directories whose name matches none of
11608 the Naming Patterns, an indication is given that there is no match.
11610 @item ^-x^/EXCLUDED_PATTERN=^@file{pattern}
11611 @cindex @option{^-x^/EXCLUDED_PATTERN^} (@code{gnatname})
11612 Excluded patterns. Using this switch, it is possible to exclude some files
11613 that would match the name patterns. For example,
11615 gnatname ^-x "*_nt.ada"^/EXCLUDED_PATTERN=*_nt.ada^ "*.ada"
11618 will look for Ada units in all files with the @file{.ada} extension,
11619 except those whose names end with @file{_nt.ada}.
11623 @node Examples of gnatname Usage
11624 @section Examples of @code{gnatname} Usage
11628 $ gnatname /CONFIG_FILE=[HOME.ME]NAMES.ADC /SOURCE_DIRS=SOURCES "[a-z]*.ada*"
11634 $ gnatname -c /home/me/names.adc -d sources "[a-z]*.ada*"
11639 In this example, the directory @file{^/home/me^[HOME.ME]^} must already exist
11640 and be writable. In addition, the directory
11641 @file{^/home/me/sources^[HOME.ME.SOURCES]^} (specified by
11642 @option{^-d sources^/SOURCE_DIRS=SOURCES^}) must exist and be readable.
11645 Note the optional spaces after @option{-c} and @option{-d}.
11650 $ gnatname -P/home/me/proj -x "*_nt_body.ada"
11651 -dsources -dsources/plus -Dcommon_dirs.txt "body_*" "spec_*"
11654 $ gnatname /PROJECT_FILE=[HOME.ME]PROJ
11655 /EXCLUDED_PATTERN=*_nt_body.ada
11656 /SOURCE_DIRS=(SOURCES,[SOURCES.PLUS])
11657 /DIRS_FILE=COMMON_DIRS.TXT "body_*" "spec_*"
11661 Note that several switches @option{^-d^/SOURCE_DIRS^} may be used,
11662 even in conjunction with one or several switches
11663 @option{^-D^/DIRS_FILE^}. Several Naming Patterns and one excluded pattern
11664 are used in this example.
11666 @c *****************************************
11667 @c * G N A T P r o j e c t M a n a g e r *
11668 @c *****************************************
11669 @node GNAT Project Manager
11670 @chapter GNAT Project Manager
11674 * Examples of Project Files::
11675 * Project File Syntax::
11676 * Objects and Sources in Project Files::
11677 * Importing Projects::
11678 * Project Extension::
11679 * Project Hierarchy Extension::
11680 * External References in Project Files::
11681 * Packages in Project Files::
11682 * Variables from Imported Projects::
11684 * Library Projects::
11685 * Stand-alone Library Projects::
11686 * Switches Related to Project Files::
11687 * Tools Supporting Project Files::
11688 * An Extended Example::
11689 * Project File Complete Syntax::
11692 @c ****************
11693 @c * Introduction *
11694 @c ****************
11697 @section Introduction
11700 This chapter describes GNAT's @emph{Project Manager}, a facility that allows
11701 you to manage complex builds involving a number of source files, directories,
11702 and compilation options for different system configurations. In particular,
11703 project files allow you to specify:
11706 The directory or set of directories containing the source files, and/or the
11707 names of the specific source files themselves
11709 The directory in which the compiler's output
11710 (@file{ALI} files, object files, tree files) is to be placed
11712 The directory in which the executable programs is to be placed
11714 ^Switch^Switch^ settings for any of the project-enabled tools
11715 (@command{gnatmake}, compiler, binder, linker, @code{gnatls}, @code{gnatxref},
11716 @code{gnatfind}); you can apply these settings either globally or to individual
11719 The source files containing the main subprogram(s) to be built
11721 The source programming language(s) (currently Ada and/or C)
11723 Source file naming conventions; you can specify these either globally or for
11724 individual compilation units
11731 @node Project Files
11732 @subsection Project Files
11735 Project files are written in a syntax close to that of Ada, using familiar
11736 notions such as packages, context clauses, declarations, default values,
11737 assignments, and inheritance. Finally, project files can be built
11738 hierarchically from other project files, simplifying complex system
11739 integration and project reuse.
11741 A @dfn{project} is a specific set of values for various compilation properties.
11742 The settings for a given project are described by means of
11743 a @dfn{project file}, which is a text file written in an Ada-like syntax.
11744 Property values in project files are either strings or lists of strings.
11745 Properties that are not explicitly set receive default values. A project
11746 file may interrogate the values of @dfn{external variables} (user-defined
11747 command-line switches or environment variables), and it may specify property
11748 settings conditionally, based on the value of such variables.
11750 In simple cases, a project's source files depend only on other source files
11751 in the same project, or on the predefined libraries. (@emph{Dependence} is
11753 the Ada technical sense; as in one Ada unit @code{with}ing another.) However,
11754 the Project Manager also allows more sophisticated arrangements,
11755 where the source files in one project depend on source files in other
11759 One project can @emph{import} other projects containing needed source files.
11761 You can organize GNAT projects in a hierarchy: a @emph{child} project
11762 can extend a @emph{parent} project, inheriting the parent's source files and
11763 optionally overriding any of them with alternative versions
11767 More generally, the Project Manager lets you structure large development
11768 efforts into hierarchical subsystems, where build decisions are delegated
11769 to the subsystem level, and thus different compilation environments
11770 (^switch^switch^ settings) used for different subsystems.
11772 The Project Manager is invoked through the
11773 @option{^-P^/PROJECT_FILE=^@emph{projectfile}}
11774 switch to @command{gnatmake} or to the @command{^gnat^GNAT^} front driver.
11776 There may be zero, one or more spaces between @option{-P} and
11777 @option{@emph{projectfile}}.
11779 If you want to define (on the command line) an external variable that is
11780 queried by the project file, you must use the
11781 @option{^-X^/EXTERNAL_REFERENCE=^@emph{vbl}=@emph{value}} switch.
11782 The Project Manager parses and interprets the project file, and drives the
11783 invoked tool based on the project settings.
11785 The Project Manager supports a wide range of development strategies,
11786 for systems of all sizes. Here are some typical practices that are
11790 Using a common set of source files, but generating object files in different
11791 directories via different ^switch^switch^ settings
11793 Using a mostly-shared set of source files, but with different versions of
11798 The destination of an executable can be controlled inside a project file
11799 using the @option{^-o^-o^}
11801 In the absence of such a ^switch^switch^ either inside
11802 the project file or on the command line, any executable files generated by
11803 @command{gnatmake} are placed in the directory @code{Exec_Dir} specified
11804 in the project file. If no @code{Exec_Dir} is specified, they will be placed
11805 in the object directory of the project.
11807 You can use project files to achieve some of the effects of a source
11808 versioning system (for example, defining separate projects for
11809 the different sets of sources that comprise different releases) but the
11810 Project Manager is independent of any source configuration management tools
11811 that might be used by the developers.
11813 The next section introduces the main features of GNAT's project facility
11814 through a sequence of examples; subsequent sections will present the syntax
11815 and semantics in more detail. A more formal description of the project
11816 facility appears in @ref{Project File Reference,,, gnat_rm, GNAT
11819 @c *****************************
11820 @c * Examples of Project Files *
11821 @c *****************************
11823 @node Examples of Project Files
11824 @section Examples of Project Files
11826 This section illustrates some of the typical uses of project files and
11827 explains their basic structure and behavior.
11830 * Common Sources with Different ^Switches^Switches^ and Directories::
11831 * Using External Variables::
11832 * Importing Other Projects::
11833 * Extending a Project::
11836 @node Common Sources with Different ^Switches^Switches^ and Directories
11837 @subsection Common Sources with Different ^Switches^Switches^ and Directories
11841 * Specifying the Object Directory::
11842 * Specifying the Exec Directory::
11843 * Project File Packages::
11844 * Specifying ^Switch^Switch^ Settings::
11845 * Main Subprograms::
11846 * Executable File Names::
11847 * Source File Naming Conventions::
11848 * Source Language(s)::
11852 Suppose that the Ada source files @file{pack.ads}, @file{pack.adb}, and
11853 @file{proc.adb} are in the @file{/common} directory. The file
11854 @file{proc.adb} contains an Ada main subprogram @code{Proc} that @code{with}s
11855 package @code{Pack}. We want to compile these source files under two sets
11856 of ^switches^switches^:
11859 When debugging, we want to pass the @option{-g} switch to @command{gnatmake},
11860 and the @option{^-gnata^-gnata^},
11861 @option{^-gnato^-gnato^},
11862 and @option{^-gnatE^-gnatE^} switches to the
11863 compiler; the compiler's output is to appear in @file{/common/debug}
11865 When preparing a release version, we want to pass the @option{^-O2^O2^} switch
11866 to the compiler; the compiler's output is to appear in @file{/common/release}
11870 The GNAT project files shown below, respectively @file{debug.gpr} and
11871 @file{release.gpr} in the @file{/common} directory, achieve these effects.
11884 ^/common/debug^[COMMON.DEBUG]^
11889 ^/common/release^[COMMON.RELEASE]^
11894 Here are the corresponding project files:
11896 @smallexample @c projectfile
11899 for Object_Dir use "debug";
11900 for Main use ("proc");
11903 for ^Default_Switches^Default_Switches^ ("Ada")
11905 for Executable ("proc.adb") use "proc1";
11910 package Compiler is
11911 for ^Default_Switches^Default_Switches^ ("Ada")
11912 use ("-fstack-check",
11915 "^-gnatE^-gnatE^");
11921 @smallexample @c projectfile
11924 for Object_Dir use "release";
11925 for Exec_Dir use ".";
11926 for Main use ("proc");
11928 package Compiler is
11929 for ^Default_Switches^Default_Switches^ ("Ada")
11937 The name of the project defined by @file{debug.gpr} is @code{"Debug"} (case
11938 insensitive), and analogously the project defined by @file{release.gpr} is
11939 @code{"Release"}. For consistency the file should have the same name as the
11940 project, and the project file's extension should be @code{"gpr"}. These
11941 conventions are not required, but a warning is issued if they are not followed.
11943 If the current directory is @file{^/temp^[TEMP]^}, then the command
11945 gnatmake ^-P/common/debug.gpr^/PROJECT_FILE=[COMMON]DEBUG^
11949 generates object and ALI files in @file{^/common/debug^[COMMON.DEBUG]^},
11950 as well as the @code{^proc1^PROC1.EXE^} executable,
11951 using the ^switch^switch^ settings defined in the project file.
11953 Likewise, the command
11955 gnatmake ^-P/common/release.gpr^/PROJECT_FILE=[COMMON]RELEASE^
11959 generates object and ALI files in @file{^/common/release^[COMMON.RELEASE]^},
11960 and the @code{^proc^PROC.EXE^}
11961 executable in @file{^/common^[COMMON]^},
11962 using the ^switch^switch^ settings from the project file.
11965 @unnumberedsubsubsec Source Files
11968 If a project file does not explicitly specify a set of source directories or
11969 a set of source files, then by default the project's source files are the
11970 Ada source files in the project file directory. Thus @file{pack.ads},
11971 @file{pack.adb}, and @file{proc.adb} are the source files for both projects.
11973 @node Specifying the Object Directory
11974 @unnumberedsubsubsec Specifying the Object Directory
11977 Several project properties are modeled by Ada-style @emph{attributes};
11978 a property is defined by supplying the equivalent of an Ada attribute
11979 definition clause in the project file.
11980 A project's object directory is another such a property; the corresponding
11981 attribute is @code{Object_Dir}, and its value is also a string expression,
11982 specified either as absolute or relative. In the later case,
11983 it is relative to the project file directory. Thus the compiler's
11984 output is directed to @file{^/common/debug^[COMMON.DEBUG]^}
11985 (for the @code{Debug} project)
11986 and to @file{^/common/release^[COMMON.RELEASE]^}
11987 (for the @code{Release} project).
11988 If @code{Object_Dir} is not specified, then the default is the project file
11991 @node Specifying the Exec Directory
11992 @unnumberedsubsubsec Specifying the Exec Directory
11995 A project's exec directory is another property; the corresponding
11996 attribute is @code{Exec_Dir}, and its value is also a string expression,
11997 either specified as relative or absolute. If @code{Exec_Dir} is not specified,
11998 then the default is the object directory (which may also be the project file
11999 directory if attribute @code{Object_Dir} is not specified). Thus the executable
12000 is placed in @file{^/common/debug^[COMMON.DEBUG]^}
12001 for the @code{Debug} project (attribute @code{Exec_Dir} not specified)
12002 and in @file{^/common^[COMMON]^} for the @code{Release} project.
12004 @node Project File Packages
12005 @unnumberedsubsubsec Project File Packages
12008 A GNAT tool that is integrated with the Project Manager is modeled by a
12009 corresponding package in the project file. In the example above,
12010 The @code{Debug} project defines the packages @code{Builder}
12011 (for @command{gnatmake}) and @code{Compiler};
12012 the @code{Release} project defines only the @code{Compiler} package.
12014 The Ada-like package syntax is not to be taken literally. Although packages in
12015 project files bear a surface resemblance to packages in Ada source code, the
12016 notation is simply a way to convey a grouping of properties for a named
12017 entity. Indeed, the package names permitted in project files are restricted
12018 to a predefined set, corresponding to the project-aware tools, and the contents
12019 of packages are limited to a small set of constructs.
12020 The packages in the example above contain attribute definitions.
12022 @node Specifying ^Switch^Switch^ Settings
12023 @unnumberedsubsubsec Specifying ^Switch^Switch^ Settings
12026 ^Switch^Switch^ settings for a project-aware tool can be specified through
12027 attributes in the package that corresponds to the tool.
12028 The example above illustrates one of the relevant attributes,
12029 @code{^Default_Switches^Default_Switches^}, which is defined in packages
12030 in both project files.
12031 Unlike simple attributes like @code{Source_Dirs},
12032 @code{^Default_Switches^Default_Switches^} is
12033 known as an @emph{associative array}. When you define this attribute, you must
12034 supply an ``index'' (a literal string), and the effect of the attribute
12035 definition is to set the value of the array at the specified index.
12036 For the @code{^Default_Switches^Default_Switches^} attribute,
12037 the index is a programming language (in our case, Ada),
12038 and the value specified (after @code{use}) must be a list
12039 of string expressions.
12041 The attributes permitted in project files are restricted to a predefined set.
12042 Some may appear at project level, others in packages.
12043 For any attribute that is an associative array, the index must always be a
12044 literal string, but the restrictions on this string (e.g., a file name or a
12045 language name) depend on the individual attribute.
12046 Also depending on the attribute, its specified value will need to be either a
12047 string or a string list.
12049 In the @code{Debug} project, we set the switches for two tools,
12050 @command{gnatmake} and the compiler, and thus we include the two corresponding
12051 packages; each package defines the @code{^Default_Switches^Default_Switches^}
12052 attribute with index @code{"Ada"}.
12053 Note that the package corresponding to
12054 @command{gnatmake} is named @code{Builder}. The @code{Release} project is
12055 similar, but only includes the @code{Compiler} package.
12057 In project @code{Debug} above, the ^switches^switches^ starting with
12058 @option{-gnat} that are specified in package @code{Compiler}
12059 could have been placed in package @code{Builder}, since @command{gnatmake}
12060 transmits all such ^switches^switches^ to the compiler.
12062 @node Main Subprograms
12063 @unnumberedsubsubsec Main Subprograms
12066 One of the specifiable properties of a project is a list of files that contain
12067 main subprograms. This property is captured in the @code{Main} attribute,
12068 whose value is a list of strings. If a project defines the @code{Main}
12069 attribute, it is not necessary to identify the main subprogram(s) when
12070 invoking @command{gnatmake} (@pxref{gnatmake and Project Files}).
12072 @node Executable File Names
12073 @unnumberedsubsubsec Executable File Names
12076 By default, the executable file name corresponding to a main source is
12077 deduced from the main source file name. Through the attributes
12078 @code{Executable} and @code{Executable_Suffix} of package @code{Builder},
12079 it is possible to change this default.
12080 In project @code{Debug} above, the executable file name
12081 for main source @file{^proc.adb^PROC.ADB^} is
12082 @file{^proc1^PROC1.EXE^}.
12083 Attribute @code{Executable_Suffix}, when specified, may change the suffix
12084 of the executable files, when no attribute @code{Executable} applies:
12085 its value replace the platform-specific executable suffix.
12086 Attributes @code{Executable} and @code{Executable_Suffix} are the only ways to
12087 specify a non-default executable file name when several mains are built at once
12088 in a single @command{gnatmake} command.
12090 @node Source File Naming Conventions
12091 @unnumberedsubsubsec Source File Naming Conventions
12094 Since the project files above do not specify any source file naming
12095 conventions, the GNAT defaults are used. The mechanism for defining source
12096 file naming conventions -- a package named @code{Naming} --
12097 is described below (@pxref{Naming Schemes}).
12099 @node Source Language(s)
12100 @unnumberedsubsubsec Source Language(s)
12103 Since the project files do not specify a @code{Languages} attribute, by
12104 default the GNAT tools assume that the language of the project file is Ada.
12105 More generally, a project can comprise source files
12106 in Ada, C, and/or other languages.
12108 @node Using External Variables
12109 @subsection Using External Variables
12112 Instead of supplying different project files for debug and release, we can
12113 define a single project file that queries an external variable (set either
12114 on the command line or via an ^environment variable^logical name^) in order to
12115 conditionally define the appropriate settings. Again, assume that the
12116 source files @file{pack.ads}, @file{pack.adb}, and @file{proc.adb} are
12117 located in directory @file{^/common^[COMMON]^}. The following project file,
12118 @file{build.gpr}, queries the external variable named @code{STYLE} and
12119 defines an object directory and ^switch^switch^ settings based on whether
12120 the value is @code{"deb"} (debug) or @code{"rel"} (release), and where
12121 the default is @code{"deb"}.
12123 @smallexample @c projectfile
12126 for Main use ("proc");
12128 type Style_Type is ("deb", "rel");
12129 Style : Style_Type := external ("STYLE", "deb");
12133 for Object_Dir use "debug";
12136 for Object_Dir use "release";
12137 for Exec_Dir use ".";
12146 for ^Default_Switches^Default_Switches^ ("Ada")
12148 for Executable ("proc") use "proc1";
12157 package Compiler is
12161 for ^Default_Switches^Default_Switches^ ("Ada")
12162 use ("^-gnata^-gnata^",
12164 "^-gnatE^-gnatE^");
12167 for ^Default_Switches^Default_Switches^ ("Ada")
12178 @code{Style_Type} is an example of a @emph{string type}, which is the project
12179 file analog of an Ada enumeration type but whose components are string literals
12180 rather than identifiers. @code{Style} is declared as a variable of this type.
12182 The form @code{external("STYLE", "deb")} is known as an
12183 @emph{external reference}; its first argument is the name of an
12184 @emph{external variable}, and the second argument is a default value to be
12185 used if the external variable doesn't exist. You can define an external
12186 variable on the command line via the @option{^-X^/EXTERNAL_REFERENCE^} switch,
12187 or you can use ^an environment variable^a logical name^
12188 as an external variable.
12190 Each @code{case} construct is expanded by the Project Manager based on the
12191 value of @code{Style}. Thus the command
12194 gnatmake -P/common/build.gpr -XSTYLE=deb
12200 gnatmake /PROJECT_FILE=[COMMON]BUILD.GPR /EXTERNAL_REFERENCE=STYLE=deb
12205 is equivalent to the @command{gnatmake} invocation using the project file
12206 @file{debug.gpr} in the earlier example. So is the command
12208 gnatmake ^-P/common/build.gpr^/PROJECT_FILE=[COMMON]BUILD.GPR^
12212 since @code{"deb"} is the default for @code{STYLE}.
12218 gnatmake -P/common/build.gpr -XSTYLE=rel
12224 GNAT MAKE /PROJECT_FILE=[COMMON]BUILD.GPR /EXTERNAL_REFERENCE=STYLE=rel
12229 is equivalent to the @command{gnatmake} invocation using the project file
12230 @file{release.gpr} in the earlier example.
12232 @node Importing Other Projects
12233 @subsection Importing Other Projects
12234 @cindex @code{ADA_PROJECT_PATH}
12237 A compilation unit in a source file in one project may depend on compilation
12238 units in source files in other projects. To compile this unit under
12239 control of a project file, the
12240 dependent project must @emph{import} the projects containing the needed source
12242 This effect is obtained using syntax similar to an Ada @code{with} clause,
12243 but where @code{with}ed entities are strings that denote project files.
12245 As an example, suppose that the two projects @code{GUI_Proj} and
12246 @code{Comm_Proj} are defined in the project files @file{gui_proj.gpr} and
12247 @file{comm_proj.gpr} in directories @file{^/gui^[GUI]^}
12248 and @file{^/comm^[COMM]^}, respectively.
12249 Suppose that the source files for @code{GUI_Proj} are
12250 @file{gui.ads} and @file{gui.adb}, and that the source files for
12251 @code{Comm_Proj} are @file{comm.ads} and @file{comm.adb}, where each set of
12252 files is located in its respective project file directory. Schematically:
12271 We want to develop an application in directory @file{^/app^[APP]^} that
12272 @code{with} the packages @code{GUI} and @code{Comm}, using the properties of
12273 the corresponding project files (e.g.@: the ^switch^switch^ settings
12274 and object directory).
12275 Skeletal code for a main procedure might be something like the following:
12277 @smallexample @c ada
12280 procedure App_Main is
12289 Here is a project file, @file{app_proj.gpr}, that achieves the desired
12292 @smallexample @c projectfile
12294 with "/gui/gui_proj", "/comm/comm_proj";
12295 project App_Proj is
12296 for Main use ("app_main");
12302 Building an executable is achieved through the command:
12304 gnatmake ^-P/app/app_proj^/PROJECT_FILE=[APP]APP_PROJ^
12307 which will generate the @code{^app_main^APP_MAIN.EXE^} executable
12308 in the directory where @file{app_proj.gpr} resides.
12310 If an imported project file uses the standard extension (@code{^gpr^GPR^}) then
12311 (as illustrated above) the @code{with} clause can omit the extension.
12313 Our example specified an absolute path for each imported project file.
12314 Alternatively, the directory name of an imported object can be omitted
12318 The imported project file is in the same directory as the importing project
12321 You have defined ^an environment variable^a logical name^
12322 that includes the directory containing
12323 the needed project file. The syntax of @code{ADA_PROJECT_PATH} is the same as
12324 the syntax of @code{ADA_INCLUDE_PATH} and @code{ADA_OBJECTS_PATH}: a list of
12325 directory names separated by colons (semicolons on Windows).
12329 Thus, if we define @code{ADA_PROJECT_PATH} to include @file{^/gui^[GUI]^} and
12330 @file{^/comm^[COMM]^}, then our project file @file{app_proj.gpr} can be written
12333 @smallexample @c projectfile
12335 with "gui_proj", "comm_proj";
12336 project App_Proj is
12337 for Main use ("app_main");
12343 Importing other projects can create ambiguities.
12344 For example, the same unit might be present in different imported projects, or
12345 it might be present in both the importing project and in an imported project.
12346 Both of these conditions are errors. Note that in the current version of
12347 the Project Manager, it is illegal to have an ambiguous unit even if the
12348 unit is never referenced by the importing project. This restriction may be
12349 relaxed in a future release.
12351 @node Extending a Project
12352 @subsection Extending a Project
12355 In large software systems it is common to have multiple
12356 implementations of a common interface; in Ada terms, multiple versions of a
12357 package body for the same spec. For example, one implementation
12358 might be safe for use in tasking programs, while another might only be used
12359 in sequential applications. This can be modeled in GNAT using the concept
12360 of @emph{project extension}. If one project (the ``child'') @emph{extends}
12361 another project (the ``parent'') then by default all source files of the
12362 parent project are inherited by the child, but the child project can
12363 override any of the parent's source files with new versions, and can also
12364 add new files. This facility is the project analog of a type extension in
12365 Object-Oriented Programming. Project hierarchies are permitted (a child
12366 project may be the parent of yet another project), and a project that
12367 inherits one project can also import other projects.
12369 As an example, suppose that directory @file{^/seq^[SEQ]^} contains the project
12370 file @file{seq_proj.gpr} as well as the source files @file{pack.ads},
12371 @file{pack.adb}, and @file{proc.adb}:
12384 Note that the project file can simply be empty (that is, no attribute or
12385 package is defined):
12387 @smallexample @c projectfile
12389 project Seq_Proj is
12395 implying that its source files are all the Ada source files in the project
12398 Suppose we want to supply an alternate version of @file{pack.adb}, in
12399 directory @file{^/tasking^[TASKING]^}, but use the existing versions of
12400 @file{pack.ads} and @file{proc.adb}. We can define a project
12401 @code{Tasking_Proj} that inherits @code{Seq_Proj}:
12405 ^/tasking^[TASKING]^
12411 project Tasking_Proj extends "/seq/seq_proj" is
12417 The version of @file{pack.adb} used in a build depends on which project file
12420 Note that we could have obtained the desired behavior using project import
12421 rather than project inheritance; a @code{base} project would contain the
12422 sources for @file{pack.ads} and @file{proc.adb}, a sequential project would
12423 import @code{base} and add @file{pack.adb}, and likewise a tasking project
12424 would import @code{base} and add a different version of @file{pack.adb}. The
12425 choice depends on whether other sources in the original project need to be
12426 overridden. If they do, then project extension is necessary, otherwise,
12427 importing is sufficient.
12430 In a project file that extends another project file, it is possible to
12431 indicate that an inherited source is not part of the sources of the extending
12432 project. This is necessary sometimes when a package spec has been overloaded
12433 and no longer requires a body: in this case, it is necessary to indicate that
12434 the inherited body is not part of the sources of the project, otherwise there
12435 will be a compilation error when compiling the spec.
12437 For that purpose, the attribute @code{Excluded_Source_Files} is used.
12438 Its value is a string list: a list of file names. It is also possible to use
12439 attribute @code{Excluded_Source_List_File}. Its value is a single string:
12440 the file name of a text file containing a list of file names, one per line.
12442 @smallexample @c @projectfile
12443 project B extends "a" is
12444 for Source_Files use ("pkg.ads");
12445 -- New spec of Pkg does not need a completion
12446 for Excluded_Source_Files use ("pkg.adb");
12450 Attribute @code{Excluded_Source_Files} may also be used to check if a source
12451 is still needed: if it is possible to build using @command{gnatmake} when such
12452 a source is put in attribute @code{Excluded_Source_Files} of a project P, then
12453 it is possible to remove the source completely from a system that includes
12456 @c ***********************
12457 @c * Project File Syntax *
12458 @c ***********************
12460 @node Project File Syntax
12461 @section Project File Syntax
12465 * Qualified Projects::
12471 * Associative Array Attributes::
12472 * case Constructions::
12476 This section describes the structure of project files.
12478 A project may be an @emph{independent project}, entirely defined by a single
12479 project file. Any Ada source file in an independent project depends only
12480 on the predefined library and other Ada source files in the same project.
12483 A project may also @dfn{depend on} other projects, in either or both of
12484 the following ways:
12486 @item It may import any number of projects
12487 @item It may extend at most one other project
12491 The dependence relation is a directed acyclic graph (the subgraph reflecting
12492 the ``extends'' relation is a tree).
12494 A project's @dfn{immediate sources} are the source files directly defined by
12495 that project, either implicitly by residing in the project file's directory,
12496 or explicitly through any of the source-related attributes described below.
12497 More generally, a project @var{proj}'s @dfn{sources} are the immediate sources
12498 of @var{proj} together with the immediate sources (unless overridden) of any
12499 project on which @var{proj} depends (either directly or indirectly).
12502 @subsection Basic Syntax
12505 As seen in the earlier examples, project files have an Ada-like syntax.
12506 The minimal project file is:
12507 @smallexample @c projectfile
12516 The identifier @code{Empty} is the name of the project.
12517 This project name must be present after the reserved
12518 word @code{end} at the end of the project file, followed by a semi-colon.
12520 Any name in a project file, such as the project name or a variable name,
12521 has the same syntax as an Ada identifier.
12523 The reserved words of project files are the Ada 95 reserved words plus
12524 @code{extends}, @code{external}, and @code{project}. Note that the only Ada
12525 reserved words currently used in project file syntax are:
12561 Comments in project files have the same syntax as in Ada, two consecutive
12562 hyphens through the end of the line.
12564 @node Qualified Projects
12565 @subsection Qualified Projects
12568 Before the reserved @code{project}, there may be one or two "qualifiers", that
12569 is identifiers or other reserved words, to qualify the project.
12571 The current list of qualifiers is:
12575 @code{abstract}: qualify a project with no sources. A qualified abstract
12576 project must either have no declaration of attributes @code{Source_Dirs},
12577 @code{Source_Files}, @code{Languages} or @code{Source_List_File}, or one of
12578 @code{Source_Dirs}, @code{Source_Files}, or @code{Languages} must be declared
12579 as empty. If it extends another project, the project it extends must also be a
12580 qualified abstract project.
12583 @code{standard}: a standard project is a non library project with sources.
12586 @code{aggregate}: for future extension
12589 @code{aggregate library}: for future extension
12592 @code{library}: a library project must declare both attributes
12593 @code{Library_Name} and @code{Library_Dir}.
12596 @code{configuration}: a configuration project cannot be in a project tree.
12600 @subsection Packages
12603 A project file may contain @emph{packages}. The name of a package must be one
12604 of the identifiers from the following list. A package
12605 with a given name may only appear once in a project file. Package names are
12606 case insensitive. The following package names are legal:
12622 @code{Cross_Reference}
12626 @code{Pretty_Printer}
12636 @code{Language_Processing}
12640 In its simplest form, a package may be empty:
12642 @smallexample @c projectfile
12652 A package may contain @emph{attribute declarations},
12653 @emph{variable declarations} and @emph{case constructions}, as will be
12656 When there is ambiguity between a project name and a package name,
12657 the name always designates the project. To avoid possible confusion, it is
12658 always a good idea to avoid naming a project with one of the
12659 names allowed for packages or any name that starts with @code{gnat}.
12662 @subsection Expressions
12665 An @emph{expression} is either a @emph{string expression} or a
12666 @emph{string list expression}.
12668 A @emph{string expression} is either a @emph{simple string expression} or a
12669 @emph{compound string expression}.
12671 A @emph{simple string expression} is one of the following:
12673 @item A literal string; e.g.@: @code{"comm/my_proj.gpr"}
12674 @item A string-valued variable reference (@pxref{Variables})
12675 @item A string-valued attribute reference (@pxref{Attributes})
12676 @item An external reference (@pxref{External References in Project Files})
12680 A @emph{compound string expression} is a concatenation of string expressions,
12681 using the operator @code{"&"}
12683 Path & "/" & File_Name & ".ads"
12687 A @emph{string list expression} is either a
12688 @emph{simple string list expression} or a
12689 @emph{compound string list expression}.
12691 A @emph{simple string list expression} is one of the following:
12693 @item A parenthesized list of zero or more string expressions,
12694 separated by commas
12696 File_Names := (File_Name, "gnat.adc", File_Name & ".orig");
12699 @item A string list-valued variable reference
12700 @item A string list-valued attribute reference
12704 A @emph{compound string list expression} is the concatenation (using
12705 @code{"&"}) of a simple string list expression and an expression. Note that
12706 each term in a compound string list expression, except the first, may be
12707 either a string expression or a string list expression.
12709 @smallexample @c projectfile
12711 File_Name_List := () & File_Name; -- One string in this list
12712 Extended_File_Name_List := File_Name_List & (File_Name & ".orig");
12714 Big_List := File_Name_List & Extended_File_Name_List;
12715 -- Concatenation of two string lists: three strings
12716 Illegal_List := "gnat.adc" & Extended_File_Name_List;
12717 -- Illegal: must start with a string list
12722 @subsection String Types
12725 A @emph{string type declaration} introduces a discrete set of string literals.
12726 If a string variable is declared to have this type, its value
12727 is restricted to the given set of literals.
12729 Here is an example of a string type declaration:
12731 @smallexample @c projectfile
12732 type OS is ("NT", "nt", "Unix", "GNU/Linux", "other OS");
12736 Variables of a string type are called @emph{typed variables}; all other
12737 variables are called @emph{untyped variables}. Typed variables are
12738 particularly useful in @code{case} constructions, to support conditional
12739 attribute declarations.
12740 (@pxref{case Constructions}).
12742 The string literals in the list are case sensitive and must all be different.
12743 They may include any graphic characters allowed in Ada, including spaces.
12745 A string type may only be declared at the project level, not inside a package.
12747 A string type may be referenced by its name if it has been declared in the same
12748 project file, or by an expanded name whose prefix is the name of the project
12749 in which it is declared.
12752 @subsection Variables
12755 A variable may be declared at the project file level, or within a package.
12756 Here are some examples of variable declarations:
12758 @smallexample @c projectfile
12760 This_OS : OS := external ("OS"); -- a typed variable declaration
12761 That_OS := "GNU/Linux"; -- an untyped variable declaration
12766 The syntax of a @emph{typed variable declaration} is identical to the Ada
12767 syntax for an object declaration. By contrast, the syntax of an untyped
12768 variable declaration is identical to an Ada assignment statement. In fact,
12769 variable declarations in project files have some of the characteristics of
12770 an assignment, in that successive declarations for the same variable are
12771 allowed. Untyped variable declarations do establish the expected kind of the
12772 variable (string or string list), and successive declarations for it must
12773 respect the initial kind.
12776 A string variable declaration (typed or untyped) declares a variable
12777 whose value is a string. This variable may be used as a string expression.
12778 @smallexample @c projectfile
12779 File_Name := "readme.txt";
12780 Saved_File_Name := File_Name & ".saved";
12784 A string list variable declaration declares a variable whose value is a list
12785 of strings. The list may contain any number (zero or more) of strings.
12787 @smallexample @c projectfile
12789 List_With_One_Element := ("^-gnaty^-gnaty^");
12790 List_With_Two_Elements := List_With_One_Element & "^-gnatg^-gnatg^";
12791 Long_List := ("main.ada", "pack1_.ada", "pack1.ada", "pack2_.ada"
12792 "pack2.ada", "util_.ada", "util.ada");
12796 The same typed variable may not be declared more than once at project level,
12797 and it may not be declared more than once in any package; it is in effect
12800 The same untyped variable may be declared several times. Declarations are
12801 elaborated in the order in which they appear, so the new value replaces
12802 the old one, and any subsequent reference to the variable uses the new value.
12803 However, as noted above, if a variable has been declared as a string, all
12805 declarations must give it a string value. Similarly, if a variable has
12806 been declared as a string list, all subsequent declarations
12807 must give it a string list value.
12809 A @emph{variable reference} may take several forms:
12812 @item The simple variable name, for a variable in the current package (if any)
12813 or in the current project
12814 @item An expanded name, whose prefix is a context name.
12818 A @emph{context} may be one of the following:
12821 @item The name of an existing package in the current project
12822 @item The name of an imported project of the current project
12823 @item The name of an ancestor project (i.e., a project extended by the current
12824 project, either directly or indirectly)
12825 @item An expanded name whose prefix is an imported/parent project name, and
12826 whose selector is a package name in that project.
12830 A variable reference may be used in an expression.
12833 @subsection Attributes
12836 A project (and its packages) may have @emph{attributes} that define
12837 the project's properties. Some attributes have values that are strings;
12838 others have values that are string lists.
12840 There are two categories of attributes: @emph{simple attributes}
12841 and @emph{associative arrays} (@pxref{Associative Array Attributes}).
12843 Legal project attribute names, and attribute names for each legal package are
12844 listed below. Attributes names are case-insensitive.
12846 The following attributes are defined on projects (all are simple attributes):
12848 @multitable @columnfractions .4 .3
12849 @item @emph{Attribute Name}
12851 @item @code{Source_Files}
12853 @item @code{Source_Dirs}
12855 @item @code{Source_List_File}
12857 @item @code{Object_Dir}
12859 @item @code{Exec_Dir}
12861 @item @code{Excluded_Source_Dirs}
12863 @item @code{Excluded_Source_Files}
12865 @item @code{Excluded_Source_List_File}
12867 @item @code{Languages}
12871 @item @code{Library_Dir}
12873 @item @code{Library_Name}
12875 @item @code{Library_Kind}
12877 @item @code{Library_Version}
12879 @item @code{Library_Interface}
12881 @item @code{Library_Auto_Init}
12883 @item @code{Library_Options}
12885 @item @code{Library_Src_Dir}
12887 @item @code{Library_ALI_Dir}
12889 @item @code{Library_GCC}
12891 @item @code{Library_Symbol_File}
12893 @item @code{Library_Symbol_Policy}
12895 @item @code{Library_Reference_Symbol_File}
12897 @item @code{Externally_Built}
12902 The following attributes are defined for package @code{Naming}
12903 (@pxref{Naming Schemes}):
12905 @multitable @columnfractions .4 .2 .2 .2
12906 @item Attribute Name @tab Category @tab Index @tab Value
12907 @item @code{Spec_Suffix}
12908 @tab associative array
12911 @item @code{Body_Suffix}
12912 @tab associative array
12915 @item @code{Separate_Suffix}
12916 @tab simple attribute
12919 @item @code{Casing}
12920 @tab simple attribute
12923 @item @code{Dot_Replacement}
12924 @tab simple attribute
12928 @tab associative array
12932 @tab associative array
12935 @item @code{Specification_Exceptions}
12936 @tab associative array
12939 @item @code{Implementation_Exceptions}
12940 @tab associative array
12946 The following attributes are defined for packages @code{Builder},
12947 @code{Compiler}, @code{Binder},
12948 @code{Linker}, @code{Cross_Reference}, and @code{Finder}
12949 (@pxref{^Switches^Switches^ and Project Files}).
12951 @multitable @columnfractions .4 .2 .2 .2
12952 @item Attribute Name @tab Category @tab Index @tab Value
12953 @item @code{^Default_Switches^Default_Switches^}
12954 @tab associative array
12957 @item @code{^Switches^Switches^}
12958 @tab associative array
12964 In addition, package @code{Compiler} has a single string attribute
12965 @code{Local_Configuration_Pragmas} and package @code{Builder} has a single
12966 string attribute @code{Global_Configuration_Pragmas}.
12969 Each simple attribute has a default value: the empty string (for string-valued
12970 attributes) and the empty list (for string list-valued attributes).
12972 An attribute declaration defines a new value for an attribute.
12974 Examples of simple attribute declarations:
12976 @smallexample @c projectfile
12977 for Object_Dir use "objects";
12978 for Source_Dirs use ("units", "test/drivers");
12982 The syntax of a @dfn{simple attribute declaration} is similar to that of an
12983 attribute definition clause in Ada.
12985 Attributes references may be appear in expressions.
12986 The general form for such a reference is @code{<entity>'<attribute>}:
12987 Associative array attributes are functions. Associative
12988 array attribute references must have an argument that is a string literal.
12992 @smallexample @c projectfile
12994 Naming'Dot_Replacement
12995 Imported_Project'Source_Dirs
12996 Imported_Project.Naming'Casing
12997 Builder'^Default_Switches^Default_Switches^("Ada")
13001 The prefix of an attribute may be:
13003 @item @code{project} for an attribute of the current project
13004 @item The name of an existing package of the current project
13005 @item The name of an imported project
13006 @item The name of a parent project that is extended by the current project
13007 @item An expanded name whose prefix is imported/parent project name,
13008 and whose selector is a package name
13013 @smallexample @c projectfile
13016 for Source_Dirs use project'Source_Dirs & "units";
13017 for Source_Dirs use project'Source_Dirs & "test/drivers"
13023 In the first attribute declaration, initially the attribute @code{Source_Dirs}
13024 has the default value: an empty string list. After this declaration,
13025 @code{Source_Dirs} is a string list of one element: @code{"units"}.
13026 After the second attribute declaration @code{Source_Dirs} is a string list of
13027 two elements: @code{"units"} and @code{"test/drivers"}.
13029 Note: this example is for illustration only. In practice,
13030 the project file would contain only one attribute declaration:
13032 @smallexample @c projectfile
13033 for Source_Dirs use ("units", "test/drivers");
13036 @node Associative Array Attributes
13037 @subsection Associative Array Attributes
13040 Some attributes are defined as @emph{associative arrays}. An associative
13041 array may be regarded as a function that takes a string as a parameter
13042 and delivers a string or string list value as its result.
13044 Here are some examples of single associative array attribute associations:
13046 @smallexample @c projectfile
13047 for Body ("main") use "Main.ada";
13048 for ^Switches^Switches^ ("main.ada")
13050 "^-gnatv^-gnatv^");
13051 for ^Switches^Switches^ ("main.ada")
13052 use Builder'^Switches^Switches^ ("main.ada")
13057 Like untyped variables and simple attributes, associative array attributes
13058 may be declared several times. Each declaration supplies a new value for the
13059 attribute, and replaces the previous setting.
13062 An associative array attribute may be declared as a full associative array
13063 declaration, with the value of the same attribute in an imported or extended
13066 @smallexample @c projectfile
13068 for Default_Switches use Default.Builder'Default_Switches;
13073 In this example, @code{Default} must be either a project imported by the
13074 current project, or the project that the current project extends. If the
13075 attribute is in a package (in this case, in package @code{Builder}), the same
13076 package needs to be specified.
13079 A full associative array declaration replaces any other declaration for the
13080 attribute, including other full associative array declaration. Single
13081 associative array associations may be declare after a full associative
13082 declaration, modifying the value for a single association of the attribute.
13084 @node case Constructions
13085 @subsection @code{case} Constructions
13088 A @code{case} construction is used in a project file to effect conditional
13090 Here is a typical example:
13092 @smallexample @c projectfile
13095 type OS_Type is ("GNU/Linux", "Unix", "NT", "VMS");
13097 OS : OS_Type := external ("OS", "GNU/Linux");
13101 package Compiler is
13103 when "GNU/Linux" | "Unix" =>
13104 for ^Default_Switches^Default_Switches^ ("Ada")
13105 use ("^-gnath^-gnath^");
13107 for ^Default_Switches^Default_Switches^ ("Ada")
13108 use ("^-gnatP^-gnatP^");
13117 The syntax of a @code{case} construction is based on the Ada case statement
13118 (although there is no @code{null} construction for empty alternatives).
13120 The case expression must be a typed string variable.
13121 Each alternative comprises the reserved word @code{when}, either a list of
13122 literal strings separated by the @code{"|"} character or the reserved word
13123 @code{others}, and the @code{"=>"} token.
13124 Each literal string must belong to the string type that is the type of the
13126 An @code{others} alternative, if present, must occur last.
13128 After each @code{=>}, there are zero or more constructions. The only
13129 constructions allowed in a case construction are other case constructions,
13130 attribute declarations and variable declarations. String type declarations and
13131 package declarations are not allowed. Variable declarations are restricted to
13132 variables that have already been declared before the case construction.
13134 The value of the case variable is often given by an external reference
13135 (@pxref{External References in Project Files}).
13137 @c ****************************************
13138 @c * Objects and Sources in Project Files *
13139 @c ****************************************
13141 @node Objects and Sources in Project Files
13142 @section Objects and Sources in Project Files
13145 * Object Directory::
13147 * Source Directories::
13148 * Source File Names::
13152 Each project has exactly one object directory and one or more source
13153 directories. The source directories must contain at least one source file,
13154 unless the project file explicitly specifies that no source files are present
13155 (@pxref{Source File Names}).
13157 @node Object Directory
13158 @subsection Object Directory
13161 The object directory for a project is the directory containing the compiler's
13162 output (such as @file{ALI} files and object files) for the project's immediate
13165 The object directory is given by the value of the attribute @code{Object_Dir}
13166 in the project file.
13168 @smallexample @c projectfile
13169 for Object_Dir use "objects";
13173 The attribute @code{Object_Dir} has a string value, the path name of the object
13174 directory. The path name may be absolute or relative to the directory of the
13175 project file. This directory must already exist, and be readable and writable.
13177 By default, when the attribute @code{Object_Dir} is not given an explicit value
13178 or when its value is the empty string, the object directory is the same as the
13179 directory containing the project file.
13181 @node Exec Directory
13182 @subsection Exec Directory
13185 The exec directory for a project is the directory containing the executables
13186 for the project's main subprograms.
13188 The exec directory is given by the value of the attribute @code{Exec_Dir}
13189 in the project file.
13191 @smallexample @c projectfile
13192 for Exec_Dir use "executables";
13196 The attribute @code{Exec_Dir} has a string value, the path name of the exec
13197 directory. The path name may be absolute or relative to the directory of the
13198 project file. This directory must already exist, and be writable.
13200 By default, when the attribute @code{Exec_Dir} is not given an explicit value
13201 or when its value is the empty string, the exec directory is the same as the
13202 object directory of the project file.
13204 @node Source Directories
13205 @subsection Source Directories
13208 The source directories of a project are specified by the project file
13209 attribute @code{Source_Dirs}.
13211 This attribute's value is a string list. If the attribute is not given an
13212 explicit value, then there is only one source directory, the one where the
13213 project file resides.
13215 A @code{Source_Dirs} attribute that is explicitly defined to be the empty list,
13218 @smallexample @c projectfile
13219 for Source_Dirs use ();
13223 indicates that the project contains no source files.
13225 Otherwise, each string in the string list designates one or more
13226 source directories.
13228 @smallexample @c projectfile
13229 for Source_Dirs use ("sources", "test/drivers");
13233 If a string in the list ends with @code{"/**"}, then the directory whose path
13234 name precedes the two asterisks, as well as all its subdirectories
13235 (recursively), are source directories.
13237 @smallexample @c projectfile
13238 for Source_Dirs use ("/system/sources/**");
13242 Here the directory @code{/system/sources} and all of its subdirectories
13243 (recursively) are source directories.
13245 To specify that the source directories are the directory of the project file
13246 and all of its subdirectories, you can declare @code{Source_Dirs} as follows:
13247 @smallexample @c projectfile
13248 for Source_Dirs use ("./**");
13252 Each of the source directories must exist and be readable.
13254 @node Source File Names
13255 @subsection Source File Names
13258 In a project that contains source files, their names may be specified by the
13259 attributes @code{Source_Files} (a string list) or @code{Source_List_File}
13260 (a string). Source file names never include any directory information.
13262 If the attribute @code{Source_Files} is given an explicit value, then each
13263 element of the list is a source file name.
13265 @smallexample @c projectfile
13266 for Source_Files use ("main.adb");
13267 for Source_Files use ("main.adb", "pack1.ads", "pack2.adb");
13271 If the attribute @code{Source_Files} is not given an explicit value,
13272 but the attribute @code{Source_List_File} is given a string value,
13273 then the source file names are contained in the text file whose path name
13274 (absolute or relative to the directory of the project file) is the
13275 value of the attribute @code{Source_List_File}.
13277 Each line in the file that is not empty or is not a comment
13278 contains a source file name.
13280 @smallexample @c projectfile
13281 for Source_List_File use "source_list.txt";
13285 By default, if neither the attribute @code{Source_Files} nor the attribute
13286 @code{Source_List_File} is given an explicit value, then each file in the
13287 source directories that conforms to the project's naming scheme
13288 (@pxref{Naming Schemes}) is an immediate source of the project.
13290 A warning is issued if both attributes @code{Source_Files} and
13291 @code{Source_List_File} are given explicit values. In this case, the attribute
13292 @code{Source_Files} prevails.
13294 Each source file name must be the name of one existing source file
13295 in one of the source directories.
13297 A @code{Source_Files} attribute whose value is an empty list
13298 indicates that there are no source files in the project.
13300 If the order of the source directories is known statically, that is if
13301 @code{"/**"} is not used in the string list @code{Source_Dirs}, then there may
13302 be several files with the same source file name. In this case, only the file
13303 in the first directory is considered as an immediate source of the project
13304 file. If the order of the source directories is not known statically, it is
13305 an error to have several files with the same source file name.
13307 Projects can be specified to have no Ada source
13308 files: the value of (@code{Source_Dirs} or @code{Source_Files} may be an empty
13309 list, or the @code{"Ada"} may be absent from @code{Languages}:
13311 @smallexample @c projectfile
13312 for Source_Dirs use ();
13313 for Source_Files use ();
13314 for Languages use ("C", "C++");
13318 Otherwise, a project must contain at least one immediate source.
13320 Projects with no source files are useful as template packages
13321 (@pxref{Packages in Project Files}) for other projects; in particular to
13322 define a package @code{Naming} (@pxref{Naming Schemes}).
13324 @c ****************************
13325 @c * Importing Projects *
13326 @c ****************************
13328 @node Importing Projects
13329 @section Importing Projects
13330 @cindex @code{ADA_PROJECT_PATH}
13333 An immediate source of a project P may depend on source files that
13334 are neither immediate sources of P nor in the predefined library.
13335 To get this effect, P must @emph{import} the projects that contain the needed
13338 @smallexample @c projectfile
13340 with "project1", "utilities.gpr";
13341 with "/namings/apex.gpr";
13348 As can be seen in this example, the syntax for importing projects is similar
13349 to the syntax for importing compilation units in Ada. However, project files
13350 use literal strings instead of names, and the @code{with} clause identifies
13351 project files rather than packages.
13353 Each literal string is the file name or path name (absolute or relative) of a
13354 project file. If a string corresponds to a file name, with no path or a
13355 relative path, then its location is determined by the @emph{project path}. The
13356 latter can be queried using @code{gnatls -v}. It contains:
13360 In first position, the directory containing the current project file.
13362 In last position, the default project directory. This default project directory
13363 is part of the GNAT installation and is the standard place to install project
13364 files giving access to standard support libraries.
13366 @ref{Installing a library}
13370 In between, all the directories referenced in the
13371 ^environment variable^logical name^ @env{ADA_PROJECT_PATH} if it exists.
13375 If a relative pathname is used, as in
13377 @smallexample @c projectfile
13382 then the full path for the project is constructed by concatenating this
13383 relative path to those in the project path, in order, until a matching file is
13384 found. Any symbolic link will be fully resolved in the directory of the
13385 importing project file before the imported project file is examined.
13387 If the @code{with}'ed project file name does not have an extension,
13388 the default is @file{^.gpr^.GPR^}. If a file with this extension is not found,
13389 then the file name as specified in the @code{with} clause (no extension) will
13390 be used. In the above example, if a file @code{project1.gpr} is found, then it
13391 will be used; otherwise, if a file @code{^project1^PROJECT1^} exists
13392 then it will be used; if neither file exists, this is an error.
13394 A warning is issued if the name of the project file does not match the
13395 name of the project; this check is case insensitive.
13397 Any source file that is an immediate source of the imported project can be
13398 used by the immediate sources of the importing project, transitively. Thus
13399 if @code{A} imports @code{B}, and @code{B} imports @code{C}, the immediate
13400 sources of @code{A} may depend on the immediate sources of @code{C}, even if
13401 @code{A} does not import @code{C} explicitly. However, this is not recommended,
13402 because if and when @code{B} ceases to import @code{C}, some sources in
13403 @code{A} will no longer compile.
13405 A side effect of this capability is that normally cyclic dependencies are not
13406 permitted: if @code{A} imports @code{B} (directly or indirectly) then @code{B}
13407 is not allowed to import @code{A}. However, there are cases when cyclic
13408 dependencies would be beneficial. For these cases, another form of import
13409 between projects exists, the @code{limited with}: a project @code{A} that
13410 imports a project @code{B} with a straight @code{with} may also be imported,
13411 directly or indirectly, by @code{B} on the condition that imports from @code{B}
13412 to @code{A} include at least one @code{limited with}.
13414 @smallexample @c 0projectfile
13420 limited with "../a/a.gpr";
13428 limited with "../a/a.gpr";
13434 In the above legal example, there are two project cycles:
13437 @item A -> C -> D -> A
13441 In each of these cycle there is one @code{limited with}: import of @code{A}
13442 from @code{B} and import of @code{A} from @code{D}.
13444 The difference between straight @code{with} and @code{limited with} is that
13445 the name of a project imported with a @code{limited with} cannot be used in the
13446 project that imports it. In particular, its packages cannot be renamed and
13447 its variables cannot be referred to.
13449 An exception to the above rules for @code{limited with} is that for the main
13450 project specified to @command{gnatmake} or to the @command{GNAT} driver a
13451 @code{limited with} is equivalent to a straight @code{with}. For example,
13452 in the example above, projects @code{B} and @code{D} could not be main
13453 projects for @command{gnatmake} or to the @command{GNAT} driver, because they
13454 each have a @code{limited with} that is the only one in a cycle of importing
13457 @c *********************
13458 @c * Project Extension *
13459 @c *********************
13461 @node Project Extension
13462 @section Project Extension
13465 During development of a large system, it is sometimes necessary to use
13466 modified versions of some of the source files, without changing the original
13467 sources. This can be achieved through the @emph{project extension} facility.
13469 @smallexample @c projectfile
13470 project Modified_Utilities extends "/baseline/utilities.gpr" is @dots{}
13474 A project extension declaration introduces an extending project
13475 (the @emph{child}) and a project being extended (the @emph{parent}).
13477 By default, a child project inherits all the sources of its parent.
13478 However, inherited sources can be overridden: a unit in a parent is hidden
13479 by a unit of the same name in the child.
13481 Inherited sources are considered to be sources (but not immediate sources)
13482 of the child project; see @ref{Project File Syntax}.
13484 An inherited source file retains any switches specified in the parent project.
13486 For example if the project @code{Utilities} contains the spec and the
13487 body of an Ada package @code{Util_IO}, then the project
13488 @code{Modified_Utilities} can contain a new body for package @code{Util_IO}.
13489 The original body of @code{Util_IO} will not be considered in program builds.
13490 However, the package spec will still be found in the project
13493 A child project can have only one parent, except when it is qualified as
13494 abstract. But it may import any number of other projects.
13496 A project is not allowed to import directly or indirectly at the same time a
13497 child project and any of its ancestors.
13499 @c *******************************
13500 @c * Project Hierarchy Extension *
13501 @c *******************************
13503 @node Project Hierarchy Extension
13504 @section Project Hierarchy Extension
13507 When extending a large system spanning multiple projects, it is often
13508 inconvenient to extend every project in the hierarchy that is impacted by a
13509 small change introduced. In such cases, it is possible to create a virtual
13510 extension of entire hierarchy using @code{extends all} relationship.
13512 When the project is extended using @code{extends all} inheritance, all projects
13513 that are imported by it, both directly and indirectly, are considered virtually
13514 extended. That is, the Project Manager creates "virtual projects"
13515 that extend every project in the hierarchy; all these virtual projects have
13516 no sources of their own and have as object directory the object directory of
13517 the root of "extending all" project.
13519 It is possible to explicitly extend one or more projects in the hierarchy
13520 in order to modify the sources. These extending projects must be imported by
13521 the "extending all" project, which will replace the corresponding virtual
13522 projects with the explicit ones.
13524 When building such a project hierarchy extension, the Project Manager will
13525 ensure that both modified sources and sources in virtual extending projects
13526 that depend on them, are recompiled.
13528 By means of example, consider the following hierarchy of projects.
13532 project A, containing package P1
13534 project B importing A and containing package P2 which depends on P1
13536 project C importing B and containing package P3 which depends on P2
13540 We want to modify packages P1 and P3.
13542 This project hierarchy will need to be extended as follows:
13546 Create project A1 that extends A, placing modified P1 there:
13548 @smallexample @c 0projectfile
13549 project A1 extends "(@dots{})/A" is
13554 Create project C1 that "extends all" C and imports A1, placing modified
13557 @smallexample @c 0projectfile
13558 with "(@dots{})/A1";
13559 project C1 extends all "(@dots{})/C" is
13564 When you build project C1, your entire modified project space will be
13565 recompiled, including the virtual project B1 that has been impacted by the
13566 "extending all" inheritance of project C.
13568 Note that if a Library Project in the hierarchy is virtually extended,
13569 the virtual project that extends the Library Project is not a Library Project.
13571 @c ****************************************
13572 @c * External References in Project Files *
13573 @c ****************************************
13575 @node External References in Project Files
13576 @section External References in Project Files
13579 A project file may contain references to external variables; such references
13580 are called @emph{external references}.
13582 An external variable is either defined as part of the environment (an
13583 environment variable in Unix, for example) or else specified on the command
13584 line via the @option{^-X^/EXTERNAL_REFERENCE=^@emph{vbl}=@emph{value}} switch.
13585 If both, then the command line value is used.
13587 The value of an external reference is obtained by means of the built-in
13588 function @code{external}, which returns a string value.
13589 This function has two forms:
13591 @item @code{external (external_variable_name)}
13592 @item @code{external (external_variable_name, default_value)}
13596 Each parameter must be a string literal. For example:
13598 @smallexample @c projectfile
13600 external ("OS", "GNU/Linux")
13604 In the form with one parameter, the function returns the value of
13605 the external variable given as parameter. If this name is not present in the
13606 environment, the function returns an empty string.
13608 In the form with two string parameters, the second argument is
13609 the value returned when the variable given as the first argument is not
13610 present in the environment. In the example above, if @code{"OS"} is not
13611 the name of ^an environment variable^a logical name^ and is not passed on
13612 the command line, then the returned value is @code{"GNU/Linux"}.
13614 An external reference may be part of a string expression or of a string
13615 list expression, and can therefore appear in a variable declaration or
13616 an attribute declaration.
13618 @smallexample @c projectfile
13620 type Mode_Type is ("Debug", "Release");
13621 Mode : Mode_Type := external ("MODE");
13628 @c *****************************
13629 @c * Packages in Project Files *
13630 @c *****************************
13632 @node Packages in Project Files
13633 @section Packages in Project Files
13636 A @emph{package} defines the settings for project-aware tools within a
13638 For each such tool one can declare a package; the names for these
13639 packages are preset (@pxref{Packages}).
13640 A package may contain variable declarations, attribute declarations, and case
13643 @smallexample @c projectfile
13646 package Builder is -- used by gnatmake
13647 for ^Default_Switches^Default_Switches^ ("Ada")
13656 The syntax of package declarations mimics that of package in Ada.
13658 Most of the packages have an attribute
13659 @code{^Default_Switches^Default_Switches^}.
13660 This attribute is an associative array, and its value is a string list.
13661 The index of the associative array is the name of a programming language (case
13662 insensitive). This attribute indicates the ^switch^switch^
13663 or ^switches^switches^ to be used
13664 with the corresponding tool.
13666 Some packages also have another attribute, @code{^Switches^Switches^},
13667 an associative array whose value is a string list.
13668 The index is the name of a source file.
13669 This attribute indicates the ^switch^switch^
13670 or ^switches^switches^ to be used by the corresponding
13671 tool when dealing with this specific file.
13673 Further information on these ^switch^switch^-related attributes is found in
13674 @ref{^Switches^Switches^ and Project Files}.
13676 A package may be declared as a @emph{renaming} of another package; e.g., from
13677 the project file for an imported project.
13679 @smallexample @c projectfile
13681 with "/global/apex.gpr";
13683 package Naming renames Apex.Naming;
13690 Packages that are renamed in other project files often come from project files
13691 that have no sources: they are just used as templates. Any modification in the
13692 template will be reflected automatically in all the project files that rename
13693 a package from the template.
13695 In addition to the tool-oriented packages, you can also declare a package
13696 named @code{Naming} to establish specialized source file naming conventions
13697 (@pxref{Naming Schemes}).
13699 @c ************************************
13700 @c * Variables from Imported Projects *
13701 @c ************************************
13703 @node Variables from Imported Projects
13704 @section Variables from Imported Projects
13707 An attribute or variable defined in an imported or parent project can
13708 be used in expressions in the importing / extending project.
13709 Such an attribute or variable is denoted by an expanded name whose prefix
13710 is either the name of the project or the expanded name of a package within
13713 @smallexample @c projectfile
13716 project Main extends "base" is
13717 Var1 := Imported.Var;
13718 Var2 := Base.Var & ".new";
13723 for ^Default_Switches^Default_Switches^ ("Ada")
13724 use Imported.Builder'Ada_^Switches^Switches^ &
13725 "^-gnatg^-gnatg^" &
13731 package Compiler is
13732 for ^Default_Switches^Default_Switches^ ("Ada")
13733 use Base.Compiler'Ada_^Switches^Switches^;
13744 The value of @code{Var1} is a copy of the variable @code{Var} defined
13745 in the project file @file{"imported.gpr"}
13747 the value of @code{Var2} is a copy of the value of variable @code{Var}
13748 defined in the project file @file{base.gpr}, concatenated with @code{".new"}
13750 attribute @code{^Default_Switches^Default_Switches^ ("Ada")} in package
13751 @code{Builder} is a string list that includes in its value a copy of the value
13752 of @code{Ada_^Switches^Switches^} defined in the @code{Builder} package
13753 in project file @file{imported.gpr} plus two new elements:
13754 @option{"^-gnatg^-gnatg^"}
13755 and @option{"^-v^-v^"};
13757 attribute @code{^Default_Switches^Default_Switches^ ("Ada")} in package
13758 @code{Compiler} is a copy of the variable @code{Ada_^Switches^Switches^}
13759 defined in the @code{Compiler} package in project file @file{base.gpr},
13760 the project being extended.
13763 @c ******************
13764 @c * Naming Schemes *
13765 @c ******************
13767 @node Naming Schemes
13768 @section Naming Schemes
13771 Sometimes an Ada software system is ported from a foreign compilation
13772 environment to GNAT, and the file names do not use the default GNAT
13773 conventions. Instead of changing all the file names (which for a variety
13774 of reasons might not be possible), you can define the relevant file
13775 naming scheme in the @code{Naming} package in your project file.
13778 Note that the use of pragmas described in
13779 @ref{Alternative File Naming Schemes} by mean of a configuration
13780 pragmas file is not supported when using project files. You must use
13781 the features described in this paragraph. You can however use specify
13782 other configuration pragmas (@pxref{Specifying Configuration Pragmas}).
13785 For example, the following
13786 package models the Apex file naming rules:
13788 @smallexample @c projectfile
13791 for Casing use "lowercase";
13792 for Dot_Replacement use ".";
13793 for Spec_Suffix ("Ada") use ".1.ada";
13794 for Body_Suffix ("Ada") use ".2.ada";
13801 For example, the following package models the HP Ada file naming rules:
13803 @smallexample @c projectfile
13806 for Casing use "lowercase";
13807 for Dot_Replacement use "__";
13808 for Spec_Suffix ("Ada") use "_.^ada^ada^";
13809 for Body_Suffix ("Ada") use ".^ada^ada^";
13815 (Note that @code{Casing} is @code{"lowercase"} because GNAT gets the file
13816 names in lower case)
13820 You can define the following attributes in package @code{Naming}:
13824 @item @code{Casing}
13825 This must be a string with one of the three values @code{"lowercase"},
13826 @code{"uppercase"} or @code{"mixedcase"}; these strings are case insensitive.
13829 If @code{Casing} is not specified, then the default is @code{"lowercase"}.
13831 @item @code{Dot_Replacement}
13832 This must be a string whose value satisfies the following conditions:
13835 @item It must not be empty
13836 @item It cannot start or end with an alphanumeric character
13837 @item It cannot be a single underscore
13838 @item It cannot start with an underscore followed by an alphanumeric
13839 @item It cannot contain a dot @code{'.'} except if the entire string
13844 If @code{Dot_Replacement} is not specified, then the default is @code{"-"}.
13846 @item @code{Spec_Suffix}
13847 This is an associative array (indexed by the programming language name, case
13848 insensitive) whose value is a string that must satisfy the following
13852 @item It must not be empty
13853 @item It must include at least one dot
13856 If @code{Spec_Suffix ("Ada")} is not specified, then the default is
13857 @code{"^.ads^.ADS^"}.
13859 @item @code{Body_Suffix}
13860 This is an associative array (indexed by the programming language name, case
13861 insensitive) whose value is a string that must satisfy the following
13865 @item It must not be empty
13866 @item It must include at least one dot
13867 @item It cannot be the same as @code{Spec_Suffix ("Ada")}
13870 If @code{Body_Suffix ("Ada")} and @code{Spec_Suffix ("Ada")} end with the
13871 same string, then a file name that ends with the longest of these two suffixes
13872 will be a body if the longest suffix is @code{Body_Suffix ("Ada")} or a spec
13873 if the longest suffix is @code{Spec_Suffix ("Ada")}.
13875 If the suffix does not start with a '.', a file with a name exactly equal
13876 to the suffix will also be part of the project (for instance if you define
13877 the suffix as @code{Makefile}, a file called @file{Makefile} will be part
13878 of the project. This is not interesting in general when using projects to
13879 compile. However, it might become useful when a project is also used to
13880 find the list of source files in an editor, like the GNAT Programming System
13883 If @code{Body_Suffix ("Ada")} is not specified, then the default is
13884 @code{"^.adb^.ADB^"}.
13886 @item @code{Separate_Suffix}
13887 This must be a string whose value satisfies the same conditions as
13888 @code{Body_Suffix}. The same "longest suffix" rules apply.
13891 If @code{Separate_Suffix ("Ada")} is not specified, then it defaults to same
13892 value as @code{Body_Suffix ("Ada")}.
13896 You can use the associative array attribute @code{Spec} to define
13897 the source file name for an individual Ada compilation unit's spec. The array
13898 index must be a string literal that identifies the Ada unit (case insensitive).
13899 The value of this attribute must be a string that identifies the file that
13900 contains this unit's spec (case sensitive or insensitive depending on the
13903 @smallexample @c projectfile
13904 for Spec ("MyPack.MyChild") use "mypack.mychild.spec";
13907 When the source file contains several units, you can indicate at what
13908 position the unit occurs in the file, with the following. The first unit
13909 in the file has index 1
13911 @smallexample @c projectfile
13912 for Body ("top") use "foo.a" at 1;
13913 for Body ("foo") use "foo.a" at 2;
13918 You can use the associative array attribute @code{Body} to
13919 define the source file name for an individual Ada compilation unit's body
13920 (possibly a subunit). The array index must be a string literal that identifies
13921 the Ada unit (case insensitive). The value of this attribute must be a string
13922 that identifies the file that contains this unit's body or subunit (case
13923 sensitive or insensitive depending on the operating system).
13925 @smallexample @c projectfile
13926 for Body ("MyPack.MyChild") use "mypack.mychild.body";
13930 @c ********************
13931 @c * Library Projects *
13932 @c ********************
13934 @node Library Projects
13935 @section Library Projects
13938 @emph{Library projects} are projects whose object code is placed in a library.
13939 (Note that this facility is not yet supported on all platforms).
13941 @code{gnatmake} or @code{gprbuild} will collect all object files into a
13942 single archive, which might either be a shared or a static library. This
13943 library can later on be linked with multiple executables, potentially
13944 reducing their sizes.
13946 If your project file specifies languages other than Ada, but you are still
13947 using @code{gnatmake} to compile and link, the latter will not try to
13948 compile your sources other than Ada (you should use @code{gprbuild} if that
13949 is your intent). However, @code{gnatmake} will automatically link all object
13950 files found in the object directory, whether or not they were compiled from
13951 an Ada source file. This specific behavior only applies when multiple
13952 languages are specified.
13954 To create a library project, you need to define in its project file
13955 two project-level attributes: @code{Library_Name} and @code{Library_Dir}.
13956 Additionally, you may define other library-related attributes such as
13957 @code{Library_Kind}, @code{Library_Version}, @code{Library_Interface},
13958 @code{Library_Auto_Init}, @code{Library_Options} and @code{Library_GCC}.
13960 The @code{Library_Name} attribute has a string value. There is no restriction
13961 on the name of a library. It is the responsibility of the developer to
13962 choose a name that will be accepted by the platform. It is recommended to
13963 choose names that could be Ada identifiers; such names are almost guaranteed
13964 to be acceptable on all platforms.
13966 The @code{Library_Dir} attribute has a string value that designates the path
13967 (absolute or relative) of the directory where the library will reside.
13968 It must designate an existing directory, and this directory must be writable,
13969 different from the project's object directory and from any source directory
13970 in the project tree.
13972 If both @code{Library_Name} and @code{Library_Dir} are specified and
13973 are legal, then the project file defines a library project. The optional
13974 library-related attributes are checked only for such project files.
13976 The @code{Library_Kind} attribute has a string value that must be one of the
13977 following (case insensitive): @code{"static"}, @code{"dynamic"} or
13978 @code{"relocatable"} (which is a synonym for @code{"dynamic"}). If this
13979 attribute is not specified, the library is a static library, that is
13980 an archive of object files that can be potentially linked into a
13981 static executable. Otherwise, the library may be dynamic or
13982 relocatable, that is a library that is loaded only at the start of execution.
13984 If you need to build both a static and a dynamic library, you should use two
13985 different object directories, since in some cases some extra code needs to
13986 be generated for the latter. For such cases, it is recommended to either use
13987 two different project files, or a single one which uses external variables
13988 to indicate what kind of library should be build.
13990 The @code{Library_ALI_Dir} attribute may be specified to indicate the
13991 directory where the ALI files of the library will be copied. When it is
13992 not specified, the ALI files are copied to the directory specified in
13993 attribute @code{Library_Dir}. The directory specified by @code{Library_ALI_Dir}
13994 must be writable and different from the project's object directory and from
13995 any source directory in the project tree.
13997 The @code{Library_Version} attribute has a string value whose interpretation
13998 is platform dependent. It has no effect on VMS and Windows. On Unix, it is
13999 used only for dynamic/relocatable libraries as the internal name of the
14000 library (the @code{"soname"}). If the library file name (built from the
14001 @code{Library_Name}) is different from the @code{Library_Version}, then the
14002 library file will be a symbolic link to the actual file whose name will be
14003 @code{Library_Version}.
14007 @smallexample @c projectfile
14013 for Library_Dir use "lib_dir";
14014 for Library_Name use "dummy";
14015 for Library_Kind use "relocatable";
14016 for Library_Version use "libdummy.so." & Version;
14023 Directory @file{lib_dir} will contain the internal library file whose name
14024 will be @file{libdummy.so.1}, and @file{libdummy.so} will be a symbolic link to
14025 @file{libdummy.so.1}.
14027 When @command{gnatmake} detects that a project file
14028 is a library project file, it will check all immediate sources of the project
14029 and rebuild the library if any of the sources have been recompiled.
14031 Standard project files can import library project files. In such cases,
14032 the libraries will only be rebuilt if some of its sources are recompiled
14033 because they are in the closure of some other source in an importing project.
14034 Sources of the library project files that are not in such a closure will
14035 not be checked, unless the full library is checked, because one of its sources
14036 needs to be recompiled.
14038 For instance, assume the project file @code{A} imports the library project file
14039 @code{L}. The immediate sources of A are @file{a1.adb}, @file{a2.ads} and
14040 @file{a2.adb}. The immediate sources of L are @file{l1.ads}, @file{l1.adb},
14041 @file{l2.ads}, @file{l2.adb}.
14043 If @file{l1.adb} has been modified, then the library associated with @code{L}
14044 will be rebuilt when compiling all the immediate sources of @code{A} only
14045 if @file{a1.ads}, @file{a2.ads} or @file{a2.adb} includes a statement
14048 To be sure that all the sources in the library associated with @code{L} are
14049 up to date, and that all the sources of project @code{A} are also up to date,
14050 the following two commands needs to be used:
14057 When a library is built or rebuilt, an attempt is made first to delete all
14058 files in the library directory.
14059 All @file{ALI} files will also be copied from the object directory to the
14060 library directory. To build executables, @command{gnatmake} will use the
14061 library rather than the individual object files.
14064 It is also possible to create library project files for third-party libraries
14065 that are precompiled and cannot be compiled locally thanks to the
14066 @code{externally_built} attribute. (See @ref{Installing a library}).
14069 @c *******************************
14070 @c * Stand-alone Library Projects *
14071 @c *******************************
14073 @node Stand-alone Library Projects
14074 @section Stand-alone Library Projects
14077 A Stand-alone Library is a library that contains the necessary code to
14078 elaborate the Ada units that are included in the library. A Stand-alone
14079 Library is suitable to be used in an executable when the main is not
14080 in Ada. However, Stand-alone Libraries may also be used with an Ada main
14083 A Stand-alone Library Project is a Library Project where the library is
14084 a Stand-alone Library.
14086 To be a Stand-alone Library Project, in addition to the two attributes
14087 that make a project a Library Project (@code{Library_Name} and
14088 @code{Library_Dir}, see @ref{Library Projects}), the attribute
14089 @code{Library_Interface} must be defined.
14091 @smallexample @c projectfile
14093 for Library_Dir use "lib_dir";
14094 for Library_Name use "dummy";
14095 for Library_Interface use ("int1", "int1.child");
14099 Attribute @code{Library_Interface} has a nonempty string list value,
14100 each string in the list designating a unit contained in an immediate source
14101 of the project file.
14103 When a Stand-alone Library is built, first the binder is invoked to build
14104 a package whose name depends on the library name
14105 (^b~dummy.ads/b^B$DUMMY.ADS/B^ in the example above).
14106 This binder-generated package includes initialization and
14107 finalization procedures whose
14108 names depend on the library name (dummyinit and dummyfinal in the example
14109 above). The object corresponding to this package is included in the library.
14111 A dynamic or relocatable Stand-alone Library is automatically initialized
14112 if automatic initialization of Stand-alone Libraries is supported on the
14113 platform and if attribute @code{Library_Auto_Init} is not specified or
14114 is specified with the value "true". A static Stand-alone Library is never
14115 automatically initialized.
14117 Single string attribute @code{Library_Auto_Init} may be specified with only
14118 two possible values: "false" or "true" (case-insensitive). Specifying
14119 "false" for attribute @code{Library_Auto_Init} will prevent automatic
14120 initialization of dynamic or relocatable libraries.
14122 When a non-automatically initialized Stand-alone Library is used
14123 in an executable, its initialization procedure must be called before
14124 any service of the library is used.
14125 When the main subprogram is in Ada, it may mean that the initialization
14126 procedure has to be called during elaboration of another package.
14128 For a Stand-Alone Library, only the @file{ALI} files of the Interface Units
14129 (those that are listed in attribute @code{Library_Interface}) are copied to
14130 the Library Directory. As a consequence, only the Interface Units may be
14131 imported from Ada units outside of the library. If other units are imported,
14132 the binding phase will fail.
14134 When a Stand-Alone Library is bound, the switches that are specified in
14135 the attribute @code{Default_Switches ("Ada")} in package @code{Binder} are
14136 used in the call to @command{gnatbind}.
14138 The string list attribute @code{Library_Options} may be used to specified
14139 additional switches to the call to @command{gcc} to link the library.
14141 The attribute @code{Library_Src_Dir}, may be specified for a
14142 Stand-Alone Library. @code{Library_Src_Dir} is a simple attribute that has a
14143 single string value. Its value must be the path (absolute or relative to the
14144 project directory) of an existing directory. This directory cannot be the
14145 object directory or one of the source directories, but it can be the same as
14146 the library directory. The sources of the Interface
14147 Units of the library, necessary to an Ada client of the library, will be
14148 copied to the designated directory, called Interface Copy directory.
14149 These sources includes the specs of the Interface Units, but they may also
14150 include bodies and subunits, when pragmas @code{Inline} or @code{Inline_Always}
14151 are used, or when there is a generic units in the spec. Before the sources
14152 are copied to the Interface Copy directory, an attempt is made to delete all
14153 files in the Interface Copy directory.
14155 @c *************************************
14156 @c * Switches Related to Project Files *
14157 @c *************************************
14158 @node Switches Related to Project Files
14159 @section Switches Related to Project Files
14162 The following switches are used by GNAT tools that support project files:
14166 @item ^-P^/PROJECT_FILE=^@var{project}
14167 @cindex @option{^-P^/PROJECT_FILE^} (any project-aware tool)
14168 Indicates the name of a project file. This project file will be parsed with
14169 the verbosity indicated by @option{^-vP^MESSAGE_PROJECT_FILES=^@emph{x}},
14170 if any, and using the external references indicated
14171 by @option{^-X^/EXTERNAL_REFERENCE^} switches, if any.
14173 There may zero, one or more spaces between @option{-P} and @var{project}.
14177 There must be only one @option{^-P^/PROJECT_FILE^} switch on the command line.
14180 Since the Project Manager parses the project file only after all the switches
14181 on the command line are checked, the order of the switches
14182 @option{^-P^/PROJECT_FILE^},
14183 @option{^-vP^/MESSAGES_PROJECT_FILE=^@emph{x}}
14184 or @option{^-X^/EXTERNAL_REFERENCE^} is not significant.
14186 @item ^-X^/EXTERNAL_REFERENCE=^@var{name=value}
14187 @cindex @option{^-X^/EXTERNAL_REFERENCE^} (any project-aware tool)
14188 Indicates that external variable @var{name} has the value @var{value}.
14189 The Project Manager will use this value for occurrences of
14190 @code{external(name)} when parsing the project file.
14194 If @var{name} or @var{value} includes a space, then @var{name=value} should be
14195 put between quotes.
14203 Several @option{^-X^/EXTERNAL_REFERENCE^} switches can be used simultaneously.
14204 If several @option{^-X^/EXTERNAL_REFERENCE^} switches specify the same
14205 @var{name}, only the last one is used.
14208 An external variable specified with a @option{^-X^/EXTERNAL_REFERENCE^} switch
14209 takes precedence over the value of the same name in the environment.
14211 @item ^-vP^/MESSAGES_PROJECT_FILE=^@emph{x}
14212 @cindex @option{^-vP^/MESSAGES_PROJECT_FILE^} (any project-aware tool)
14213 Indicates the verbosity of the parsing of GNAT project files.
14216 @option{-vP0} means Default;
14217 @option{-vP1} means Medium;
14218 @option{-vP2} means High.
14222 There are three possible options for this qualifier: DEFAULT, MEDIUM and
14227 The default is ^Default^DEFAULT^: no output for syntactically correct
14230 If several @option{^-vP^/MESSAGES_PROJECT_FILE=^@emph{x}} switches are present,
14231 only the last one is used.
14233 @item ^-aP^/ADD_PROJECT_SEARCH_DIR=^<dir>
14234 @cindex @option{^-aP^/ADD_PROJECT_SEARCH_DIR=^} (any project-aware tool)
14235 Add directory <dir> at the beginning of the project search path, in order,
14236 after the current working directory.
14240 @cindex @option{-eL} (any project-aware tool)
14241 Follow all symbolic links when processing project files.
14244 @item ^--subdirs^/SUBDIRS^=<subdir>
14245 @cindex @option{^--subdirs^/SUBDIRS^=} (gnatmake and gnatclean)
14246 This switch is recognized by gnatmake and gnatclean. It indicate that the real
14247 directories (except the source directories) are the subdirectories <subdir>
14248 of the directories specified in the project files. This applies in particular
14249 to object directories, library directories and exec directories. If the
14250 subdirectories do not exist, they are created automatically.
14254 @c **********************************
14255 @c * Tools Supporting Project Files *
14256 @c **********************************
14258 @node Tools Supporting Project Files
14259 @section Tools Supporting Project Files
14262 * gnatmake and Project Files::
14263 * The GNAT Driver and Project Files::
14266 @node gnatmake and Project Files
14267 @subsection gnatmake and Project Files
14270 This section covers several topics related to @command{gnatmake} and
14271 project files: defining ^switches^switches^ for @command{gnatmake}
14272 and for the tools that it invokes; specifying configuration pragmas;
14273 the use of the @code{Main} attribute; building and rebuilding library project
14277 * ^Switches^Switches^ and Project Files::
14278 * Specifying Configuration Pragmas::
14279 * Project Files and Main Subprograms::
14280 * Library Project Files::
14283 @node ^Switches^Switches^ and Project Files
14284 @subsubsection ^Switches^Switches^ and Project Files
14287 It is not currently possible to specify VMS style qualifiers in the project
14288 files; only Unix style ^switches^switches^ may be specified.
14292 For each of the packages @code{Builder}, @code{Compiler}, @code{Binder}, and
14293 @code{Linker}, you can specify a @code{^Default_Switches^Default_Switches^}
14294 attribute, a @code{^Switches^Switches^} attribute, or both;
14295 as their names imply, these ^switch^switch^-related
14296 attributes affect the ^switches^switches^ that are used for each of these GNAT
14298 @command{gnatmake} is invoked. As will be explained below, these
14299 component-specific ^switches^switches^ precede
14300 the ^switches^switches^ provided on the @command{gnatmake} command line.
14302 The @code{^Default_Switches^Default_Switches^} attribute is an associative
14303 array indexed by language name (case insensitive) whose value is a string list.
14306 @smallexample @c projectfile
14308 package Compiler is
14309 for ^Default_Switches^Default_Switches^ ("Ada")
14310 use ("^-gnaty^-gnaty^",
14317 The @code{^Switches^Switches^} attribute is also an associative array,
14318 indexed by a file name (which may or may not be case sensitive, depending
14319 on the operating system) whose value is a string list. For example:
14321 @smallexample @c projectfile
14324 for ^Switches^Switches^ ("main1.adb")
14326 for ^Switches^Switches^ ("main2.adb")
14333 For the @code{Builder} package, the file names must designate source files
14334 for main subprograms. For the @code{Binder} and @code{Linker} packages, the
14335 file names must designate @file{ALI} or source files for main subprograms.
14336 In each case just the file name without an explicit extension is acceptable.
14338 For each tool used in a program build (@command{gnatmake}, the compiler, the
14339 binder, and the linker), the corresponding package @dfn{contributes} a set of
14340 ^switches^switches^ for each file on which the tool is invoked, based on the
14341 ^switch^switch^-related attributes defined in the package.
14342 In particular, the ^switches^switches^
14343 that each of these packages contributes for a given file @var{f} comprise:
14347 the value of attribute @code{^Switches^Switches^ (@var{f})},
14348 if it is specified in the package for the given file,
14350 otherwise, the value of @code{^Default_Switches^Default_Switches^ ("Ada")},
14351 if it is specified in the package.
14355 If neither of these attributes is defined in the package, then the package does
14356 not contribute any ^switches^switches^ for the given file.
14358 When @command{gnatmake} is invoked on a file, the ^switches^switches^ comprise
14359 two sets, in the following order: those contributed for the file
14360 by the @code{Builder} package;
14361 and the switches passed on the command line.
14363 When @command{gnatmake} invokes a tool (compiler, binder, linker) on a file,
14364 the ^switches^switches^ passed to the tool comprise three sets,
14365 in the following order:
14369 the applicable ^switches^switches^ contributed for the file
14370 by the @code{Builder} package in the project file supplied on the command line;
14373 those contributed for the file by the package (in the relevant project file --
14374 see below) corresponding to the tool; and
14377 the applicable switches passed on the command line.
14381 The term @emph{applicable ^switches^switches^} reflects the fact that
14382 @command{gnatmake} ^switches^switches^ may or may not be passed to individual
14383 tools, depending on the individual ^switch^switch^.
14385 @command{gnatmake} may invoke the compiler on source files from different
14386 projects. The Project Manager will use the appropriate project file to
14387 determine the @code{Compiler} package for each source file being compiled.
14388 Likewise for the @code{Binder} and @code{Linker} packages.
14390 As an example, consider the following package in a project file:
14392 @smallexample @c projectfile
14395 package Compiler is
14396 for ^Default_Switches^Default_Switches^ ("Ada")
14398 for ^Switches^Switches^ ("a.adb")
14400 for ^Switches^Switches^ ("b.adb")
14402 "^-gnaty^-gnaty^");
14409 If @command{gnatmake} is invoked with this project file, and it needs to
14410 compile, say, the files @file{a.adb}, @file{b.adb}, and @file{c.adb}, then
14411 @file{a.adb} will be compiled with the ^switch^switch^
14412 @option{^-O1^-O1^},
14413 @file{b.adb} with ^switches^switches^
14415 and @option{^-gnaty^-gnaty^},
14416 and @file{c.adb} with @option{^-g^-g^}.
14418 The following example illustrates the ordering of the ^switches^switches^
14419 contributed by different packages:
14421 @smallexample @c projectfile
14425 for ^Switches^Switches^ ("main.adb")
14433 package Compiler is
14434 for ^Switches^Switches^ ("main.adb")
14442 If you issue the command:
14445 gnatmake ^-Pproj2^/PROJECT_FILE=PROJ2^ -O0 main
14449 then the compiler will be invoked on @file{main.adb} with the following
14450 sequence of ^switches^switches^
14453 ^-g -O1 -O2 -O0^-g -O1 -O2 -O0^
14456 with the last @option{^-O^-O^}
14457 ^switch^switch^ having precedence over the earlier ones;
14458 several other ^switches^switches^
14459 (such as @option{^-c^-c^}) are added implicitly.
14461 The ^switches^switches^
14463 and @option{^-O1^-O1^} are contributed by package
14464 @code{Builder}, @option{^-O2^-O2^} is contributed
14465 by the package @code{Compiler}
14466 and @option{^-O0^-O0^} comes from the command line.
14468 The @option{^-g^-g^}
14469 ^switch^switch^ will also be passed in the invocation of
14470 @command{Gnatlink.}
14472 A final example illustrates switch contributions from packages in different
14475 @smallexample @c projectfile
14478 for Source_Files use ("pack.ads", "pack.adb");
14479 package Compiler is
14480 for ^Default_Switches^Default_Switches^ ("Ada")
14481 use ("^-gnata^-gnata^");
14489 for Source_Files use ("foo_main.adb", "bar_main.adb");
14491 for ^Switches^Switches^ ("foo_main.adb")
14499 -- Ada source file:
14501 procedure Foo_Main is
14509 gnatmake ^-PProj4^/PROJECT_FILE=PROJ4^ foo_main.adb -cargs -gnato
14513 then the ^switches^switches^ passed to the compiler for @file{foo_main.adb} are
14514 @option{^-g^-g^} (contributed by the package @code{Proj4.Builder}) and
14515 @option{^-gnato^-gnato^} (passed on the command line).
14516 When the imported package @code{Pack} is compiled, the ^switches^switches^ used
14517 are @option{^-g^-g^} from @code{Proj4.Builder},
14518 @option{^-gnata^-gnata^} (contributed from package @code{Proj3.Compiler},
14519 and @option{^-gnato^-gnato^} from the command line.
14522 When using @command{gnatmake} with project files, some ^switches^switches^ or
14523 arguments may be expressed as relative paths. As the working directory where
14524 compilation occurs may change, these relative paths are converted to absolute
14525 paths. For the ^switches^switches^ found in a project file, the relative paths
14526 are relative to the project file directory, for the switches on the command
14527 line, they are relative to the directory where @command{gnatmake} is invoked.
14528 The ^switches^switches^ for which this occurs are:
14534 ^-aI^-aI^, as well as all arguments that are not switches (arguments to
14536 ^-o^-o^, object files specified in package @code{Linker} or after
14537 -largs on the command line). The exception to this rule is the ^switch^switch^
14538 ^--RTS=^--RTS=^ for which a relative path argument is never converted.
14540 @node Specifying Configuration Pragmas
14541 @subsubsection Specifying Configuration Pragmas
14543 When using @command{gnatmake} with project files, if there exists a file
14544 @file{gnat.adc} that contains configuration pragmas, this file will be
14547 Configuration pragmas can be defined by means of the following attributes in
14548 project files: @code{Global_Configuration_Pragmas} in package @code{Builder}
14549 and @code{Local_Configuration_Pragmas} in package @code{Compiler}.
14551 Both these attributes are single string attributes. Their values is the path
14552 name of a file containing configuration pragmas. If a path name is relative,
14553 then it is relative to the project directory of the project file where the
14554 attribute is defined.
14556 When compiling a source, the configuration pragmas used are, in order,
14557 those listed in the file designated by attribute
14558 @code{Global_Configuration_Pragmas} in package @code{Builder} of the main
14559 project file, if it is specified, and those listed in the file designated by
14560 attribute @code{Local_Configuration_Pragmas} in package @code{Compiler} of
14561 the project file of the source, if it exists.
14563 @node Project Files and Main Subprograms
14564 @subsubsection Project Files and Main Subprograms
14567 When using a project file, you can invoke @command{gnatmake}
14568 with one or several main subprograms, by specifying their source files on the
14572 gnatmake ^-P^/PROJECT_FILE=^prj main1 main2 main3
14576 Each of these needs to be a source file of the same project, except
14577 when the switch ^-u^/UNIQUE^ is used.
14580 When ^-u^/UNIQUE^ is not used, all the mains need to be sources of the
14581 same project, one of the project in the tree rooted at the project specified
14582 on the command line. The package @code{Builder} of this common project, the
14583 "main project" is the one that is considered by @command{gnatmake}.
14586 When ^-u^/UNIQUE^ is used, the specified source files may be in projects
14587 imported directly or indirectly by the project specified on the command line.
14588 Note that if such a source file is not part of the project specified on the
14589 command line, the ^switches^switches^ found in package @code{Builder} of the
14590 project specified on the command line, if any, that are transmitted
14591 to the compiler will still be used, not those found in the project file of
14595 When using a project file, you can also invoke @command{gnatmake} without
14596 explicitly specifying any main, and the effect depends on whether you have
14597 defined the @code{Main} attribute. This attribute has a string list value,
14598 where each element in the list is the name of a source file (the file
14599 extension is optional) that contains a unit that can be a main subprogram.
14601 If the @code{Main} attribute is defined in a project file as a non-empty
14602 string list and the switch @option{^-u^/UNIQUE^} is not used on the command
14603 line, then invoking @command{gnatmake} with this project file but without any
14604 main on the command line is equivalent to invoking @command{gnatmake} with all
14605 the file names in the @code{Main} attribute on the command line.
14608 @smallexample @c projectfile
14611 for Main use ("main1", "main2", "main3");
14617 With this project file, @code{"gnatmake ^-Pprj^/PROJECT_FILE=PRJ^"}
14619 @code{"gnatmake ^-Pprj^/PROJECT_FILE=PRJ^ main1 main2 main3"}.
14621 When the project attribute @code{Main} is not specified, or is specified
14622 as an empty string list, or when the switch @option{-u} is used on the command
14623 line, then invoking @command{gnatmake} with no main on the command line will
14624 result in all immediate sources of the project file being checked, and
14625 potentially recompiled. Depending on the presence of the switch @option{-u},
14626 sources from other project files on which the immediate sources of the main
14627 project file depend are also checked and potentially recompiled. In other
14628 words, the @option{-u} switch is applied to all of the immediate sources of the
14631 When no main is specified on the command line and attribute @code{Main} exists
14632 and includes several mains, or when several mains are specified on the
14633 command line, the default ^switches^switches^ in package @code{Builder} will
14634 be used for all mains, even if there are specific ^switches^switches^
14635 specified for one or several mains.
14637 But the ^switches^switches^ from package @code{Binder} or @code{Linker} will be
14638 the specific ^switches^switches^ for each main, if they are specified.
14640 @node Library Project Files
14641 @subsubsection Library Project Files
14644 When @command{gnatmake} is invoked with a main project file that is a library
14645 project file, it is not allowed to specify one or more mains on the command
14649 When a library project file is specified, switches ^-b^/ACTION=BIND^ and
14650 ^-l^/ACTION=LINK^ have special meanings.
14653 @item ^-b^/ACTION=BIND^ is only allowed for stand-alone libraries. It indicates
14654 to @command{gnatmake} that @command{gnatbind} should be invoked for the
14657 @item ^-l^/ACTION=LINK^ may be used for all library projects. It indicates
14658 to @command{gnatmake} that the binder generated file should be compiled
14659 (in the case of a stand-alone library) and that the library should be built.
14663 @node The GNAT Driver and Project Files
14664 @subsection The GNAT Driver and Project Files
14667 A number of GNAT tools, other than @command{^gnatmake^gnatmake^}
14668 can benefit from project files:
14669 @command{^gnatbind^gnatbind^},
14670 @command{^gnatcheck^gnatcheck^}),
14671 @command{^gnatclean^gnatclean^}),
14672 @command{^gnatelim^gnatelim^},
14673 @command{^gnatfind^gnatfind^},
14674 @command{^gnatlink^gnatlink^},
14675 @command{^gnatls^gnatls^},
14676 @command{^gnatmetric^gnatmetric^},
14677 @command{^gnatpp^gnatpp^},
14678 @command{^gnatstub^gnatstub^},
14679 and @command{^gnatxref^gnatxref^}. However, none of these tools can be invoked
14680 directly with a project file switch (@option{^-P^/PROJECT_FILE=^}).
14681 They must be invoked through the @command{gnat} driver.
14683 The @command{gnat} driver is a wrapper that accepts a number of commands and
14684 calls the corresponding tool. It was designed initially for VMS platforms (to
14685 convert VMS qualifiers to Unix-style switches), but it is now available on all
14688 On non-VMS platforms, the @command{gnat} driver accepts the following commands
14689 (case insensitive):
14693 BIND to invoke @command{^gnatbind^gnatbind^}
14695 CHOP to invoke @command{^gnatchop^gnatchop^}
14697 CLEAN to invoke @command{^gnatclean^gnatclean^}
14699 COMP or COMPILE to invoke the compiler
14701 ELIM to invoke @command{^gnatelim^gnatelim^}
14703 FIND to invoke @command{^gnatfind^gnatfind^}
14705 KR or KRUNCH to invoke @command{^gnatkr^gnatkr^}
14707 LINK to invoke @command{^gnatlink^gnatlink^}
14709 LS or LIST to invoke @command{^gnatls^gnatls^}
14711 MAKE to invoke @command{^gnatmake^gnatmake^}
14713 NAME to invoke @command{^gnatname^gnatname^}
14715 PREP or PREPROCESS to invoke @command{^gnatprep^gnatprep^}
14717 PP or PRETTY to invoke @command{^gnatpp^gnatpp^}
14719 METRIC to invoke @command{^gnatmetric^gnatmetric^}
14721 STUB to invoke @command{^gnatstub^gnatstub^}
14723 XREF to invoke @command{^gnatxref^gnatxref^}
14727 (note that the compiler is invoked using the command
14728 @command{^gnatmake -f -u -c^gnatmake -f -u -c^}).
14731 On non-VMS platforms, between @command{gnat} and the command, two
14732 special switches may be used:
14736 @command{-v} to display the invocation of the tool.
14738 @command{-dn} to prevent the @command{gnat} driver from removing
14739 the temporary files it has created. These temporary files are
14740 configuration files and temporary file list files.
14744 The command may be followed by switches and arguments for the invoked
14748 gnat bind -C main.ali
14754 Switches may also be put in text files, one switch per line, and the text
14755 files may be specified with their path name preceded by '@@'.
14758 gnat bind @@args.txt main.ali
14762 In addition, for commands BIND, COMP or COMPILE, FIND, ELIM, LS or LIST, LINK,
14763 METRIC, PP or PRETTY, STUB and XREF, the project file related switches
14764 (@option{^-P^/PROJECT_FILE^},
14765 @option{^-X^/EXTERNAL_REFERENCE^} and
14766 @option{^-vP^/MESSAGES_PROJECT_FILE=^x}) may be used in addition to
14767 the switches of the invoking tool.
14770 When GNAT PP or GNAT PRETTY is used with a project file, but with no source
14771 specified on the command line, it invokes @command{^gnatpp^gnatpp^} with all
14772 the immediate sources of the specified project file.
14775 When GNAT METRIC is used with a project file, but with no source
14776 specified on the command line, it invokes @command{^gnatmetric^gnatmetric^}
14777 with all the immediate sources of the specified project file and with
14778 @option{^-d^/DIRECTORY^} with the parameter pointing to the object directory
14782 In addition, when GNAT PP, GNAT PRETTY or GNAT METRIC is used with
14783 a project file, no source is specified on the command line and
14784 switch ^-U^/ALL_PROJECTS^ is specified on the command line, then
14785 the underlying tool (^gnatpp^gnatpp^ or
14786 ^gnatmetric^gnatmetric^) is invoked for all sources of all projects,
14787 not only for the immediate sources of the main project.
14789 (-U stands for Universal or Union of the project files of the project tree)
14793 For each of the following commands, there is optionally a corresponding
14794 package in the main project.
14798 package @code{Binder} for command BIND (invoking @code{^gnatbind^gnatbind^})
14801 package @code{Check} for command CHECK (invoking
14802 @code{^gnatcheck^gnatcheck^})
14805 package @code{Compiler} for command COMP or COMPILE (invoking the compiler)
14808 package @code{Cross_Reference} for command XREF (invoking
14809 @code{^gnatxref^gnatxref^})
14812 package @code{Eliminate} for command ELIM (invoking
14813 @code{^gnatelim^gnatelim^})
14816 package @code{Finder} for command FIND (invoking @code{^gnatfind^gnatfind^})
14819 package @code{Gnatls} for command LS or LIST (invoking @code{^gnatls^gnatls^})
14822 package @code{Gnatstub} for command STUB
14823 (invoking @code{^gnatstub^gnatstub^})
14826 package @code{Linker} for command LINK (invoking @code{^gnatlink^gnatlink^})
14829 package @code{Metrics} for command METRIC
14830 (invoking @code{^gnatmetric^gnatmetric^})
14833 package @code{Pretty_Printer} for command PP or PRETTY
14834 (invoking @code{^gnatpp^gnatpp^})
14839 Package @code{Gnatls} has a unique attribute @code{^Switches^Switches^},
14840 a simple variable with a string list value. It contains ^switches^switches^
14841 for the invocation of @code{^gnatls^gnatls^}.
14843 @smallexample @c projectfile
14847 for ^Switches^Switches^
14856 All other packages have two attribute @code{^Switches^Switches^} and
14857 @code{^Default_Switches^Default_Switches^}.
14860 @code{^Switches^Switches^} is an associative array attribute, indexed by the
14861 source file name, that has a string list value: the ^switches^switches^ to be
14862 used when the tool corresponding to the package is invoked for the specific
14866 @code{^Default_Switches^Default_Switches^} is an associative array attribute,
14867 indexed by the programming language that has a string list value.
14868 @code{^Default_Switches^Default_Switches^ ("Ada")} contains the
14869 ^switches^switches^ for the invocation of the tool corresponding
14870 to the package, except if a specific @code{^Switches^Switches^} attribute
14871 is specified for the source file.
14873 @smallexample @c projectfile
14877 for Source_Dirs use ("./**");
14880 for ^Switches^Switches^ use
14887 package Compiler is
14888 for ^Default_Switches^Default_Switches^ ("Ada")
14889 use ("^-gnatv^-gnatv^",
14890 "^-gnatwa^-gnatwa^");
14896 for ^Default_Switches^Default_Switches^ ("Ada")
14904 for ^Default_Switches^Default_Switches^ ("Ada")
14906 for ^Switches^Switches^ ("main.adb")
14915 for ^Default_Switches^Default_Switches^ ("Ada")
14922 package Cross_Reference is
14923 for ^Default_Switches^Default_Switches^ ("Ada")
14928 end Cross_Reference;
14934 With the above project file, commands such as
14937 ^gnat comp -Pproj main^GNAT COMP /PROJECT_FILE=PROJ MAIN^
14938 ^gnat ls -Pproj main^GNAT LIST /PROJECT_FILE=PROJ MAIN^
14939 ^gnat xref -Pproj main^GNAT XREF /PROJECT_FILE=PROJ MAIN^
14940 ^gnat bind -Pproj main.ali^GNAT BIND /PROJECT_FILE=PROJ MAIN.ALI^
14941 ^gnat link -Pproj main.ali^GNAT LINK /PROJECT_FILE=PROJ MAIN.ALI^
14945 will set up the environment properly and invoke the tool with the switches
14946 found in the package corresponding to the tool:
14947 @code{^Default_Switches^Default_Switches^ ("Ada")} for all tools,
14948 except @code{^Switches^Switches^ ("main.adb")}
14949 for @code{^gnatlink^gnatlink^}.
14950 It is also possible to invoke some of the tools,
14951 @code{^gnatcheck^gnatcheck^}),
14952 @code{^gnatmetric^gnatmetric^}),
14953 and @code{^gnatpp^gnatpp^})
14954 on a set of project units thanks to the combination of the switches
14955 @option{-P}, @option{-U} and possibly the main unit when one is interested
14956 in its closure. For instance,
14960 will compute the metrics for all the immediate units of project
14963 gnat metric -Pproj -U
14965 will compute the metrics for all the units of the closure of projects
14966 rooted at @code{proj}.
14968 gnat metric -Pproj -U main_unit
14970 will compute the metrics for the closure of units rooted at
14971 @code{main_unit}. This last possibility relies implicitly
14972 on @command{gnatbind}'s option @option{-R}.
14974 @c **********************
14975 @node An Extended Example
14976 @section An Extended Example
14979 Suppose that we have two programs, @var{prog1} and @var{prog2},
14980 whose sources are in corresponding directories. We would like
14981 to build them with a single @command{gnatmake} command, and we want to place
14982 their object files into @file{build} subdirectories of the source directories.
14983 Furthermore, we want to have to have two separate subdirectories
14984 in @file{build} -- @file{release} and @file{debug} -- which will contain
14985 the object files compiled with different set of compilation flags.
14987 In other words, we have the following structure:
15004 Here are the project files that we must place in a directory @file{main}
15005 to maintain this structure:
15009 @item We create a @code{Common} project with a package @code{Compiler} that
15010 specifies the compilation ^switches^switches^:
15015 @b{project} Common @b{is}
15017 @b{for} Source_Dirs @b{use} (); -- No source files
15021 @b{type} Build_Type @b{is} ("release", "debug");
15022 Build : Build_Type := External ("BUILD", "debug");
15025 @b{package} Compiler @b{is}
15026 @b{case} Build @b{is}
15027 @b{when} "release" =>
15028 @b{for} ^Default_Switches^Default_Switches^ ("Ada")
15029 @b{use} ("^-O2^-O2^");
15030 @b{when} "debug" =>
15031 @b{for} ^Default_Switches^Default_Switches^ ("Ada")
15032 @b{use} ("^-g^-g^");
15040 @item We create separate projects for the two programs:
15047 @b{project} Prog1 @b{is}
15049 @b{for} Source_Dirs @b{use} ("prog1");
15050 @b{for} Object_Dir @b{use} "prog1/build/" & Common.Build;
15052 @b{package} Compiler @b{renames} Common.Compiler;
15063 @b{project} Prog2 @b{is}
15065 @b{for} Source_Dirs @b{use} ("prog2");
15066 @b{for} Object_Dir @b{use} "prog2/build/" & Common.Build;
15068 @b{package} Compiler @b{renames} Common.Compiler;
15074 @item We create a wrapping project @code{Main}:
15083 @b{project} Main @b{is}
15085 @b{package} Compiler @b{renames} Common.Compiler;
15091 @item Finally we need to create a dummy procedure that @code{with}s (either
15092 explicitly or implicitly) all the sources of our two programs.
15097 Now we can build the programs using the command
15100 gnatmake ^-P^/PROJECT_FILE=^main dummy
15104 for the Debug mode, or
15108 gnatmake -Pmain -XBUILD=release
15114 GNAT MAKE /PROJECT_FILE=main /EXTERNAL_REFERENCE=BUILD=release
15119 for the Release mode.
15121 @c ********************************
15122 @c * Project File Complete Syntax *
15123 @c ********************************
15125 @node Project File Complete Syntax
15126 @section Project File Complete Syntax
15130 context_clause project_declaration
15136 @b{with} path_name @{ , path_name @} ;
15141 project_declaration ::=
15142 simple_project_declaration | project_extension
15144 simple_project_declaration ::=
15145 @b{project} <project_>simple_name @b{is}
15146 @{declarative_item@}
15147 @b{end} <project_>simple_name;
15149 project_extension ::=
15150 @b{project} <project_>simple_name @b{extends} path_name @b{is}
15151 @{declarative_item@}
15152 @b{end} <project_>simple_name;
15154 declarative_item ::=
15155 package_declaration |
15156 typed_string_declaration |
15157 other_declarative_item
15159 package_declaration ::=
15160 package_spec | package_renaming
15163 @b{package} package_identifier @b{is}
15164 @{simple_declarative_item@}
15165 @b{end} package_identifier ;
15167 package_identifier ::=
15168 @code{Naming} | @code{Builder} | @code{Compiler} | @code{Binder} |
15169 @code{Linker} | @code{Finder} | @code{Cross_Reference} |
15170 @code{^gnatls^gnatls^} | @code{IDE} | @code{Pretty_Printer}
15172 package_renaming ::==
15173 @b{package} package_identifier @b{renames}
15174 <project_>simple_name.package_identifier ;
15176 typed_string_declaration ::=
15177 @b{type} <typed_string_>_simple_name @b{is}
15178 ( string_literal @{, string_literal@} );
15180 other_declarative_item ::=
15181 attribute_declaration |
15182 typed_variable_declaration |
15183 variable_declaration |
15186 attribute_declaration ::=
15187 full_associative_array_declaration |
15188 @b{for} attribute_designator @b{use} expression ;
15190 full_associative_array_declaration ::=
15191 @b{for} <associative_array_attribute_>simple_name @b{use}
15192 <project_>simple_name [ . <package_>simple_Name ] ' <attribute_>simple_name ;
15194 attribute_designator ::=
15195 <simple_attribute_>simple_name |
15196 <associative_array_attribute_>simple_name ( string_literal )
15198 typed_variable_declaration ::=
15199 <typed_variable_>simple_name : <typed_string_>name := string_expression ;
15201 variable_declaration ::=
15202 <variable_>simple_name := expression;
15212 attribute_reference
15218 ( <string_>expression @{ , <string_>expression @} )
15221 @b{external} ( string_literal [, string_literal] )
15223 attribute_reference ::=
15224 attribute_prefix ' <simple_attribute_>simple_name [ ( literal_string ) ]
15226 attribute_prefix ::=
15228 <project_>simple_name | package_identifier |
15229 <project_>simple_name . package_identifier
15231 case_construction ::=
15232 @b{case} <typed_variable_>name @b{is}
15237 @b{when} discrete_choice_list =>
15238 @{case_construction | attribute_declaration@}
15240 discrete_choice_list ::=
15241 string_literal @{| string_literal@} |
15245 simple_name @{. simple_name@}
15248 identifier (same as Ada)
15252 @node The Cross-Referencing Tools gnatxref and gnatfind
15253 @chapter The Cross-Referencing Tools @code{gnatxref} and @code{gnatfind}
15258 The compiler generates cross-referencing information (unless
15259 you set the @samp{-gnatx} switch), which are saved in the @file{.ali} files.
15260 This information indicates where in the source each entity is declared and
15261 referenced. Note that entities in package Standard are not included, but
15262 entities in all other predefined units are included in the output.
15264 Before using any of these two tools, you need to compile successfully your
15265 application, so that GNAT gets a chance to generate the cross-referencing
15268 The two tools @code{gnatxref} and @code{gnatfind} take advantage of this
15269 information to provide the user with the capability to easily locate the
15270 declaration and references to an entity. These tools are quite similar,
15271 the difference being that @code{gnatfind} is intended for locating
15272 definitions and/or references to a specified entity or entities, whereas
15273 @code{gnatxref} is oriented to generating a full report of all
15276 To use these tools, you must not compile your application using the
15277 @option{-gnatx} switch on the @command{gnatmake} command line
15278 (@pxref{The GNAT Make Program gnatmake}). Otherwise, cross-referencing
15279 information will not be generated.
15281 Note: to invoke @code{gnatxref} or @code{gnatfind} with a project file,
15282 use the @code{gnat} driver (see @ref{The GNAT Driver and Project Files}).
15285 * gnatxref Switches::
15286 * gnatfind Switches::
15287 * Project Files for gnatxref and gnatfind::
15288 * Regular Expressions in gnatfind and gnatxref::
15289 * Examples of gnatxref Usage::
15290 * Examples of gnatfind Usage::
15293 @node gnatxref Switches
15294 @section @code{gnatxref} Switches
15297 The command invocation for @code{gnatxref} is:
15299 $ gnatxref @ovar{switches} @var{sourcefile1} @r{[}@var{sourcefile2} @dots{}@r{]}
15308 identifies the source files for which a report is to be generated. The
15309 ``with''ed units will be processed too. You must provide at least one file.
15311 These file names are considered to be regular expressions, so for instance
15312 specifying @file{source*.adb} is the same as giving every file in the current
15313 directory whose name starts with @file{source} and whose extension is
15316 You shouldn't specify any directory name, just base names. @command{gnatxref}
15317 and @command{gnatfind} will be able to locate these files by themselves using
15318 the source path. If you specify directories, no result is produced.
15323 The switches can be:
15327 @cindex @option{--version} @command{gnatxref}
15328 Display Copyright and version, then exit disregarding all other options.
15331 @cindex @option{--help} @command{gnatxref}
15332 If @option{--version} was not used, display usage, then exit disregarding
15335 @item ^-a^/ALL_FILES^
15336 @cindex @option{^-a^/ALL_FILES^} (@command{gnatxref})
15337 If this switch is present, @code{gnatfind} and @code{gnatxref} will parse
15338 the read-only files found in the library search path. Otherwise, these files
15339 will be ignored. This option can be used to protect Gnat sources or your own
15340 libraries from being parsed, thus making @code{gnatfind} and @code{gnatxref}
15341 much faster, and their output much smaller. Read-only here refers to access
15342 or permissions status in the file system for the current user.
15345 @cindex @option{-aIDIR} (@command{gnatxref})
15346 When looking for source files also look in directory DIR. The order in which
15347 source file search is undertaken is the same as for @command{gnatmake}.
15350 @cindex @option{-aODIR} (@command{gnatxref})
15351 When searching for library and object files, look in directory
15352 DIR. The order in which library files are searched is the same as for
15353 @command{gnatmake}.
15356 @cindex @option{-nostdinc} (@command{gnatxref})
15357 Do not look for sources in the system default directory.
15360 @cindex @option{-nostdlib} (@command{gnatxref})
15361 Do not look for library files in the system default directory.
15363 @item --RTS=@var{rts-path}
15364 @cindex @option{--RTS} (@command{gnatxref})
15365 Specifies the default location of the runtime library. Same meaning as the
15366 equivalent @command{gnatmake} flag (@pxref{Switches for gnatmake}).
15368 @item ^-d^/DERIVED_TYPES^
15369 @cindex @option{^-d^/DERIVED_TYPES^} (@command{gnatxref})
15370 If this switch is set @code{gnatxref} will output the parent type
15371 reference for each matching derived types.
15373 @item ^-f^/FULL_PATHNAME^
15374 @cindex @option{^-f^/FULL_PATHNAME^} (@command{gnatxref})
15375 If this switch is set, the output file names will be preceded by their
15376 directory (if the file was found in the search path). If this switch is
15377 not set, the directory will not be printed.
15379 @item ^-g^/IGNORE_LOCALS^
15380 @cindex @option{^-g^/IGNORE_LOCALS^} (@command{gnatxref})
15381 If this switch is set, information is output only for library-level
15382 entities, ignoring local entities. The use of this switch may accelerate
15383 @code{gnatfind} and @code{gnatxref}.
15386 @cindex @option{-IDIR} (@command{gnatxref})
15387 Equivalent to @samp{-aODIR -aIDIR}.
15390 @cindex @option{-pFILE} (@command{gnatxref})
15391 Specify a project file to use @xref{Project Files}.
15392 If you need to use the @file{.gpr}
15393 project files, you should use gnatxref through the GNAT driver
15394 (@command{gnat xref -Pproject}).
15396 By default, @code{gnatxref} and @code{gnatfind} will try to locate a
15397 project file in the current directory.
15399 If a project file is either specified or found by the tools, then the content
15400 of the source directory and object directory lines are added as if they
15401 had been specified respectively by @samp{^-aI^/SOURCE_SEARCH^}
15402 and @samp{^-aO^OBJECT_SEARCH^}.
15404 Output only unused symbols. This may be really useful if you give your
15405 main compilation unit on the command line, as @code{gnatxref} will then
15406 display every unused entity and 'with'ed package.
15410 Instead of producing the default output, @code{gnatxref} will generate a
15411 @file{tags} file that can be used by vi. For examples how to use this
15412 feature, see @ref{Examples of gnatxref Usage}. The tags file is output
15413 to the standard output, thus you will have to redirect it to a file.
15419 All these switches may be in any order on the command line, and may even
15420 appear after the file names. They need not be separated by spaces, thus
15421 you can say @samp{gnatxref ^-ag^/ALL_FILES/IGNORE_LOCALS^} instead of
15422 @samp{gnatxref ^-a -g^/ALL_FILES /IGNORE_LOCALS^}.
15424 @node gnatfind Switches
15425 @section @code{gnatfind} Switches
15428 The command line for @code{gnatfind} is:
15431 $ gnatfind @ovar{switches} @var{pattern}@r{[}:@var{sourcefile}@r{[}:@var{line}@r{[}:@var{column}@r{]]]}
15432 @r{[}@var{file1} @var{file2} @dots{}]
15440 An entity will be output only if it matches the regular expression found
15441 in @var{pattern}, see @ref{Regular Expressions in gnatfind and gnatxref}.
15443 Omitting the pattern is equivalent to specifying @samp{*}, which
15444 will match any entity. Note that if you do not provide a pattern, you
15445 have to provide both a sourcefile and a line.
15447 Entity names are given in Latin-1, with uppercase/lowercase equivalence
15448 for matching purposes. At the current time there is no support for
15449 8-bit codes other than Latin-1, or for wide characters in identifiers.
15452 @code{gnatfind} will look for references, bodies or declarations
15453 of symbols referenced in @file{@var{sourcefile}}, at line @var{line}
15454 and column @var{column}. See @ref{Examples of gnatfind Usage}
15455 for syntax examples.
15458 is a decimal integer identifying the line number containing
15459 the reference to the entity (or entities) to be located.
15462 is a decimal integer identifying the exact location on the
15463 line of the first character of the identifier for the
15464 entity reference. Columns are numbered from 1.
15466 @item file1 file2 @dots{}
15467 The search will be restricted to these source files. If none are given, then
15468 the search will be done for every library file in the search path.
15469 These file must appear only after the pattern or sourcefile.
15471 These file names are considered to be regular expressions, so for instance
15472 specifying @file{source*.adb} is the same as giving every file in the current
15473 directory whose name starts with @file{source} and whose extension is
15476 The location of the spec of the entity will always be displayed, even if it
15477 isn't in one of @file{@var{file1}}, @file{@var{file2}},@enddots{} The
15478 occurrences of the entity in the separate units of the ones given on the
15479 command line will also be displayed.
15481 Note that if you specify at least one file in this part, @code{gnatfind} may
15482 sometimes not be able to find the body of the subprograms.
15487 At least one of 'sourcefile' or 'pattern' has to be present on
15490 The following switches are available:
15494 @cindex @option{--version} @command{gnatfind}
15495 Display Copyright and version, then exit disregarding all other options.
15498 @cindex @option{--help} @command{gnatfind}
15499 If @option{--version} was not used, display usage, then exit disregarding
15502 @item ^-a^/ALL_FILES^
15503 @cindex @option{^-a^/ALL_FILES^} (@command{gnatfind})
15504 If this switch is present, @code{gnatfind} and @code{gnatxref} will parse
15505 the read-only files found in the library search path. Otherwise, these files
15506 will be ignored. This option can be used to protect Gnat sources or your own
15507 libraries from being parsed, thus making @code{gnatfind} and @code{gnatxref}
15508 much faster, and their output much smaller. Read-only here refers to access
15509 or permission status in the file system for the current user.
15512 @cindex @option{-aIDIR} (@command{gnatfind})
15513 When looking for source files also look in directory DIR. The order in which
15514 source file search is undertaken is the same as for @command{gnatmake}.
15517 @cindex @option{-aODIR} (@command{gnatfind})
15518 When searching for library and object files, look in directory
15519 DIR. The order in which library files are searched is the same as for
15520 @command{gnatmake}.
15523 @cindex @option{-nostdinc} (@command{gnatfind})
15524 Do not look for sources in the system default directory.
15527 @cindex @option{-nostdlib} (@command{gnatfind})
15528 Do not look for library files in the system default directory.
15530 @item --RTS=@var{rts-path}
15531 @cindex @option{--RTS} (@command{gnatfind})
15532 Specifies the default location of the runtime library. Same meaning as the
15533 equivalent @command{gnatmake} flag (@pxref{Switches for gnatmake}).
15535 @item ^-d^/DERIVED_TYPE_INFORMATION^
15536 @cindex @option{^-d^/DERIVED_TYPE_INFORMATION^} (@code{gnatfind})
15537 If this switch is set, then @code{gnatfind} will output the parent type
15538 reference for each matching derived types.
15540 @item ^-e^/EXPRESSIONS^
15541 @cindex @option{^-e^/EXPRESSIONS^} (@command{gnatfind})
15542 By default, @code{gnatfind} accept the simple regular expression set for
15543 @samp{pattern}. If this switch is set, then the pattern will be
15544 considered as full Unix-style regular expression.
15546 @item ^-f^/FULL_PATHNAME^
15547 @cindex @option{^-f^/FULL_PATHNAME^} (@command{gnatfind})
15548 If this switch is set, the output file names will be preceded by their
15549 directory (if the file was found in the search path). If this switch is
15550 not set, the directory will not be printed.
15552 @item ^-g^/IGNORE_LOCALS^
15553 @cindex @option{^-g^/IGNORE_LOCALS^} (@command{gnatfind})
15554 If this switch is set, information is output only for library-level
15555 entities, ignoring local entities. The use of this switch may accelerate
15556 @code{gnatfind} and @code{gnatxref}.
15559 @cindex @option{-IDIR} (@command{gnatfind})
15560 Equivalent to @samp{-aODIR -aIDIR}.
15563 @cindex @option{-pFILE} (@command{gnatfind})
15564 Specify a project file (@pxref{Project Files}) to use.
15565 By default, @code{gnatxref} and @code{gnatfind} will try to locate a
15566 project file in the current directory.
15568 If a project file is either specified or found by the tools, then the content
15569 of the source directory and object directory lines are added as if they
15570 had been specified respectively by @samp{^-aI^/SOURCE_SEARCH^} and
15571 @samp{^-aO^/OBJECT_SEARCH^}.
15573 @item ^-r^/REFERENCES^
15574 @cindex @option{^-r^/REFERENCES^} (@command{gnatfind})
15575 By default, @code{gnatfind} will output only the information about the
15576 declaration, body or type completion of the entities. If this switch is
15577 set, the @code{gnatfind} will locate every reference to the entities in
15578 the files specified on the command line (or in every file in the search
15579 path if no file is given on the command line).
15581 @item ^-s^/PRINT_LINES^
15582 @cindex @option{^-s^/PRINT_LINES^} (@command{gnatfind})
15583 If this switch is set, then @code{gnatfind} will output the content
15584 of the Ada source file lines were the entity was found.
15586 @item ^-t^/TYPE_HIERARCHY^
15587 @cindex @option{^-t^/TYPE_HIERARCHY^} (@command{gnatfind})
15588 If this switch is set, then @code{gnatfind} will output the type hierarchy for
15589 the specified type. It act like -d option but recursively from parent
15590 type to parent type. When this switch is set it is not possible to
15591 specify more than one file.
15596 All these switches may be in any order on the command line, and may even
15597 appear after the file names. They need not be separated by spaces, thus
15598 you can say @samp{gnatxref ^-ag^/ALL_FILES/IGNORE_LOCALS^} instead of
15599 @samp{gnatxref ^-a -g^/ALL_FILES /IGNORE_LOCALS^}.
15601 As stated previously, gnatfind will search in every directory in the
15602 search path. You can force it to look only in the current directory if
15603 you specify @code{*} at the end of the command line.
15605 @node Project Files for gnatxref and gnatfind
15606 @section Project Files for @command{gnatxref} and @command{gnatfind}
15609 Project files allow a programmer to specify how to compile its
15610 application, where to find sources, etc. These files are used
15612 primarily by GPS, but they can also be used
15615 @code{gnatxref} and @code{gnatfind}.
15617 A project file name must end with @file{.gpr}. If a single one is
15618 present in the current directory, then @code{gnatxref} and @code{gnatfind} will
15619 extract the information from it. If multiple project files are found, none of
15620 them is read, and you have to use the @samp{-p} switch to specify the one
15623 The following lines can be included, even though most of them have default
15624 values which can be used in most cases.
15625 The lines can be entered in any order in the file.
15626 Except for @file{src_dir} and @file{obj_dir}, you can only have one instance of
15627 each line. If you have multiple instances, only the last one is taken into
15632 [default: @code{"^./^[]^"}]
15633 specifies a directory where to look for source files. Multiple @code{src_dir}
15634 lines can be specified and they will be searched in the order they
15638 [default: @code{"^./^[]^"}]
15639 specifies a directory where to look for object and library files. Multiple
15640 @code{obj_dir} lines can be specified, and they will be searched in the order
15643 @item comp_opt=SWITCHES
15644 [default: @code{""}]
15645 creates a variable which can be referred to subsequently by using
15646 the @code{$@{comp_opt@}} notation. This is intended to store the default
15647 switches given to @command{gnatmake} and @command{gcc}.
15649 @item bind_opt=SWITCHES
15650 [default: @code{""}]
15651 creates a variable which can be referred to subsequently by using
15652 the @samp{$@{bind_opt@}} notation. This is intended to store the default
15653 switches given to @command{gnatbind}.
15655 @item link_opt=SWITCHES
15656 [default: @code{""}]
15657 creates a variable which can be referred to subsequently by using
15658 the @samp{$@{link_opt@}} notation. This is intended to store the default
15659 switches given to @command{gnatlink}.
15661 @item main=EXECUTABLE
15662 [default: @code{""}]
15663 specifies the name of the executable for the application. This variable can
15664 be referred to in the following lines by using the @samp{$@{main@}} notation.
15667 @item comp_cmd=COMMAND
15668 [default: @code{"GNAT COMPILE /SEARCH=$@{src_dir@} /DEBUG /TRY_SEMANTICS"}]
15671 @item comp_cmd=COMMAND
15672 [default: @code{"gcc -c -I$@{src_dir@} -g -gnatq"}]
15674 specifies the command used to compile a single file in the application.
15677 @item make_cmd=COMMAND
15678 [default: @code{"GNAT MAKE $@{main@}
15679 /SOURCE_SEARCH=$@{src_dir@} /OBJECT_SEARCH=$@{obj_dir@}
15680 /DEBUG /TRY_SEMANTICS /COMPILER_QUALIFIERS $@{comp_opt@}
15681 /BINDER_QUALIFIERS $@{bind_opt@} /LINKER_QUALIFIERS $@{link_opt@}"}]
15684 @item make_cmd=COMMAND
15685 [default: @code{"gnatmake $@{main@} -aI$@{src_dir@}
15686 -aO$@{obj_dir@} -g -gnatq -cargs $@{comp_opt@}
15687 -bargs $@{bind_opt@} -largs $@{link_opt@}"}]
15689 specifies the command used to recompile the whole application.
15691 @item run_cmd=COMMAND
15692 [default: @code{"$@{main@}"}]
15693 specifies the command used to run the application.
15695 @item debug_cmd=COMMAND
15696 [default: @code{"gdb $@{main@}"}]
15697 specifies the command used to debug the application
15702 @command{gnatxref} and @command{gnatfind} only take into account the
15703 @code{src_dir} and @code{obj_dir} lines, and ignore the others.
15705 @node Regular Expressions in gnatfind and gnatxref
15706 @section Regular Expressions in @code{gnatfind} and @code{gnatxref}
15709 As specified in the section about @command{gnatfind}, the pattern can be a
15710 regular expression. Actually, there are to set of regular expressions
15711 which are recognized by the program:
15714 @item globbing patterns
15715 These are the most usual regular expression. They are the same that you
15716 generally used in a Unix shell command line, or in a DOS session.
15718 Here is a more formal grammar:
15725 term ::= elmt -- matches elmt
15726 term ::= elmt elmt -- concatenation (elmt then elmt)
15727 term ::= * -- any string of 0 or more characters
15728 term ::= ? -- matches any character
15729 term ::= [char @{char@}] -- matches any character listed
15730 term ::= [char - char] -- matches any character in range
15734 @item full regular expression
15735 The second set of regular expressions is much more powerful. This is the
15736 type of regular expressions recognized by utilities such a @file{grep}.
15738 The following is the form of a regular expression, expressed in Ada
15739 reference manual style BNF is as follows
15746 regexp ::= term @{| term@} -- alternation (term or term @dots{})
15748 term ::= item @{item@} -- concatenation (item then item)
15750 item ::= elmt -- match elmt
15751 item ::= elmt * -- zero or more elmt's
15752 item ::= elmt + -- one or more elmt's
15753 item ::= elmt ? -- matches elmt or nothing
15756 elmt ::= nschar -- matches given character
15757 elmt ::= [nschar @{nschar@}] -- matches any character listed
15758 elmt ::= [^^^ nschar @{nschar@}] -- matches any character not listed
15759 elmt ::= [char - char] -- matches chars in given range
15760 elmt ::= \ char -- matches given character
15761 elmt ::= . -- matches any single character
15762 elmt ::= ( regexp ) -- parens used for grouping
15764 char ::= any character, including special characters
15765 nschar ::= any character except ()[].*+?^^^
15769 Following are a few examples:
15773 will match any of the two strings @samp{abcde} and @samp{fghi},
15776 will match any string like @samp{abd}, @samp{abcd}, @samp{abccd},
15777 @samp{abcccd}, and so on,
15780 will match any string which has only lowercase characters in it (and at
15781 least one character.
15786 @node Examples of gnatxref Usage
15787 @section Examples of @code{gnatxref} Usage
15789 @subsection General Usage
15792 For the following examples, we will consider the following units:
15794 @smallexample @c ada
15800 3: procedure Foo (B : in Integer);
15807 1: package body Main is
15808 2: procedure Foo (B : in Integer) is
15819 2: procedure Print (B : Integer);
15828 The first thing to do is to recompile your application (for instance, in
15829 that case just by doing a @samp{gnatmake main}, so that GNAT generates
15830 the cross-referencing information.
15831 You can then issue any of the following commands:
15833 @item gnatxref main.adb
15834 @code{gnatxref} generates cross-reference information for main.adb
15835 and every unit 'with'ed by main.adb.
15837 The output would be:
15845 Decl: main.ads 3:20
15846 Body: main.adb 2:20
15847 Ref: main.adb 4:13 5:13 6:19
15850 Ref: main.adb 6:8 7:8
15860 Decl: main.ads 3:15
15861 Body: main.adb 2:15
15864 Body: main.adb 1:14
15867 Ref: main.adb 6:12 7:12
15871 that is the entity @code{Main} is declared in main.ads, line 2, column 9,
15872 its body is in main.adb, line 1, column 14 and is not referenced any where.
15874 The entity @code{Print} is declared in bar.ads, line 2, column 15 and it
15875 it referenced in main.adb, line 6 column 12 and line 7 column 12.
15877 @item gnatxref package1.adb package2.ads
15878 @code{gnatxref} will generates cross-reference information for
15879 package1.adb, package2.ads and any other package 'with'ed by any
15885 @subsection Using gnatxref with vi
15887 @code{gnatxref} can generate a tags file output, which can be used
15888 directly from @command{vi}. Note that the standard version of @command{vi}
15889 will not work properly with overloaded symbols. Consider using another
15890 free implementation of @command{vi}, such as @command{vim}.
15893 $ gnatxref -v gnatfind.adb > tags
15897 will generate the tags file for @code{gnatfind} itself (if the sources
15898 are in the search path!).
15900 From @command{vi}, you can then use the command @samp{:tag @var{entity}}
15901 (replacing @var{entity} by whatever you are looking for), and vi will
15902 display a new file with the corresponding declaration of entity.
15905 @node Examples of gnatfind Usage
15906 @section Examples of @code{gnatfind} Usage
15910 @item gnatfind ^-f^/FULL_PATHNAME^ xyz:main.adb
15911 Find declarations for all entities xyz referenced at least once in
15912 main.adb. The references are search in every library file in the search
15915 The directories will be printed as well (as the @samp{^-f^/FULL_PATHNAME^}
15918 The output will look like:
15920 ^directory/^[directory]^main.ads:106:14: xyz <= declaration
15921 ^directory/^[directory]^main.adb:24:10: xyz <= body
15922 ^directory/^[directory]^foo.ads:45:23: xyz <= declaration
15926 that is to say, one of the entities xyz found in main.adb is declared at
15927 line 12 of main.ads (and its body is in main.adb), and another one is
15928 declared at line 45 of foo.ads
15930 @item gnatfind ^-fs^/FULL_PATHNAME/SOURCE_LINE^ xyz:main.adb
15931 This is the same command as the previous one, instead @code{gnatfind} will
15932 display the content of the Ada source file lines.
15934 The output will look like:
15937 ^directory/^[directory]^main.ads:106:14: xyz <= declaration
15939 ^directory/^[directory]^main.adb:24:10: xyz <= body
15941 ^directory/^[directory]^foo.ads:45:23: xyz <= declaration
15946 This can make it easier to find exactly the location your are looking
15949 @item gnatfind ^-r^/REFERENCES^ "*x*":main.ads:123 foo.adb
15950 Find references to all entities containing an x that are
15951 referenced on line 123 of main.ads.
15952 The references will be searched only in main.ads and foo.adb.
15954 @item gnatfind main.ads:123
15955 Find declarations and bodies for all entities that are referenced on
15956 line 123 of main.ads.
15958 This is the same as @code{gnatfind "*":main.adb:123}.
15960 @item gnatfind ^mydir/^[mydir]^main.adb:123:45
15961 Find the declaration for the entity referenced at column 45 in
15962 line 123 of file main.adb in directory mydir. Note that it
15963 is usual to omit the identifier name when the column is given,
15964 since the column position identifies a unique reference.
15966 The column has to be the beginning of the identifier, and should not
15967 point to any character in the middle of the identifier.
15971 @c *********************************
15972 @node The GNAT Pretty-Printer gnatpp
15973 @chapter The GNAT Pretty-Printer @command{gnatpp}
15975 @cindex Pretty-Printer
15978 ^The @command{gnatpp} tool^GNAT PRETTY^ is an ASIS-based utility
15979 for source reformatting / pretty-printing.
15980 It takes an Ada source file as input and generates a reformatted
15982 You can specify various style directives via switches; e.g.,
15983 identifier case conventions, rules of indentation, and comment layout.
15985 To produce a reformatted file, @command{gnatpp} generates and uses the ASIS
15986 tree for the input source and thus requires the input to be syntactically and
15987 semantically legal.
15988 If this condition is not met, @command{gnatpp} will terminate with an
15989 error message; no output file will be generated.
15991 If the source files presented to @command{gnatpp} contain
15992 preprocessing directives, then the output file will
15993 correspond to the generated source after all
15994 preprocessing is carried out. There is no way
15995 using @command{gnatpp} to obtain pretty printed files that
15996 include the preprocessing directives.
15998 If the compilation unit
15999 contained in the input source depends semantically upon units located
16000 outside the current directory, you have to provide the source search path
16001 when invoking @command{gnatpp}, if these units are contained in files with
16002 names that do not follow the GNAT file naming rules, you have to provide
16003 the configuration file describing the corresponding naming scheme;
16004 see the description of the @command{gnatpp}
16005 switches below. Another possibility is to use a project file and to
16006 call @command{gnatpp} through the @command{gnat} driver
16008 The @command{gnatpp} command has the form
16011 $ gnatpp @ovar{switches} @var{filename}
16018 @var{switches} is an optional sequence of switches defining such properties as
16019 the formatting rules, the source search path, and the destination for the
16023 @var{filename} is the name (including the extension) of the source file to
16024 reformat; ``wildcards'' or several file names on the same gnatpp command are
16025 allowed. The file name may contain path information; it does not have to
16026 follow the GNAT file naming rules
16030 * Switches for gnatpp::
16031 * Formatting Rules::
16034 @node Switches for gnatpp
16035 @section Switches for @command{gnatpp}
16038 The following subsections describe the various switches accepted by
16039 @command{gnatpp}, organized by category.
16042 You specify a switch by supplying a name and generally also a value.
16043 In many cases the values for a switch with a given name are incompatible with
16045 (for example the switch that controls the casing of a reserved word may have
16046 exactly one value: upper case, lower case, or
16047 mixed case) and thus exactly one such switch can be in effect for an
16048 invocation of @command{gnatpp}.
16049 If more than one is supplied, the last one is used.
16050 However, some values for the same switch are mutually compatible.
16051 You may supply several such switches to @command{gnatpp}, but then
16052 each must be specified in full, with both the name and the value.
16053 Abbreviated forms (the name appearing once, followed by each value) are
16055 For example, to set
16056 the alignment of the assignment delimiter both in declarations and in
16057 assignment statements, you must write @option{-A2A3}
16058 (or @option{-A2 -A3}), but not @option{-A23}.
16062 In many cases the set of options for a given qualifier are incompatible with
16063 each other (for example the qualifier that controls the casing of a reserved
16064 word may have exactly one option, which specifies either upper case, lower
16065 case, or mixed case), and thus exactly one such option can be in effect for
16066 an invocation of @command{gnatpp}.
16067 If more than one is supplied, the last one is used.
16068 However, some qualifiers have options that are mutually compatible,
16069 and then you may then supply several such options when invoking
16073 In most cases, it is obvious whether or not the
16074 ^values for a switch with a given name^options for a given qualifier^
16075 are compatible with each other.
16076 When the semantics might not be evident, the summaries below explicitly
16077 indicate the effect.
16080 * Alignment Control::
16082 * Construct Layout Control::
16083 * General Text Layout Control::
16084 * Other Formatting Options::
16085 * Setting the Source Search Path::
16086 * Output File Control::
16087 * Other gnatpp Switches::
16090 @node Alignment Control
16091 @subsection Alignment Control
16092 @cindex Alignment control in @command{gnatpp}
16095 Programs can be easier to read if certain constructs are vertically aligned.
16096 By default all alignments are set ON.
16097 Through the @option{^-A0^/ALIGN=OFF^} switch you may reset the default to
16098 OFF, and then use one or more of the other
16099 ^@option{-A@var{n}} switches^@option{/ALIGN} options^
16100 to activate alignment for specific constructs.
16103 @cindex @option{^-A@var{n}^/ALIGN^} (@command{gnatpp})
16107 Set all alignments to ON
16110 @item ^-A0^/ALIGN=OFF^
16111 Set all alignments to OFF
16113 @item ^-A1^/ALIGN=COLONS^
16114 Align @code{:} in declarations
16116 @item ^-A2^/ALIGN=DECLARATIONS^
16117 Align @code{:=} in initializations in declarations
16119 @item ^-A3^/ALIGN=STATEMENTS^
16120 Align @code{:=} in assignment statements
16122 @item ^-A4^/ALIGN=ARROWS^
16123 Align @code{=>} in associations
16125 @item ^-A5^/ALIGN=COMPONENT_CLAUSES^
16126 Align @code{at} keywords in the component clauses in record
16127 representation clauses
16131 The @option{^-A^/ALIGN^} switches are mutually compatible; any combination
16134 @node Casing Control
16135 @subsection Casing Control
16136 @cindex Casing control in @command{gnatpp}
16139 @command{gnatpp} allows you to specify the casing for reserved words,
16140 pragma names, attribute designators and identifiers.
16141 For identifiers you may define a
16142 general rule for name casing but also override this rule
16143 via a set of dictionary files.
16145 Three types of casing are supported: lower case, upper case, and mixed case.
16146 Lower and upper case are self-explanatory (but since some letters in
16147 Latin1 and other GNAT-supported character sets
16148 exist only in lower-case form, an upper case conversion will have no
16150 ``Mixed case'' means that the first letter, and also each letter immediately
16151 following an underscore, are converted to their uppercase forms;
16152 all the other letters are converted to their lowercase forms.
16155 @cindex @option{^-a@var{x}^/ATTRIBUTE^} (@command{gnatpp})
16156 @item ^-aL^/ATTRIBUTE_CASING=LOWER_CASE^
16157 Attribute designators are lower case
16159 @item ^-aU^/ATTRIBUTE_CASING=UPPER_CASE^
16160 Attribute designators are upper case
16162 @item ^-aM^/ATTRIBUTE_CASING=MIXED_CASE^
16163 Attribute designators are mixed case (this is the default)
16165 @cindex @option{^-k@var{x}^/KEYWORD_CASING^} (@command{gnatpp})
16166 @item ^-kL^/KEYWORD_CASING=LOWER_CASE^
16167 Keywords (technically, these are known in Ada as @emph{reserved words}) are
16168 lower case (this is the default)
16170 @item ^-kU^/KEYWORD_CASING=UPPER_CASE^
16171 Keywords are upper case
16173 @cindex @option{^-n@var{x}^/NAME_CASING^} (@command{gnatpp})
16174 @item ^-nD^/NAME_CASING=AS_DECLARED^
16175 Name casing for defining occurrences are as they appear in the source file
16176 (this is the default)
16178 @item ^-nU^/NAME_CASING=UPPER_CASE^
16179 Names are in upper case
16181 @item ^-nL^/NAME_CASING=LOWER_CASE^
16182 Names are in lower case
16184 @item ^-nM^/NAME_CASING=MIXED_CASE^
16185 Names are in mixed case
16187 @cindex @option{^-p@var{x}^/PRAGMA_CASING^} (@command{gnatpp})
16188 @item ^-pL^/PRAGMA_CASING=LOWER_CASE^
16189 Pragma names are lower case
16191 @item ^-pU^/PRAGMA_CASING=UPPER_CASE^
16192 Pragma names are upper case
16194 @item ^-pM^/PRAGMA_CASING=MIXED_CASE^
16195 Pragma names are mixed case (this is the default)
16197 @item ^-D@var{file}^/DICTIONARY=@var{file}^
16198 @cindex @option{^-D^/DICTIONARY^} (@command{gnatpp})
16199 Use @var{file} as a @emph{dictionary file} that defines
16200 the casing for a set of specified names,
16201 thereby overriding the effect on these names by
16202 any explicit or implicit
16203 ^-n^/NAME_CASING^ switch.
16204 To supply more than one dictionary file,
16205 use ^several @option{-D} switches^a list of files as options^.
16208 @option{gnatpp} implicitly uses a @emph{default dictionary file}
16209 to define the casing for the Ada predefined names and
16210 the names declared in the GNAT libraries.
16212 @item ^-D-^/SPECIFIC_CASING^
16213 @cindex @option{^-D-^/SPECIFIC_CASING^} (@command{gnatpp})
16214 Do not use the default dictionary file;
16215 instead, use the casing
16216 defined by a @option{^-n^/NAME_CASING^} switch and any explicit
16221 The structure of a dictionary file, and details on the conventions
16222 used in the default dictionary file, are defined in @ref{Name Casing}.
16224 The @option{^-D-^/SPECIFIC_CASING^} and
16225 @option{^-D@var{file}^/DICTIONARY=@var{file}^} switches are mutually
16228 @node Construct Layout Control
16229 @subsection Construct Layout Control
16230 @cindex Layout control in @command{gnatpp}
16233 This group of @command{gnatpp} switches controls the layout of comments and
16234 complex syntactic constructs. See @ref{Formatting Comments} for details
16238 @cindex @option{^-c@var{n}^/COMMENTS_LAYOUT^} (@command{gnatpp})
16239 @item ^-c0^/COMMENTS_LAYOUT=UNTOUCHED^
16240 All the comments remain unchanged
16242 @item ^-c1^/COMMENTS_LAYOUT=DEFAULT^
16243 GNAT-style comment line indentation (this is the default).
16245 @item ^-c2^/COMMENTS_LAYOUT=STANDARD_INDENT^
16246 Reference-manual comment line indentation.
16248 @item ^-c3^/COMMENTS_LAYOUT=GNAT_BEGINNING^
16249 GNAT-style comment beginning
16251 @item ^-c4^/COMMENTS_LAYOUT=REFORMAT^
16252 Reformat comment blocks
16254 @item ^-c5^/COMMENTS_LAYOUT=KEEP_SPECIAL^
16255 Keep unchanged special form comments
16257 Reformat comment blocks
16259 @cindex @option{^-l@var{n}^/CONSTRUCT_LAYOUT^} (@command{gnatpp})
16260 @item ^-l1^/CONSTRUCT_LAYOUT=GNAT^
16261 GNAT-style layout (this is the default)
16263 @item ^-l2^/CONSTRUCT_LAYOUT=COMPACT^
16266 @item ^-l3^/CONSTRUCT_LAYOUT=UNCOMPACT^
16269 @cindex @option{^-N^/NOTABS^} (@command{gnatpp})
16271 All the VT characters are removed from the comment text. All the HT characters
16272 are expanded with the sequences of space characters to get to the next tab
16275 @cindex @option{^--no-separate-is^/NO_SEPARATE_IS^} (@command{gnatpp})
16276 @item ^--no-separate-is^/NO_SEPARATE_IS^
16277 Do not place the keyword @code{is} on a separate line in a subprogram body in
16278 case if the spec occupies more then one line.
16280 @cindex @option{^--separate-loop-then^/SEPARATE_LOOP_THEN^} (@command{gnatpp})
16281 @item ^--separate-loop-then^/SEPARATE_LOOP_THEN^
16282 Place the keyword @code{loop} in FOR and WHILE loop statements and the
16283 keyword @code{then} in IF statements on a separate line.
16285 @cindex @option{^--no-separate-loop-then^/NO_SEPARATE_LOOP_THEN^} (@command{gnatpp})
16286 @item ^--no-separate-loop-then^/NO_SEPARATE_LOOP_THEN^
16287 Do not place the keyword @code{loop} in FOR and WHILE loop statements and the
16288 keyword @code{then} in IF statements on a separate line. This option is
16289 incompatible with @option{^--separate-loop-then^/SEPARATE_LOOP_THEN^} option.
16291 @cindex @option{^--use-on-new-line^/USE_ON_NEW_LINE^} (@command{gnatpp})
16292 @item ^--use-on-new-line^/USE_ON_NEW_LINE^
16293 Start each USE clause in a context clause from a separate line.
16295 @cindex @option{^--separate-stmt-name^/STMT_NAME_ON_NEW_LINE^} (@command{gnatpp})
16296 @item ^--separate-stmt-name^/STMT_NAME_ON_NEW_LINE^
16297 Use a separate line for a loop or block statement name, but do not use an extra
16298 indentation level for the statement itself.
16304 The @option{-c1} and @option{-c2} switches are incompatible.
16305 The @option{-c3} and @option{-c4} switches are compatible with each other and
16306 also with @option{-c1} and @option{-c2}. The @option{-c0} switch disables all
16307 the other comment formatting switches.
16309 The @option{-l1}, @option{-l2}, and @option{-l3} switches are incompatible.
16314 For the @option{/COMMENTS_LAYOUT} qualifier:
16317 The @option{DEFAULT} and @option{STANDARD_INDENT} options are incompatible.
16319 The @option{GNAT_BEGINNING} and @option{REFORMAT} options are compatible with
16320 each other and also with @option{DEFAULT} and @option{STANDARD_INDENT}.
16324 The @option{GNAT}, @option{COMPACT}, and @option{UNCOMPACT} options for the
16325 @option{/CONSTRUCT_LAYOUT} qualifier are incompatible.
16328 @node General Text Layout Control
16329 @subsection General Text Layout Control
16332 These switches allow control over line length and indentation.
16335 @item ^-M@var{nnn}^/LINE_LENGTH_MAX=@var{nnn}^
16336 @cindex @option{^-M^/LINE_LENGTH^} (@command{gnatpp})
16337 Maximum line length, @var{nnn} from 32@dots{}256, the default value is 79
16339 @item ^-i@var{nnn}^/INDENTATION_LEVEL=@var{nnn}^
16340 @cindex @option{^-i^/INDENTATION_LEVEL^} (@command{gnatpp})
16341 Indentation level, @var{nnn} from 1@dots{}9, the default value is 3
16343 @item ^-cl@var{nnn}^/CONTINUATION_INDENT=@var{nnn}^
16344 @cindex @option{^-cl^/CONTINUATION_INDENT^} (@command{gnatpp})
16345 Indentation level for continuation lines (relative to the line being
16346 continued), @var{nnn} from 1@dots{}9.
16348 value is one less then the (normal) indentation level, unless the
16349 indentation is set to 1 (in which case the default value for continuation
16350 line indentation is also 1)
16353 @node Other Formatting Options
16354 @subsection Other Formatting Options
16357 These switches control the inclusion of missing end/exit labels, and
16358 the indentation level in @b{case} statements.
16361 @item ^-e^/NO_MISSED_LABELS^
16362 @cindex @option{^-e^/NO_MISSED_LABELS^} (@command{gnatpp})
16363 Do not insert missing end/exit labels. An end label is the name of
16364 a construct that may optionally be repeated at the end of the
16365 construct's declaration;
16366 e.g., the names of packages, subprograms, and tasks.
16367 An exit label is the name of a loop that may appear as target
16368 of an exit statement within the loop.
16369 By default, @command{gnatpp} inserts these end/exit labels when
16370 they are absent from the original source. This option suppresses such
16371 insertion, so that the formatted source reflects the original.
16373 @item ^-ff^/FORM_FEED_AFTER_PRAGMA_PAGE^
16374 @cindex @option{^-ff^/FORM_FEED_AFTER_PRAGMA_PAGE^} (@command{gnatpp})
16375 Insert a Form Feed character after a pragma Page.
16377 @item ^-T@var{nnn}^/MAX_INDENT=@var{nnn}^
16378 @cindex @option{^-T^/MAX_INDENT^} (@command{gnatpp})
16379 Do not use an additional indentation level for @b{case} alternatives
16380 and variants if there are @var{nnn} or more (the default
16382 If @var{nnn} is 0, an additional indentation level is
16383 used for @b{case} alternatives and variants regardless of their number.
16386 @node Setting the Source Search Path
16387 @subsection Setting the Source Search Path
16390 To define the search path for the input source file, @command{gnatpp}
16391 uses the same switches as the GNAT compiler, with the same effects.
16394 @item ^-I^/SEARCH=^@var{dir}
16395 @cindex @option{^-I^/SEARCH^} (@code{gnatpp})
16396 The same as the corresponding gcc switch
16398 @item ^-I-^/NOCURRENT_DIRECTORY^
16399 @cindex @option{^-I-^/NOCURRENT_DIRECTORY^} (@code{gnatpp})
16400 The same as the corresponding gcc switch
16402 @item ^-gnatec^/CONFIGURATION_PRAGMAS_FILE^=@var{path}
16403 @cindex @option{^-gnatec^/CONFIGURATION_PRAGMAS_FILE^} (@code{gnatpp})
16404 The same as the corresponding gcc switch
16406 @item ^--RTS^/RUNTIME_SYSTEM^=@var{path}
16407 @cindex @option{^--RTS^/RUNTIME_SYSTEM^} (@code{gnatpp})
16408 The same as the corresponding gcc switch
16412 @node Output File Control
16413 @subsection Output File Control
16416 By default the output is sent to the file whose name is obtained by appending
16417 the ^@file{.pp}^@file{$PP}^ suffix to the name of the input file
16418 (if the file with this name already exists, it is unconditionally overwritten).
16419 Thus if the input file is @file{^my_ada_proc.adb^MY_ADA_PROC.ADB^} then
16420 @command{gnatpp} will produce @file{^my_ada_proc.adb.pp^MY_ADA_PROC.ADB$PP^}
16422 The output may be redirected by the following switches:
16425 @item ^-pipe^/STANDARD_OUTPUT^
16426 @cindex @option{^-pipe^/STANDARD_OUTPUT^} (@code{gnatpp})
16427 Send the output to @code{Standard_Output}
16429 @item ^-o @var{output_file}^/OUTPUT=@var{output_file}^
16430 @cindex @option{^-o^/OUTPUT^} (@code{gnatpp})
16431 Write the output into @var{output_file}.
16432 If @var{output_file} already exists, @command{gnatpp} terminates without
16433 reading or processing the input file.
16435 @item ^-of ^/FORCED_OUTPUT=^@var{output_file}
16436 @cindex @option{^-of^/FORCED_OUTPUT^} (@code{gnatpp})
16437 Write the output into @var{output_file}, overwriting the existing file
16438 (if one is present).
16440 @item ^-r^/REPLACE^
16441 @cindex @option{^-r^/REPLACE^} (@code{gnatpp})
16442 Replace the input source file with the reformatted output, and copy the
16443 original input source into the file whose name is obtained by appending the
16444 ^@file{.npp}^@file{$NPP}^ suffix to the name of the input file.
16445 If a file with this name already exists, @command{gnatpp} terminates without
16446 reading or processing the input file.
16448 @item ^-rf^/OVERRIDING_REPLACE^
16449 @cindex @option{^-rf^/OVERRIDING_REPLACE^} (@code{gnatpp})
16450 Like @option{^-r^/REPLACE^} except that if the file with the specified name
16451 already exists, it is overwritten.
16453 @item ^-rnb^/REPLACE_NO_BACKUP^
16454 @cindex @option{^-rnb^/REPLACE_NO_BACKUP^} (@code{gnatpp})
16455 Replace the input source file with the reformatted output without
16456 creating any backup copy of the input source.
16458 @item ^--eol=@var{xxx}^/END_OF_LINE=@var{xxx}^
16459 @cindex @option{^--eol^/END_OF_LINE^} (@code{gnatpp})
16460 Specifies the format of the reformatted output file. The @var{xxx}
16461 ^string specified with the switch^option^ may be either
16463 @item ``@option{^dos^DOS^}'' MS DOS style, lines end with CR LF characters
16464 @item ``@option{^crlf^CRLF^}''
16465 the same as @option{^crlf^CRLF^}
16466 @item ``@option{^unix^UNIX^}'' UNIX style, lines end with LF character
16467 @item ``@option{^lf^LF^}''
16468 the same as @option{^unix^UNIX^}
16471 @item ^-W^/RESULT_ENCODING=^@var{e}
16472 @cindex @option{^-W^/RESULT_ENCODING=^} (@command{gnatpp})
16473 Specify the wide character encoding method used to write the code in the
16475 @var{e} is one of the following:
16483 Upper half encoding
16485 @item ^s^SHIFT_JIS^
16495 Brackets encoding (default value)
16501 Options @option{^-pipe^/STANDARD_OUTPUT^},
16502 @option{^-o^/OUTPUT^} and
16503 @option{^-of^/FORCED_OUTPUT^} are allowed only if the call to gnatpp
16504 contains only one file to reformat.
16506 @option{^--eol^/END_OF_LINE^}
16508 @option{^-W^/RESULT_ENCODING^}
16509 cannot be used together
16510 with @option{^-pipe^/STANDARD_OUTPUT^} option.
16512 @node Other gnatpp Switches
16513 @subsection Other @code{gnatpp} Switches
16516 The additional @command{gnatpp} switches are defined in this subsection.
16519 @item ^-files @var{filename}^/FILES=@var{output_file}^
16520 @cindex @option{^-files^/FILES^} (@code{gnatpp})
16521 Take the argument source files from the specified file. This file should be an
16522 ordinary textual file containing file names separated by spaces or
16523 line breaks. You can use this switch more then once in the same call to
16524 @command{gnatpp}. You also can combine this switch with explicit list of
16527 @item ^-v^/VERBOSE^
16528 @cindex @option{^-v^/VERBOSE^} (@code{gnatpp})
16530 @command{gnatpp} generates version information and then
16531 a trace of the actions it takes to produce or obtain the ASIS tree.
16533 @item ^-w^/WARNINGS^
16534 @cindex @option{^-w^/WARNINGS^} (@code{gnatpp})
16536 @command{gnatpp} generates a warning whenever it cannot provide
16537 a required layout in the result source.
16540 @node Formatting Rules
16541 @section Formatting Rules
16544 The following subsections show how @command{gnatpp} treats ``white space'',
16545 comments, program layout, and name casing.
16546 They provide the detailed descriptions of the switches shown above.
16549 * White Space and Empty Lines::
16550 * Formatting Comments::
16551 * Construct Layout::
16555 @node White Space and Empty Lines
16556 @subsection White Space and Empty Lines
16559 @command{gnatpp} does not have an option to control space characters.
16560 It will add or remove spaces according to the style illustrated by the
16561 examples in the @cite{Ada Reference Manual}.
16563 The only format effectors
16564 (see @cite{Ada Reference Manual}, paragraph 2.1(13))
16565 that will appear in the output file are platform-specific line breaks,
16566 and also format effectors within (but not at the end of) comments.
16567 In particular, each horizontal tab character that is not inside
16568 a comment will be treated as a space and thus will appear in the
16569 output file as zero or more spaces depending on
16570 the reformatting of the line in which it appears.
16571 The only exception is a Form Feed character, which is inserted after a
16572 pragma @code{Page} when @option{-ff} is set.
16574 The output file will contain no lines with trailing ``white space'' (spaces,
16577 Empty lines in the original source are preserved
16578 only if they separate declarations or statements.
16579 In such contexts, a
16580 sequence of two or more empty lines is replaced by exactly one empty line.
16581 Note that a blank line will be removed if it separates two ``comment blocks''
16582 (a comment block is a sequence of whole-line comments).
16583 In order to preserve a visual separation between comment blocks, use an
16584 ``empty comment'' (a line comprising only hyphens) rather than an empty line.
16585 Likewise, if for some reason you wish to have a sequence of empty lines,
16586 use a sequence of empty comments instead.
16588 @node Formatting Comments
16589 @subsection Formatting Comments
16592 Comments in Ada code are of two kinds:
16595 a @emph{whole-line comment}, which appears by itself (possibly preceded by
16596 ``white space'') on a line
16599 an @emph{end-of-line comment}, which follows some other Ada lexical element
16604 The indentation of a whole-line comment is that of either
16605 the preceding or following line in
16606 the formatted source, depending on switch settings as will be described below.
16608 For an end-of-line comment, @command{gnatpp} leaves the same number of spaces
16609 between the end of the preceding Ada lexical element and the beginning
16610 of the comment as appear in the original source,
16611 unless either the comment has to be split to
16612 satisfy the line length limitation, or else the next line contains a
16613 whole line comment that is considered a continuation of this end-of-line
16614 comment (because it starts at the same position).
16616 cases, the start of the end-of-line comment is moved right to the nearest
16617 multiple of the indentation level.
16618 This may result in a ``line overflow'' (the right-shifted comment extending
16619 beyond the maximum line length), in which case the comment is split as
16622 There is a difference between @option{^-c1^/COMMENTS_LAYOUT=DEFAULT^}
16623 (GNAT-style comment line indentation)
16624 and @option{^-c2^/COMMENTS_LAYOUT=STANDARD_INDENT^}
16625 (reference-manual comment line indentation).
16626 With reference-manual style, a whole-line comment is indented as if it
16627 were a declaration or statement at the same place
16628 (i.e., according to the indentation of the preceding line(s)).
16629 With GNAT style, a whole-line comment that is immediately followed by an
16630 @b{if} or @b{case} statement alternative, a record variant, or the reserved
16631 word @b{begin}, is indented based on the construct that follows it.
16634 @smallexample @c ada
16646 Reference-manual indentation produces:
16648 @smallexample @c ada
16660 while GNAT-style indentation produces:
16662 @smallexample @c ada
16674 The @option{^-c3^/COMMENTS_LAYOUT=GNAT_BEGINNING^} switch
16675 (GNAT style comment beginning) has the following
16680 For each whole-line comment that does not end with two hyphens,
16681 @command{gnatpp} inserts spaces if necessary after the starting two hyphens
16682 to ensure that there are at least two spaces between these hyphens and the
16683 first non-blank character of the comment.
16687 For an end-of-line comment, if in the original source the next line is a
16688 whole-line comment that starts at the same position
16689 as the end-of-line comment,
16690 then the whole-line comment (and all whole-line comments
16691 that follow it and that start at the same position)
16692 will start at this position in the output file.
16695 That is, if in the original source we have:
16697 @smallexample @c ada
16700 A := B + C; -- B must be in the range Low1..High1
16701 -- C must be in the range Low2..High2
16702 --B+C will be in the range Low1+Low2..High1+High2
16708 Then in the formatted source we get
16710 @smallexample @c ada
16713 A := B + C; -- B must be in the range Low1..High1
16714 -- C must be in the range Low2..High2
16715 -- B+C will be in the range Low1+Low2..High1+High2
16721 A comment that exceeds the line length limit will be split.
16723 @option{^-c4^/COMMENTS_LAYOUT=REFORMAT^} (reformat comment blocks) is set and
16724 the line belongs to a reformattable block, splitting the line generates a
16725 @command{gnatpp} warning.
16726 The @option{^-c4^/COMMENTS_LAYOUT=REFORMAT^} switch specifies that whole-line
16727 comments may be reformatted in typical
16728 word processor style (that is, moving words between lines and putting as
16729 many words in a line as possible).
16732 The @option{^-c5^/COMMENTS_LAYOUT=KEEP_SPECIAL^} switch specifies, that comments
16733 that has a special format (that is, a character that is neither a letter nor digit
16734 not white space nor line break immediately following the leading @code{--} of
16735 the comment) should be without any change moved from the argument source
16736 into reformatted source. This switch allows to preserve comments that are used
16737 as a special marks in the code (e.g.@: SPARK annotation).
16739 @node Construct Layout
16740 @subsection Construct Layout
16743 In several cases the suggested layout in the Ada Reference Manual includes
16744 an extra level of indentation that many programmers prefer to avoid. The
16745 affected cases include:
16749 @item Record type declaration (RM 3.8)
16751 @item Record representation clause (RM 13.5.1)
16753 @item Loop statement in case if a loop has a statement identifier (RM 5.6)
16755 @item Block statement in case if a block has a statement identifier (RM 5.6)
16759 In compact mode (when GNAT style layout or compact layout is set),
16760 the pretty printer uses one level of indentation instead
16761 of two. This is achieved in the record definition and record representation
16762 clause cases by putting the @code{record} keyword on the same line as the
16763 start of the declaration or representation clause, and in the block and loop
16764 case by putting the block or loop header on the same line as the statement
16768 The difference between GNAT style @option{^-l1^/CONSTRUCT_LAYOUT=GNAT^}
16769 and compact @option{^-l2^/CONSTRUCT_LAYOUT=COMPACT^}
16770 layout on the one hand, and uncompact layout
16771 @option{^-l3^/CONSTRUCT_LAYOUT=UNCOMPACT^} on the other hand,
16772 can be illustrated by the following examples:
16776 @multitable @columnfractions .5 .5
16777 @item @i{GNAT style, compact layout} @tab @i{Uncompact layout}
16780 @smallexample @c ada
16787 @smallexample @c ada
16796 @smallexample @c ada
16798 a at 0 range 0 .. 31;
16799 b at 4 range 0 .. 31;
16803 @smallexample @c ada
16806 a at 0 range 0 .. 31;
16807 b at 4 range 0 .. 31;
16812 @smallexample @c ada
16820 @smallexample @c ada
16830 @smallexample @c ada
16831 Clear : for J in 1 .. 10 loop
16836 @smallexample @c ada
16838 for J in 1 .. 10 loop
16849 GNAT style, compact layout Uncompact layout
16851 type q is record type q is
16852 a : integer; record
16853 b : integer; a : integer;
16854 end record; b : integer;
16857 for q use record for q use
16858 a at 0 range 0 .. 31; record
16859 b at 4 range 0 .. 31; a at 0 range 0 .. 31;
16860 end record; b at 4 range 0 .. 31;
16863 Block : declare Block :
16864 A : Integer := 3; declare
16865 begin A : Integer := 3;
16867 end Block; Proc (A, A);
16870 Clear : for J in 1 .. 10 loop Clear :
16871 A (J) := 0; for J in 1 .. 10 loop
16872 end loop Clear; A (J) := 0;
16879 A further difference between GNAT style layout and compact layout is that
16880 GNAT style layout inserts empty lines as separation for
16881 compound statements, return statements and bodies.
16883 Note that the layout specified by
16884 @option{^--separate-stmt-name^/STMT_NAME_ON_NEW_LINE^}
16885 for named block and loop statements overrides the layout defined by these
16886 constructs by @option{^-l1^/CONSTRUCT_LAYOUT=GNAT^},
16887 @option{^-l2^/CONSTRUCT_LAYOUT=COMPACT^} or
16888 @option{^-l3^/CONSTRUCT_LAYOUT=UNCOMPACT^} option.
16891 @subsection Name Casing
16894 @command{gnatpp} always converts the usage occurrence of a (simple) name to
16895 the same casing as the corresponding defining identifier.
16897 You control the casing for defining occurrences via the
16898 @option{^-n^/NAME_CASING^} switch.
16900 With @option{-nD} (``as declared'', which is the default),
16903 With @option{/NAME_CASING=AS_DECLARED}, which is the default,
16905 defining occurrences appear exactly as in the source file
16906 where they are declared.
16907 The other ^values for this switch^options for this qualifier^ ---
16908 @option{^-nU^UPPER_CASE^},
16909 @option{^-nL^LOWER_CASE^},
16910 @option{^-nM^MIXED_CASE^} ---
16912 ^upper, lower, or mixed case, respectively^the corresponding casing^.
16913 If @command{gnatpp} changes the casing of a defining
16914 occurrence, it analogously changes the casing of all the
16915 usage occurrences of this name.
16917 If the defining occurrence of a name is not in the source compilation unit
16918 currently being processed by @command{gnatpp}, the casing of each reference to
16919 this name is changed according to the value of the @option{^-n^/NAME_CASING^}
16920 switch (subject to the dictionary file mechanism described below).
16921 Thus @command{gnatpp} acts as though the @option{^-n^/NAME_CASING^} switch
16923 casing for the defining occurrence of the name.
16925 Some names may need to be spelled with casing conventions that are not
16926 covered by the upper-, lower-, and mixed-case transformations.
16927 You can arrange correct casing by placing such names in a
16928 @emph{dictionary file},
16929 and then supplying a @option{^-D^/DICTIONARY^} switch.
16930 The casing of names from dictionary files overrides
16931 any @option{^-n^/NAME_CASING^} switch.
16933 To handle the casing of Ada predefined names and the names from GNAT libraries,
16934 @command{gnatpp} assumes a default dictionary file.
16935 The name of each predefined entity is spelled with the same casing as is used
16936 for the entity in the @cite{Ada Reference Manual}.
16937 The name of each entity in the GNAT libraries is spelled with the same casing
16938 as is used in the declaration of that entity.
16940 The @w{@option{^-D-^/SPECIFIC_CASING^}} switch suppresses the use of the
16941 default dictionary file.
16942 Instead, the casing for predefined and GNAT-defined names will be established
16943 by the @option{^-n^/NAME_CASING^} switch or explicit dictionary files.
16944 For example, by default the names @code{Ada.Text_IO} and @code{GNAT.OS_Lib}
16945 will appear as just shown,
16946 even in the presence of a @option{^-nU^/NAME_CASING=UPPER_CASE^} switch.
16947 To ensure that even such names are rendered in uppercase,
16948 additionally supply the @w{@option{^-D-^/SPECIFIC_CASING^}} switch
16949 (or else, less conveniently, place these names in upper case in a dictionary
16952 A dictionary file is
16953 a plain text file; each line in this file can be either a blank line
16954 (containing only space characters and ASCII.HT characters), an Ada comment
16955 line, or the specification of exactly one @emph{casing schema}.
16957 A casing schema is a string that has the following syntax:
16961 @var{casing_schema} ::= @var{identifier} | *@var{simple_identifier}*
16963 @var{simple_identifier} ::= @var{letter}@{@var{letter_or_digit}@}
16968 (See @cite{Ada Reference Manual}, Section 2.3) for the definition of the
16969 @var{identifier} lexical element and the @var{letter_or_digit} category.)
16971 The casing schema string can be followed by white space and/or an Ada-style
16972 comment; any amount of white space is allowed before the string.
16974 If a dictionary file is passed as
16976 the value of a @option{-D@var{file}} switch
16979 an option to the @option{/DICTIONARY} qualifier
16982 simple name and every identifier, @command{gnatpp} checks if the dictionary
16983 defines the casing for the name or for some of its parts (the term ``subword''
16984 is used below to denote the part of a name which is delimited by ``_'' or by
16985 the beginning or end of the word and which does not contain any ``_'' inside):
16989 if the whole name is in the dictionary, @command{gnatpp} uses for this name
16990 the casing defined by the dictionary; no subwords are checked for this word
16993 for every subword @command{gnatpp} checks if the dictionary contains the
16994 corresponding string of the form @code{*@var{simple_identifier}*},
16995 and if it does, the casing of this @var{simple_identifier} is used
16999 if the whole name does not contain any ``_'' inside, and if for this name
17000 the dictionary contains two entries - one of the form @var{identifier},
17001 and another - of the form *@var{simple_identifier}*, then the first one
17002 is applied to define the casing of this name
17005 if more than one dictionary file is passed as @command{gnatpp} switches, each
17006 dictionary adds new casing exceptions and overrides all the existing casing
17007 exceptions set by the previous dictionaries
17010 when @command{gnatpp} checks if the word or subword is in the dictionary,
17011 this check is not case sensitive
17015 For example, suppose we have the following source to reformat:
17017 @smallexample @c ada
17020 name1 : integer := 1;
17021 name4_name3_name2 : integer := 2;
17022 name2_name3_name4 : Boolean;
17025 name2_name3_name4 := name4_name3_name2 > name1;
17031 And suppose we have two dictionaries:
17048 If @command{gnatpp} is called with the following switches:
17052 @command{gnatpp -nM -D dict1 -D dict2 test.adb}
17055 @command{gnatpp test.adb /NAME_CASING=MIXED_CASE /DICTIONARY=(dict1, dict2)}
17060 then we will get the following name casing in the @command{gnatpp} output:
17062 @smallexample @c ada
17065 NAME1 : Integer := 1;
17066 Name4_NAME3_Name2 : Integer := 2;
17067 Name2_NAME3_Name4 : Boolean;
17070 Name2_NAME3_Name4 := Name4_NAME3_Name2 > NAME1;
17075 @c *********************************
17076 @node The GNAT Metric Tool gnatmetric
17077 @chapter The GNAT Metric Tool @command{gnatmetric}
17079 @cindex Metric tool
17082 ^The @command{gnatmetric} tool^@command{GNAT METRIC}^ is an ASIS-based utility
17083 for computing various program metrics.
17084 It takes an Ada source file as input and generates a file containing the
17085 metrics data as output. Various switches control which
17086 metrics are computed and output.
17088 @command{gnatmetric} generates and uses the ASIS
17089 tree for the input source and thus requires the input to be syntactically and
17090 semantically legal.
17091 If this condition is not met, @command{gnatmetric} will generate
17092 an error message; no metric information for this file will be
17093 computed and reported.
17095 If the compilation unit contained in the input source depends semantically
17096 upon units in files located outside the current directory, you have to provide
17097 the source search path when invoking @command{gnatmetric}.
17098 If it depends semantically upon units that are contained
17099 in files with names that do not follow the GNAT file naming rules, you have to
17100 provide the configuration file describing the corresponding naming scheme (see
17101 the description of the @command{gnatmetric} switches below.)
17102 Alternatively, you may use a project file and invoke @command{gnatmetric}
17103 through the @command{gnat} driver.
17105 The @command{gnatmetric} command has the form
17108 $ gnatmetric @ovar{switches} @{@var{filename}@} @r{[}-cargs @var{gcc_switches}@r{]}
17115 @var{switches} specify the metrics to compute and define the destination for
17119 Each @var{filename} is the name (including the extension) of a source
17120 file to process. ``Wildcards'' are allowed, and
17121 the file name may contain path information.
17122 If no @var{filename} is supplied, then the @var{switches} list must contain
17124 @option{-files} switch (@pxref{Other gnatmetric Switches}).
17125 Including both a @option{-files} switch and one or more
17126 @var{filename} arguments is permitted.
17129 @samp{-cargs @var{gcc_switches}} is a list of switches for
17130 @command{gcc}. They will be passed on to all compiler invocations made by
17131 @command{gnatmetric} to generate the ASIS trees. Here you can provide
17132 @option{^-I^/INCLUDE_DIRS=^} switches to form the source search path,
17133 and use the @option{-gnatec} switch to set the configuration file.
17137 * Switches for gnatmetric::
17140 @node Switches for gnatmetric
17141 @section Switches for @command{gnatmetric}
17144 The following subsections describe the various switches accepted by
17145 @command{gnatmetric}, organized by category.
17148 * Output Files Control::
17149 * Disable Metrics For Local Units::
17150 * Specifying a set of metrics to compute::
17151 * Other gnatmetric Switches::
17152 * Generate project-wide metrics::
17155 @node Output Files Control
17156 @subsection Output File Control
17157 @cindex Output file control in @command{gnatmetric}
17160 @command{gnatmetric} has two output formats. It can generate a
17161 textual (human-readable) form, and also XML. By default only textual
17162 output is generated.
17164 When generating the output in textual form, @command{gnatmetric} creates
17165 for each Ada source file a corresponding text file
17166 containing the computed metrics, except for the case when the set of metrics
17167 specified by gnatmetric parameters consists only of metrics that are computed
17168 for the whole set of analyzed sources, but not for each Ada source.
17169 By default, this file is placed in the same directory as where the source
17170 file is located, and its name is obtained
17171 by appending the ^@file{.metrix}^@file{$METRIX}^ suffix to the name of the
17174 All the output information generated in XML format is placed in a single
17175 file. By default this file is placed in the current directory and has the
17176 name ^@file{metrix.xml}^@file{METRIX$XML}^.
17178 Some of the computed metrics are summed over the units passed to
17179 @command{gnatmetric}; for example, the total number of lines of code.
17180 By default this information is sent to @file{stdout}, but a file
17181 can be specified with the @option{-og} switch.
17183 The following switches control the @command{gnatmetric} output:
17186 @cindex @option{^-x^/XML^} (@command{gnatmetric})
17188 Generate the XML output
17190 @cindex @option{^-xs^/XSD^} (@command{gnatmetric})
17192 Generate the XML output and the XML schema file that describes the structure
17193 of the XML metric report, this schema is assigned to the XML file. The schema
17194 file has the same name as the XML output file with @file{.xml} suffix replaced
17197 @cindex @option{^-nt^/NO_TEXT^} (@command{gnatmetric})
17198 @item ^-nt^/NO_TEXT^
17199 Do not generate the output in text form (implies @option{^-x^/XML^})
17201 @cindex @option{^-d^/DIRECTORY^} (@command{gnatmetric})
17202 @item ^-d @var{output_dir}^/DIRECTORY=@var{output_dir}^
17203 Put textual files with detailed metrics into @var{output_dir}
17205 @cindex @option{^-o^/SUFFIX_DETAILS^} (@command{gnatmetric})
17206 @item ^-o @var{file_suffix}^/SUFFIX_DETAILS=@var{file_suffix}^
17207 Use @var{file_suffix}, instead of ^@file{.metrix}^@file{$METRIX}^
17208 in the name of the output file.
17210 @cindex @option{^-og^/GLOBAL_OUTPUT^} (@command{gnatmetric})
17211 @item ^-og @var{file_name}^/GLOBAL_OUTPUT=@var{file_name}^
17212 Put global metrics into @var{file_name}
17214 @cindex @option{^-ox^/XML_OUTPUT^} (@command{gnatmetric})
17215 @item ^-ox @var{file_name}^/XML_OUTPUT=@var{file_name}^
17216 Put the XML output into @var{file_name} (also implies @option{^-x^/XML^})
17218 @cindex @option{^-sfn^/SHORT_SOURCE_FILE_NAME^} (@command{gnatmetric})
17219 @item ^-sfn^/SHORT_SOURCE_FILE_NAME^
17220 Use ``short'' source file names in the output. (The @command{gnatmetric}
17221 output includes the name(s) of the Ada source file(s) from which the metrics
17222 are computed. By default each name includes the absolute path. The
17223 @option{^-sfn^/SHORT_SOURCE_FILE_NAME^} switch causes @command{gnatmetric}
17224 to exclude all directory information from the file names that are output.)
17228 @node Disable Metrics For Local Units
17229 @subsection Disable Metrics For Local Units
17230 @cindex Disable Metrics For Local Units in @command{gnatmetric}
17233 @command{gnatmetric} relies on the GNAT compilation model @minus{}
17235 unit per one source file. It computes line metrics for the whole source
17236 file, and it also computes syntax
17237 and complexity metrics for the file's outermost unit.
17239 By default, @command{gnatmetric} will also compute all metrics for certain
17240 kinds of locally declared program units:
17244 subprogram (and generic subprogram) bodies;
17247 package (and generic package) specs and bodies;
17250 task object and type specifications and bodies;
17253 protected object and type specifications and bodies.
17257 These kinds of entities will be referred to as
17258 @emph{eligible local program units}, or simply @emph{eligible local units},
17259 @cindex Eligible local unit (for @command{gnatmetric})
17260 in the discussion below.
17262 Note that a subprogram declaration, generic instantiation,
17263 or renaming declaration only receives metrics
17264 computation when it appear as the outermost entity
17267 Suppression of metrics computation for eligible local units can be
17268 obtained via the following switch:
17271 @cindex @option{^-n@var{x}^/SUPPRESS^} (@command{gnatmetric})
17272 @item ^-nolocal^/SUPPRESS=LOCAL_DETAILS^
17273 Do not compute detailed metrics for eligible local program units
17277 @node Specifying a set of metrics to compute
17278 @subsection Specifying a set of metrics to compute
17281 By default all the metrics are computed and reported. The switches
17282 described in this subsection allow you to control, on an individual
17283 basis, whether metrics are computed and
17284 reported. If at least one positive metric
17285 switch is specified (that is, a switch that defines that a given
17286 metric or set of metrics is to be computed), then only
17287 explicitly specified metrics are reported.
17290 * Line Metrics Control::
17291 * Syntax Metrics Control::
17292 * Complexity Metrics Control::
17293 * Object-Oriented Metrics Control::
17296 @node Line Metrics Control
17297 @subsubsection Line Metrics Control
17298 @cindex Line metrics control in @command{gnatmetric}
17301 For any (legal) source file, and for each of its
17302 eligible local program units, @command{gnatmetric} computes the following
17307 the total number of lines;
17310 the total number of code lines (i.e., non-blank lines that are not comments)
17313 the number of comment lines
17316 the number of code lines containing end-of-line comments;
17319 the comment percentage: the ratio between the number of lines that contain
17320 comments and the number of all non-blank lines, expressed as a percentage;
17323 the number of empty lines and lines containing only space characters and/or
17324 format effectors (blank lines)
17327 the average number of code lines in subprogram bodies, task bodies, entry
17328 bodies and statement sequences in package bodies (this metric is only computed
17329 across the whole set of the analyzed units)
17334 @command{gnatmetric} sums the values of the line metrics for all the
17335 files being processed and then generates the cumulative results. The tool
17336 also computes for all the files being processed the average number of code
17339 You can use the following switches to select the specific line metrics
17340 to be computed and reported.
17343 @cindex @option{^--lines@var{x}^/LINE_COUNT_METRICS^} (@command{gnatmetric})
17346 @cindex @option{--no-lines@var{x}}
17349 @item ^--lines-all^/LINE_COUNT_METRICS=ALL^
17350 Report all the line metrics
17352 @item ^--no-lines-all^/LINE_COUNT_METRICS=NONE^
17353 Do not report any of line metrics
17355 @item ^--lines^/LINE_COUNT_METRICS=ALL_LINES^
17356 Report the number of all lines
17358 @item ^--no-lines^/LINE_COUNT_METRICS=NOALL_LINES^
17359 Do not report the number of all lines
17361 @item ^--lines-code^/LINE_COUNT_METRICS=CODE_LINES^
17362 Report the number of code lines
17364 @item ^--no-lines-code^/LINE_COUNT_METRICS=NOCODE_LINES^
17365 Do not report the number of code lines
17367 @item ^--lines-comment^/LINE_COUNT_METRICS=COMMENT_LINES^
17368 Report the number of comment lines
17370 @item ^--no-lines-comment^/LINE_COUNT_METRICS=NOCOMMENT_LINES^
17371 Do not report the number of comment lines
17373 @item ^--lines-eol-comment^/LINE_COUNT_METRICS=CODE_COMMENT_LINES^
17374 Report the number of code lines containing
17375 end-of-line comments
17377 @item ^--no-lines-eol-comment^/LINE_COUNT_METRICS=NOCODE_COMMENT_LINES^
17378 Do not report the number of code lines containing
17379 end-of-line comments
17381 @item ^--lines-ratio^/LINE_COUNT_METRICS=COMMENT_PERCENTAGE^
17382 Report the comment percentage in the program text
17384 @item ^--no-lines-ratio^/LINE_COUNT_METRICS=NOCOMMENT_PERCENTAGE^
17385 Do not report the comment percentage in the program text
17387 @item ^--lines-blank^/LINE_COUNT_METRICS=BLANK_LINES^
17388 Report the number of blank lines
17390 @item ^--no-lines-blank^/LINE_COUNT_METRICS=NOBLANK_LINES^
17391 Do not report the number of blank lines
17393 @item ^--lines-average^/LINE_COUNT_METRICS=AVERAGE_BODY_LINES^
17394 Report the average number of code lines in subprogram bodies, task bodies,
17395 entry bodies and statement sequences in package bodies. The metric is computed
17396 and reported for the whole set of processed Ada sources only.
17398 @item ^--no-lines-average^/LINE_COUNT_METRICS=NOAVERAGE_BODY_LINES^
17399 Do not report the average number of code lines in subprogram bodies,
17400 task bodies, entry bodies and statement sequences in package bodies.
17404 @node Syntax Metrics Control
17405 @subsubsection Syntax Metrics Control
17406 @cindex Syntax metrics control in @command{gnatmetric}
17409 @command{gnatmetric} computes various syntactic metrics for the
17410 outermost unit and for each eligible local unit:
17413 @item LSLOC (``Logical Source Lines Of Code'')
17414 The total number of declarations and the total number of statements
17416 @item Maximal static nesting level of inner program units
17418 @cite{Ada Reference Manual}, 10.1(1), ``A program unit is either a
17419 package, a task unit, a protected unit, a
17420 protected entry, a generic unit, or an explicitly declared subprogram other
17421 than an enumeration literal.''
17423 @item Maximal nesting level of composite syntactic constructs
17424 This corresponds to the notion of the
17425 maximum nesting level in the GNAT built-in style checks
17426 (@pxref{Style Checking})
17430 For the outermost unit in the file, @command{gnatmetric} additionally computes
17431 the following metrics:
17434 @item Public subprograms
17435 This metric is computed for package specs. It is the
17436 number of subprograms and generic subprograms declared in the visible
17437 part (including the visible part of nested packages, protected objects, and
17440 @item All subprograms
17441 This metric is computed for bodies and subunits. The
17442 metric is equal to a total number of subprogram bodies in the compilation
17444 Neither generic instantiations nor renamings-as-a-body nor body stubs
17445 are counted. Any subprogram body is counted, independently of its nesting
17446 level and enclosing constructs. Generic bodies and bodies of protected
17447 subprograms are counted in the same way as ``usual'' subprogram bodies.
17450 This metric is computed for package specs and
17451 generic package declarations. It is the total number of types
17452 that can be referenced from outside this compilation unit, plus the
17453 number of types from all the visible parts of all the visible generic
17454 packages. Generic formal types are not counted. Only types, not subtypes,
17458 Along with the total number of public types, the following
17459 types are counted and reported separately:
17466 Root tagged types (abstract, non-abstract, private, non-private). Type
17467 extensions are @emph{not} counted
17470 Private types (including private extensions)
17481 This metric is computed for any compilation unit. It is equal to the total
17482 number of the declarations of different types given in the compilation unit.
17483 The private and the corresponding full type declaration are counted as one
17484 type declaration. Incomplete type declarations and generic formal types
17486 No distinction is made among different kinds of types (abstract,
17487 private etc.); the total number of types is computed and reported.
17492 By default, all the syntax metrics are computed and reported. You can use the
17493 following switches to select specific syntax metrics.
17497 @cindex @option{^--syntax@var{x}^/SYNTAX_METRICS^} (@command{gnatmetric})
17500 @cindex @option{--no-syntax@var{x}} (@command{gnatmetric})
17503 @item ^--syntax-all^/SYNTAX_METRICS=ALL^
17504 Report all the syntax metrics
17506 @item ^--no-syntax-all^/SYNTAX_METRICS=NONE^
17507 Do not report any of syntax metrics
17509 @item ^--declarations^/SYNTAX_METRICS=DECLARATIONS^
17510 Report the total number of declarations
17512 @item ^--no-declarations^/SYNTAX_METRICS=NODECLARATIONS^
17513 Do not report the total number of declarations
17515 @item ^--statements^/SYNTAX_METRICS=STATEMENTS^
17516 Report the total number of statements
17518 @item ^--no-statements^/SYNTAX_METRICS=NOSTATEMENTS^
17519 Do not report the total number of statements
17521 @item ^--public-subprograms^/SYNTAX_METRICS=PUBLIC_SUBPROGRAMS^
17522 Report the number of public subprograms in a compilation unit
17524 @item ^--no-public-subprograms^/SYNTAX_METRICS=NOPUBLIC_SUBPROGRAMS^
17525 Do not report the number of public subprograms in a compilation unit
17527 @item ^--all-subprograms^/SYNTAX_METRICS=ALL_SUBPROGRAMS^
17528 Report the number of all the subprograms in a compilation unit
17530 @item ^--no-all-subprograms^/SYNTAX_METRICS=NOALL_SUBPROGRAMS^
17531 Do not report the number of all the subprograms in a compilation unit
17533 @item ^--public-types^/SYNTAX_METRICS=PUBLIC_TYPES^
17534 Report the number of public types in a compilation unit
17536 @item ^--no-public-types^/SYNTAX_METRICS=NOPUBLIC_TYPES^
17537 Do not report the number of public types in a compilation unit
17539 @item ^--all-types^/SYNTAX_METRICS=ALL_TYPES^
17540 Report the number of all the types in a compilation unit
17542 @item ^--no-all-types^/SYNTAX_METRICS=NOALL_TYPES^
17543 Do not report the number of all the types in a compilation unit
17545 @item ^--unit-nesting^/SYNTAX_METRICS=UNIT_NESTING^
17546 Report the maximal program unit nesting level
17548 @item ^--no-unit-nesting^/SYNTAX_METRICS=UNIT_NESTING_OFF^
17549 Do not report the maximal program unit nesting level
17551 @item ^--construct-nesting^/SYNTAX_METRICS=CONSTRUCT_NESTING^
17552 Report the maximal construct nesting level
17554 @item ^--no-construct-nesting^/SYNTAX_METRICS=NOCONSTRUCT_NESTING^
17555 Do not report the maximal construct nesting level
17559 @node Complexity Metrics Control
17560 @subsubsection Complexity Metrics Control
17561 @cindex Complexity metrics control in @command{gnatmetric}
17564 For a program unit that is an executable body (a subprogram body (including
17565 generic bodies), task body, entry body or a package body containing
17566 its own statement sequence) @command{gnatmetric} computes the following
17567 complexity metrics:
17571 McCabe cyclomatic complexity;
17574 McCabe essential complexity;
17577 maximal loop nesting level
17582 The McCabe complexity metrics are defined
17583 in @url{http://www.mccabe.com/pdf/nist235r.pdf}
17585 According to McCabe, both control statements and short-circuit control forms
17586 should be taken into account when computing cyclomatic complexity. For each
17587 body, we compute three metric values:
17591 the complexity introduced by control
17592 statements only, without taking into account short-circuit forms,
17595 the complexity introduced by short-circuit control forms only, and
17599 cyclomatic complexity, which is the sum of these two values.
17603 When computing cyclomatic and essential complexity, @command{gnatmetric} skips
17604 the code in the exception handlers and in all the nested program units.
17606 By default, all the complexity metrics are computed and reported.
17607 For more fine-grained control you can use
17608 the following switches:
17611 @cindex @option{^-complexity@var{x}^/COMPLEXITY_METRICS^} (@command{gnatmetric})
17614 @cindex @option{--no-complexity@var{x}}
17617 @item ^--complexity-all^/COMPLEXITY_METRICS=ALL^
17618 Report all the complexity metrics
17620 @item ^--no-complexity-all^/COMPLEXITY_METRICS=NONE^
17621 Do not report any of complexity metrics
17623 @item ^--complexity-cyclomatic^/COMPLEXITY_METRICS=CYCLOMATIC^
17624 Report the McCabe Cyclomatic Complexity
17626 @item ^--no-complexity-cyclomatic^/COMPLEXITY_METRICS=NOCYCLOMATIC^
17627 Do not report the McCabe Cyclomatic Complexity
17629 @item ^--complexity-essential^/COMPLEXITY_METRICS=ESSENTIAL^
17630 Report the Essential Complexity
17632 @item ^--no-complexity-essential^/COMPLEXITY_METRICS=NOESSENTIAL^
17633 Do not report the Essential Complexity
17635 @item ^--loop-nesting^/COMPLEXITY_METRICS=LOOP_NESTING_ON^
17636 Report maximal loop nesting level
17638 @item ^--no-loop-nesting^/COMPLEXITY_METRICS=NOLOOP_NESTING^
17639 Do not report maximal loop nesting level
17641 @item ^--complexity-average^/COMPLEXITY_METRICS=AVERAGE_COMPLEXITY^
17642 Report the average McCabe Cyclomatic Complexity for all the subprogram bodies,
17643 task bodies, entry bodies and statement sequences in package bodies.
17644 The metric is computed and reported for whole set of processed Ada sources
17647 @item ^--no-complexity-average^/COMPLEXITY_METRICS=NOAVERAGE_COMPLEXITY^
17648 Do not report the average McCabe Cyclomatic Complexity for all the subprogram
17649 bodies, task bodies, entry bodies and statement sequences in package bodies
17651 @cindex @option{^-ne^/NO_EXITS_AS_GOTOS^} (@command{gnatmetric})
17652 @item ^-ne^/NO_EXITS_AS_GOTOS^
17653 Do not consider @code{exit} statements as @code{goto}s when
17654 computing Essential Complexity
17656 @item ^--extra-exit-points^/EXTRA_EXIT_POINTS^
17657 Report the extra exit points for subprogram bodies. As an exit point, this
17658 metric counts @code{return} statements and raise statements in case when the
17659 raised exception is not handled in the same body. In case of a function this
17660 metric subtracts 1 from the number of exit points, because a function body
17661 must contain at least one @code{return} statement.
17663 @item ^--no-extra-exit-points^/NOEXTRA_EXIT_POINTS^
17664 Do not report the extra exit points for subprogram bodies
17668 @node Object-Oriented Metrics Control
17669 @subsubsection Object-Oriented Metrics Control
17670 @cindex Object-Oriented metrics control in @command{gnatmetric}
17673 @cindex Coupling metrics (in in @command{gnatmetric})
17674 Coupling metrics are object-oriented metrics that measure the
17675 dependencies between a given class (or a group of classes) and the
17676 ``external world'' (that is, the other classes in the program). In this
17677 subsection the term ``class'' is used in its
17678 traditional object-oriented programming sense
17679 (an instantiable module that contains data and/or method members).
17680 A @emph{category} (of classes)
17681 is a group of closely related classes that are reused and/or
17684 A class @code{K}'s @emph{efferent coupling} is the number of classes
17685 that @code{K} depends upon.
17686 A category's efferent coupling is the number of classes outside the
17687 category that the classes inside the category depend upon.
17689 A class @code{K}'s @emph{afferent coupling} is the number of classes
17690 that depend upon @code{K}.
17691 A category's afferent coupling is the number of classes outside the
17692 category that depend on classes belonging to the category.
17694 Ada's implementation of the object-oriented paradigm does not use the
17695 traditional class notion, so the definition of the coupling
17696 metrics for Ada maps the class and class category notions
17697 onto Ada constructs.
17699 For the coupling metrics, several kinds of modules -- a library package,
17700 a library generic package, and a library generic package instantiation --
17701 that define a tagged type or an interface type are
17702 considered to be a class. A category consists of a library package (or
17703 a library generic package) that defines a tagged or an interface type,
17704 together with all its descendant (generic) packages that define tagged
17705 or interface types. For any package counted as a class,
17706 its body and subunits (if any) are considered
17707 together with its spec when counting the dependencies, and coupling
17708 metrics are reported for spec units only. For dependencies
17709 between classes, the Ada semantic dependencies are considered.
17710 For coupling metrics, only dependencies on units that are considered as
17711 classes, are considered.
17713 When computing coupling metrics, @command{gnatmetric} counts only
17714 dependencies between units that are arguments of the gnatmetric call.
17715 Coupling metrics are program-wide (or project-wide) metrics, so to
17716 get a valid result, you should call @command{gnatmetric} for
17717 the whole set of sources that make up your program. It can be done
17718 by calling @command{gnatmetric} from the GNAT driver with @option{-U}
17719 option (see See @ref{The GNAT Driver and Project Files} for details.
17721 By default, all the coupling metrics are disabled. You can use the following
17722 switches to specify the coupling metrics to be computed and reported:
17727 @cindex @option{--package@var{x}} (@command{gnatmetric})
17728 @cindex @option{--no-package@var{x}} (@command{gnatmetric})
17729 @cindex @option{--category@var{x}} (@command{gnatmetric})
17730 @cindex @option{--no-category@var{x}} (@command{gnatmetric})
17734 @cindex @option{/COUPLING_METRICS} (@command{gnatmetric})
17737 @item ^--coupling-all^/COUPLING_METRICS=ALL^
17738 Report all the coupling metrics
17740 @item ^--no-coupling-all^/COUPLING_METRICS=NONE^
17741 Do not report any of metrics
17743 @item ^--package-efferent-coupling^/COUPLING_METRICS=PACKAGE_EFFERENT^
17744 Report package efferent coupling
17746 @item ^--no-package-efferent-coupling^/COUPLING_METRICS=NOPACKAGE_EFFERENT^
17747 Do not report package efferent coupling
17749 @item ^--package-afferent-coupling^/COUPLING_METRICS=PACKAGE_AFFERENT^
17750 Report package afferent coupling
17752 @item ^--no-package-afferent-coupling^/COUPLING_METRICS=NOPACKAGE_AFFERENT^
17753 Do not report package afferent coupling
17755 @item ^--category-efferent-coupling^/COUPLING_METRICS=CATEGORY_EFFERENT^
17756 Report category efferent coupling
17758 @item ^--no-category-efferent-coupling^/COUPLING_METRICS=NOCATEGORY_EFFERENT^
17759 Do not report category efferent coupling
17761 @item ^--category-afferent-coupling^/COUPLING_METRICS=CATEGORY_AFFERENT^
17762 Report category afferent coupling
17764 @item ^--no-category-afferent-coupling^/COUPLING_METRICS=NOCATEGORY_AFFERENT^
17765 Do not report category afferent coupling
17769 @node Other gnatmetric Switches
17770 @subsection Other @code{gnatmetric} Switches
17773 Additional @command{gnatmetric} switches are as follows:
17776 @item ^-files @var{filename}^/FILES=@var{filename}^
17777 @cindex @option{^-files^/FILES^} (@code{gnatmetric})
17778 Take the argument source files from the specified file. This file should be an
17779 ordinary text file containing file names separated by spaces or
17780 line breaks. You can use this switch more then once in the same call to
17781 @command{gnatmetric}. You also can combine this switch with
17782 an explicit list of files.
17784 @item ^-v^/VERBOSE^
17785 @cindex @option{^-v^/VERBOSE^} (@code{gnatmetric})
17787 @command{gnatmetric} generates version information and then
17788 a trace of sources being processed.
17790 @item ^-dv^/DEBUG_OUTPUT^
17791 @cindex @option{^-dv^/DEBUG_OUTPUT^} (@code{gnatmetric})
17793 @command{gnatmetric} generates various messages useful to understand what
17794 happens during the metrics computation
17797 @cindex @option{^-q^/QUIET^} (@code{gnatmetric})
17801 @node Generate project-wide metrics
17802 @subsection Generate project-wide metrics
17804 In order to compute metrics on all units of a given project, you can use
17805 the @command{gnat} driver along with the @option{-P} option:
17811 If the project @code{proj} depends upon other projects, you can compute
17812 the metrics on the project closure using the @option{-U} option:
17814 gnat metric -Pproj -U
17818 Finally, if not all the units are relevant to a particular main
17819 program in the project closure, you can generate metrics for the set
17820 of units needed to create a given main program (unit closure) using
17821 the @option{-U} option followed by the name of the main unit:
17823 gnat metric -Pproj -U main
17827 @c ***********************************
17828 @node File Name Krunching Using gnatkr
17829 @chapter File Name Krunching Using @code{gnatkr}
17833 This chapter discusses the method used by the compiler to shorten
17834 the default file names chosen for Ada units so that they do not
17835 exceed the maximum length permitted. It also describes the
17836 @code{gnatkr} utility that can be used to determine the result of
17837 applying this shortening.
17841 * Krunching Method::
17842 * Examples of gnatkr Usage::
17846 @section About @code{gnatkr}
17849 The default file naming rule in GNAT
17850 is that the file name must be derived from
17851 the unit name. The exact default rule is as follows:
17854 Take the unit name and replace all dots by hyphens.
17856 If such a replacement occurs in the
17857 second character position of a name, and the first character is
17858 ^@samp{a}, @samp{g}, @samp{s}, or @samp{i}, ^@samp{A}, @samp{G}, @samp{S}, or @samp{I},^
17859 then replace the dot by the character
17860 ^@samp{~} (tilde)^@samp{$} (dollar sign)^
17861 instead of a minus.
17863 The reason for this exception is to avoid clashes
17864 with the standard names for children of System, Ada, Interfaces,
17865 and GNAT, which use the prefixes
17866 ^@samp{s-}, @samp{a-}, @samp{i-}, and @samp{g-},^@samp{S-}, @samp{A-}, @samp{I-}, and @samp{G-},^
17869 The @option{^-gnatk^/FILE_NAME_MAX_LENGTH=^@var{nn}}
17870 switch of the compiler activates a ``krunching''
17871 circuit that limits file names to nn characters (where nn is a decimal
17872 integer). For example, using OpenVMS,
17873 where the maximum file name length is
17874 39, the value of nn is usually set to 39, but if you want to generate
17875 a set of files that would be usable if ported to a system with some
17876 different maximum file length, then a different value can be specified.
17877 The default value of 39 for OpenVMS need not be specified.
17879 The @code{gnatkr} utility can be used to determine the krunched name for
17880 a given file, when krunched to a specified maximum length.
17883 @section Using @code{gnatkr}
17886 The @code{gnatkr} command has the form
17890 $ gnatkr @var{name} @ovar{length}
17896 $ gnatkr @var{name} /COUNT=nn
17901 @var{name} is the uncrunched file name, derived from the name of the unit
17902 in the standard manner described in the previous section (i.e., in particular
17903 all dots are replaced by hyphens). The file name may or may not have an
17904 extension (defined as a suffix of the form period followed by arbitrary
17905 characters other than period). If an extension is present then it will
17906 be preserved in the output. For example, when krunching @file{hellofile.ads}
17907 to eight characters, the result will be hellofil.ads.
17909 Note: for compatibility with previous versions of @code{gnatkr} dots may
17910 appear in the name instead of hyphens, but the last dot will always be
17911 taken as the start of an extension. So if @code{gnatkr} is given an argument
17912 such as @file{Hello.World.adb} it will be treated exactly as if the first
17913 period had been a hyphen, and for example krunching to eight characters
17914 gives the result @file{hellworl.adb}.
17916 Note that the result is always all lower case (except on OpenVMS where it is
17917 all upper case). Characters of the other case are folded as required.
17919 @var{length} represents the length of the krunched name. The default
17920 when no argument is given is ^8^39^ characters. A length of zero stands for
17921 unlimited, in other words do not chop except for system files where the
17922 implied crunching length is always eight characters.
17925 The output is the krunched name. The output has an extension only if the
17926 original argument was a file name with an extension.
17928 @node Krunching Method
17929 @section Krunching Method
17932 The initial file name is determined by the name of the unit that the file
17933 contains. The name is formed by taking the full expanded name of the
17934 unit and replacing the separating dots with hyphens and
17935 using ^lowercase^uppercase^
17936 for all letters, except that a hyphen in the second character position is
17937 replaced by a ^tilde^dollar sign^ if the first character is
17938 ^@samp{a}, @samp{i}, @samp{g}, or @samp{s}^@samp{A}, @samp{I}, @samp{G}, or @samp{S}^.
17939 The extension is @code{.ads} for a
17940 spec and @code{.adb} for a body.
17941 Krunching does not affect the extension, but the file name is shortened to
17942 the specified length by following these rules:
17946 The name is divided into segments separated by hyphens, tildes or
17947 underscores and all hyphens, tildes, and underscores are
17948 eliminated. If this leaves the name short enough, we are done.
17951 If the name is too long, the longest segment is located (left-most
17952 if there are two of equal length), and shortened by dropping
17953 its last character. This is repeated until the name is short enough.
17955 As an example, consider the krunching of @*@file{our-strings-wide_fixed.adb}
17956 to fit the name into 8 characters as required by some operating systems.
17959 our-strings-wide_fixed 22
17960 our strings wide fixed 19
17961 our string wide fixed 18
17962 our strin wide fixed 17
17963 our stri wide fixed 16
17964 our stri wide fixe 15
17965 our str wide fixe 14
17966 our str wid fixe 13
17972 Final file name: oustwifi.adb
17976 The file names for all predefined units are always krunched to eight
17977 characters. The krunching of these predefined units uses the following
17978 special prefix replacements:
17982 replaced by @file{^a^A^-}
17985 replaced by @file{^g^G^-}
17988 replaced by @file{^i^I^-}
17991 replaced by @file{^s^S^-}
17994 These system files have a hyphen in the second character position. That
17995 is why normal user files replace such a character with a
17996 ^tilde^dollar sign^, to
17997 avoid confusion with system file names.
17999 As an example of this special rule, consider
18000 @*@file{ada-strings-wide_fixed.adb}, which gets krunched as follows:
18003 ada-strings-wide_fixed 22
18004 a- strings wide fixed 18
18005 a- string wide fixed 17
18006 a- strin wide fixed 16
18007 a- stri wide fixed 15
18008 a- stri wide fixe 14
18009 a- str wide fixe 13
18015 Final file name: a-stwifi.adb
18019 Of course no file shortening algorithm can guarantee uniqueness over all
18020 possible unit names, and if file name krunching is used then it is your
18021 responsibility to ensure that no name clashes occur. The utility
18022 program @code{gnatkr} is supplied for conveniently determining the
18023 krunched name of a file.
18025 @node Examples of gnatkr Usage
18026 @section Examples of @code{gnatkr} Usage
18033 $ gnatkr very_long_unit_name.ads --> velounna.ads
18034 $ gnatkr grandparent-parent-child.ads --> grparchi.ads
18035 $ gnatkr Grandparent.Parent.Child.ads --> grparchi.ads
18036 $ gnatkr grandparent-parent-child --> grparchi
18038 $ gnatkr very_long_unit_name.ads/count=6 --> vlunna.ads
18039 $ gnatkr very_long_unit_name.ads/count=0 --> very_long_unit_name.ads
18042 @node Preprocessing Using gnatprep
18043 @chapter Preprocessing Using @code{gnatprep}
18047 This chapter discusses how to use GNAT's @code{gnatprep} utility for simple
18049 Although designed for use with GNAT, @code{gnatprep} does not depend on any
18050 special GNAT features.
18051 For further discussion of conditional compilation in general, see
18052 @ref{Conditional Compilation}.
18055 * Preprocessing Symbols::
18057 * Switches for gnatprep::
18058 * Form of Definitions File::
18059 * Form of Input Text for gnatprep::
18062 @node Preprocessing Symbols
18063 @section Preprocessing Symbols
18066 Preprocessing symbols are defined in definition files and referred to in
18067 sources to be preprocessed. A Preprocessing symbol is an identifier, following
18068 normal Ada (case-insensitive) rules for its syntax, with the restriction that
18069 all characters need to be in the ASCII set (no accented letters).
18071 @node Using gnatprep
18072 @section Using @code{gnatprep}
18075 To call @code{gnatprep} use
18078 $ gnatprep @ovar{switches} @var{infile} @var{outfile} @ovar{deffile}
18085 is an optional sequence of switches as described in the next section.
18088 is the full name of the input file, which is an Ada source
18089 file containing preprocessor directives.
18092 is the full name of the output file, which is an Ada source
18093 in standard Ada form. When used with GNAT, this file name will
18094 normally have an ads or adb suffix.
18097 is the full name of a text file containing definitions of
18098 preprocessing symbols to be referenced by the preprocessor. This argument is
18099 optional, and can be replaced by the use of the @option{-D} switch.
18103 @node Switches for gnatprep
18104 @section Switches for @code{gnatprep}
18109 @item ^-b^/BLANK_LINES^
18110 @cindex @option{^-b^/BLANK_LINES^} (@command{gnatprep})
18111 Causes both preprocessor lines and the lines deleted by
18112 preprocessing to be replaced by blank lines in the output source file,
18113 preserving line numbers in the output file.
18115 @item ^-c^/COMMENTS^
18116 @cindex @option{^-c^/COMMENTS^} (@command{gnatprep})
18117 Causes both preprocessor lines and the lines deleted
18118 by preprocessing to be retained in the output source as comments marked
18119 with the special string @code{"--! "}. This option will result in line numbers
18120 being preserved in the output file.
18122 @item ^-C^/REPLACE_IN_COMMENTS^
18123 @cindex @option{^-C^/REPLACE_IN_COMMENTS^} (@command{gnatprep})
18124 Causes comments to be scanned. Normally comments are ignored by gnatprep.
18125 If this option is specified, then comments are scanned and any $symbol
18126 substitutions performed as in program text. This is particularly useful
18127 when structured comments are used (e.g., when writing programs in the
18128 SPARK dialect of Ada). Note that this switch is not available when
18129 doing integrated preprocessing (it would be useless in this context
18130 since comments are ignored by the compiler in any case).
18132 @item ^-Dsymbol=value^/ASSOCIATE="symbol=value"^
18133 @cindex @option{^-D^/ASSOCIATE^} (@command{gnatprep})
18134 Defines a new preprocessing symbol, associated with value. If no value is given
18135 on the command line, then symbol is considered to be @code{True}. This switch
18136 can be used in place of a definition file.
18140 @cindex @option{/REMOVE} (@command{gnatprep})
18141 This is the default setting which causes lines deleted by preprocessing
18142 to be entirely removed from the output file.
18145 @item ^-r^/REFERENCE^
18146 @cindex @option{^-r^/REFERENCE^} (@command{gnatprep})
18147 Causes a @code{Source_Reference} pragma to be generated that
18148 references the original input file, so that error messages will use
18149 the file name of this original file. The use of this switch implies
18150 that preprocessor lines are not to be removed from the file, so its
18151 use will force @option{^-b^/BLANK_LINES^} mode if
18152 @option{^-c^/COMMENTS^}
18153 has not been specified explicitly.
18155 Note that if the file to be preprocessed contains multiple units, then
18156 it will be necessary to @code{gnatchop} the output file from
18157 @code{gnatprep}. If a @code{Source_Reference} pragma is present
18158 in the preprocessed file, it will be respected by
18159 @code{gnatchop ^-r^/REFERENCE^}
18160 so that the final chopped files will correctly refer to the original
18161 input source file for @code{gnatprep}.
18163 @item ^-s^/SYMBOLS^
18164 @cindex @option{^-s^/SYMBOLS^} (@command{gnatprep})
18165 Causes a sorted list of symbol names and values to be
18166 listed on the standard output file.
18168 @item ^-u^/UNDEFINED^
18169 @cindex @option{^-u^/UNDEFINED^} (@command{gnatprep})
18170 Causes undefined symbols to be treated as having the value FALSE in the context
18171 of a preprocessor test. In the absence of this option, an undefined symbol in
18172 a @code{#if} or @code{#elsif} test will be treated as an error.
18178 Note: if neither @option{-b} nor @option{-c} is present,
18179 then preprocessor lines and
18180 deleted lines are completely removed from the output, unless -r is
18181 specified, in which case -b is assumed.
18184 @node Form of Definitions File
18185 @section Form of Definitions File
18188 The definitions file contains lines of the form
18195 where symbol is a preprocessing symbol, and value is one of the following:
18199 Empty, corresponding to a null substitution
18201 A string literal using normal Ada syntax
18203 Any sequence of characters from the set
18204 (letters, digits, period, underline).
18208 Comment lines may also appear in the definitions file, starting with
18209 the usual @code{--},
18210 and comments may be added to the definitions lines.
18212 @node Form of Input Text for gnatprep
18213 @section Form of Input Text for @code{gnatprep}
18216 The input text may contain preprocessor conditional inclusion lines,
18217 as well as general symbol substitution sequences.
18219 The preprocessor conditional inclusion commands have the form
18224 #if @i{expression} @r{[}then@r{]}
18226 #elsif @i{expression} @r{[}then@r{]}
18228 #elsif @i{expression} @r{[}then@r{]}
18239 In this example, @i{expression} is defined by the following grammar:
18241 @i{expression} ::= <symbol>
18242 @i{expression} ::= <symbol> = "<value>"
18243 @i{expression} ::= <symbol> = <symbol>
18244 @i{expression} ::= <symbol> 'Defined
18245 @i{expression} ::= not @i{expression}
18246 @i{expression} ::= @i{expression} and @i{expression}
18247 @i{expression} ::= @i{expression} or @i{expression}
18248 @i{expression} ::= @i{expression} and then @i{expression}
18249 @i{expression} ::= @i{expression} or else @i{expression}
18250 @i{expression} ::= ( @i{expression} )
18253 The following restriction exists: it is not allowed to have "and" or "or"
18254 following "not" in the same expression without parentheses. For example, this
18261 This should be one of the following:
18269 For the first test (@i{expression} ::= <symbol>) the symbol must have
18270 either the value true or false, that is to say the right-hand of the
18271 symbol definition must be one of the (case-insensitive) literals
18272 @code{True} or @code{False}. If the value is true, then the
18273 corresponding lines are included, and if the value is false, they are
18276 The test (@i{expression} ::= <symbol> @code{'Defined}) is true only if
18277 the symbol has been defined in the definition file or by a @option{-D}
18278 switch on the command line. Otherwise, the test is false.
18280 The equality tests are case insensitive, as are all the preprocessor lines.
18282 If the symbol referenced is not defined in the symbol definitions file,
18283 then the effect depends on whether or not switch @option{-u}
18284 is specified. If so, then the symbol is treated as if it had the value
18285 false and the test fails. If this switch is not specified, then
18286 it is an error to reference an undefined symbol. It is also an error to
18287 reference a symbol that is defined with a value other than @code{True}
18290 The use of the @code{not} operator inverts the sense of this logical test.
18291 The @code{not} operator cannot be combined with the @code{or} or @code{and}
18292 operators, without parentheses. For example, "if not X or Y then" is not
18293 allowed, but "if (not X) or Y then" and "if not (X or Y) then" are.
18295 The @code{then} keyword is optional as shown
18297 The @code{#} must be the first non-blank character on a line, but
18298 otherwise the format is free form. Spaces or tabs may appear between
18299 the @code{#} and the keyword. The keywords and the symbols are case
18300 insensitive as in normal Ada code. Comments may be used on a
18301 preprocessor line, but other than that, no other tokens may appear on a
18302 preprocessor line. Any number of @code{elsif} clauses can be present,
18303 including none at all. The @code{else} is optional, as in Ada.
18305 The @code{#} marking the start of a preprocessor line must be the first
18306 non-blank character on the line, i.e., it must be preceded only by
18307 spaces or horizontal tabs.
18309 Symbol substitution outside of preprocessor lines is obtained by using
18317 anywhere within a source line, except in a comment or within a
18318 string literal. The identifier
18319 following the @code{$} must match one of the symbols defined in the symbol
18320 definition file, and the result is to substitute the value of the
18321 symbol in place of @code{$symbol} in the output file.
18323 Note that although the substitution of strings within a string literal
18324 is not possible, it is possible to have a symbol whose defined value is
18325 a string literal. So instead of setting XYZ to @code{hello} and writing:
18328 Header : String := "$XYZ";
18332 you should set XYZ to @code{"hello"} and write:
18335 Header : String := $XYZ;
18339 and then the substitution will occur as desired.
18342 @node The GNAT Run-Time Library Builder gnatlbr
18343 @chapter The GNAT Run-Time Library Builder @code{gnatlbr}
18345 @cindex Library builder
18348 @code{gnatlbr} is a tool for rebuilding the GNAT run time with user
18349 supplied configuration pragmas.
18352 * Running gnatlbr::
18353 * Switches for gnatlbr::
18354 * Examples of gnatlbr Usage::
18357 @node Running gnatlbr
18358 @section Running @code{gnatlbr}
18361 The @code{gnatlbr} command has the form
18364 $ GNAT LIBRARY /@r{[}CREATE@r{|}SET@r{|}DELETE@r{]}=directory @r{[}/CONFIG=file@r{]}
18367 @node Switches for gnatlbr
18368 @section Switches for @code{gnatlbr}
18371 @code{gnatlbr} recognizes the following switches:
18375 @item /CREATE=directory
18376 @cindex @code{/CREATE} (@code{gnatlbr})
18377 Create the new run-time library in the specified directory.
18379 @item /SET=directory
18380 @cindex @code{/SET} (@code{gnatlbr})
18381 Make the library in the specified directory the current run-time library.
18383 @item /DELETE=directory
18384 @cindex @code{/DELETE} (@code{gnatlbr})
18385 Delete the run-time library in the specified directory.
18388 @cindex @code{/CONFIG} (@code{gnatlbr})
18389 With /CREATE: Use the configuration pragmas in the specified file when
18390 building the library.
18392 With /SET: Use the configuration pragmas in the specified file when
18397 @node Examples of gnatlbr Usage
18398 @section Example of @code{gnatlbr} Usage
18401 Contents of VAXFLOAT.ADC:
18402 pragma Float_Representation (VAX_Float);
18404 $ GNAT LIBRARY /CREATE=[.VAXFLOAT] /CONFIG=VAXFLOAT.ADC
18406 GNAT LIBRARY rebuilds the run-time library in directory [.VAXFLOAT]
18411 @node The GNAT Library Browser gnatls
18412 @chapter The GNAT Library Browser @code{gnatls}
18414 @cindex Library browser
18417 @code{gnatls} is a tool that outputs information about compiled
18418 units. It gives the relationship between objects, unit names and source
18419 files. It can also be used to check the source dependencies of a unit
18420 as well as various characteristics.
18422 Note: to invoke @code{gnatls} with a project file, use the @code{gnat}
18423 driver (see @ref{The GNAT Driver and Project Files}).
18427 * Switches for gnatls::
18428 * Examples of gnatls Usage::
18431 @node Running gnatls
18432 @section Running @code{gnatls}
18435 The @code{gnatls} command has the form
18438 $ gnatls switches @var{object_or_ali_file}
18442 The main argument is the list of object or @file{ali} files
18443 (@pxref{The Ada Library Information Files})
18444 for which information is requested.
18446 In normal mode, without additional option, @code{gnatls} produces a
18447 four-column listing. Each line represents information for a specific
18448 object. The first column gives the full path of the object, the second
18449 column gives the name of the principal unit in this object, the third
18450 column gives the status of the source and the fourth column gives the
18451 full path of the source representing this unit.
18452 Here is a simple example of use:
18456 ^./^[]^demo1.o demo1 DIF demo1.adb
18457 ^./^[]^demo2.o demo2 OK demo2.adb
18458 ^./^[]^hello.o h1 OK hello.adb
18459 ^./^[]^instr-child.o instr.child MOK instr-child.adb
18460 ^./^[]^instr.o instr OK instr.adb
18461 ^./^[]^tef.o tef DIF tef.adb
18462 ^./^[]^text_io_example.o text_io_example OK text_io_example.adb
18463 ^./^[]^tgef.o tgef DIF tgef.adb
18467 The first line can be interpreted as follows: the main unit which is
18469 object file @file{demo1.o} is demo1, whose main source is in
18470 @file{demo1.adb}. Furthermore, the version of the source used for the
18471 compilation of demo1 has been modified (DIF). Each source file has a status
18472 qualifier which can be:
18475 @item OK (unchanged)
18476 The version of the source file used for the compilation of the
18477 specified unit corresponds exactly to the actual source file.
18479 @item MOK (slightly modified)
18480 The version of the source file used for the compilation of the
18481 specified unit differs from the actual source file but not enough to
18482 require recompilation. If you use gnatmake with the qualifier
18483 @option{^-m (minimal recompilation)^/MINIMAL_RECOMPILATION^}, a file marked
18484 MOK will not be recompiled.
18486 @item DIF (modified)
18487 No version of the source found on the path corresponds to the source
18488 used to build this object.
18490 @item ??? (file not found)
18491 No source file was found for this unit.
18493 @item HID (hidden, unchanged version not first on PATH)
18494 The version of the source that corresponds exactly to the source used
18495 for compilation has been found on the path but it is hidden by another
18496 version of the same source that has been modified.
18500 @node Switches for gnatls
18501 @section Switches for @code{gnatls}
18504 @code{gnatls} recognizes the following switches:
18508 @cindex @option{--version} @command{gnatls}
18509 Display Copyright and version, then exit disregarding all other options.
18512 @cindex @option{--help} @command{gnatls}
18513 If @option{--version} was not used, display usage, then exit disregarding
18516 @item ^-a^/ALL_UNITS^
18517 @cindex @option{^-a^/ALL_UNITS^} (@code{gnatls})
18518 Consider all units, including those of the predefined Ada library.
18519 Especially useful with @option{^-d^/DEPENDENCIES^}.
18521 @item ^-d^/DEPENDENCIES^
18522 @cindex @option{^-d^/DEPENDENCIES^} (@code{gnatls})
18523 List sources from which specified units depend on.
18525 @item ^-h^/OUTPUT=OPTIONS^
18526 @cindex @option{^-h^/OUTPUT=OPTIONS^} (@code{gnatls})
18527 Output the list of options.
18529 @item ^-o^/OUTPUT=OBJECTS^
18530 @cindex @option{^-o^/OUTPUT=OBJECTS^} (@code{gnatls})
18531 Only output information about object files.
18533 @item ^-s^/OUTPUT=SOURCES^
18534 @cindex @option{^-s^/OUTPUT=SOURCES^} (@code{gnatls})
18535 Only output information about source files.
18537 @item ^-u^/OUTPUT=UNITS^
18538 @cindex @option{^-u^/OUTPUT=UNITS^} (@code{gnatls})
18539 Only output information about compilation units.
18541 @item ^-files^/FILES^=@var{file}
18542 @cindex @option{^-files^/FILES^} (@code{gnatls})
18543 Take as arguments the files listed in text file @var{file}.
18544 Text file @var{file} may contain empty lines that are ignored.
18545 Each nonempty line should contain the name of an existing file.
18546 Several such switches may be specified simultaneously.
18548 @item ^-aO^/OBJECT_SEARCH=^@var{dir}
18549 @itemx ^-aI^/SOURCE_SEARCH=^@var{dir}
18550 @itemx ^-I^/SEARCH=^@var{dir}
18551 @itemx ^-I-^/NOCURRENT_DIRECTORY^
18553 @cindex @option{^-aO^/OBJECT_SEARCH^} (@code{gnatls})
18554 @cindex @option{^-aI^/SOURCE_SEARCH^} (@code{gnatls})
18555 @cindex @option{^-I^/SEARCH^} (@code{gnatls})
18556 @cindex @option{^-I-^/NOCURRENT_DIRECTORY^} (@code{gnatls})
18557 Source path manipulation. Same meaning as the equivalent @command{gnatmake}
18558 flags (@pxref{Switches for gnatmake}).
18560 @item --RTS=@var{rts-path}
18561 @cindex @option{--RTS} (@code{gnatls})
18562 Specifies the default location of the runtime library. Same meaning as the
18563 equivalent @command{gnatmake} flag (@pxref{Switches for gnatmake}).
18565 @item ^-v^/OUTPUT=VERBOSE^
18566 @cindex @option{^-v^/OUTPUT=VERBOSE^} (@code{gnatls})
18567 Verbose mode. Output the complete source, object and project paths. Do not use
18568 the default column layout but instead use long format giving as much as
18569 information possible on each requested units, including special
18570 characteristics such as:
18573 @item Preelaborable
18574 The unit is preelaborable in the Ada sense.
18577 No elaboration code has been produced by the compiler for this unit.
18580 The unit is pure in the Ada sense.
18582 @item Elaborate_Body
18583 The unit contains a pragma Elaborate_Body.
18586 The unit contains a pragma Remote_Types.
18588 @item Shared_Passive
18589 The unit contains a pragma Shared_Passive.
18592 This unit is part of the predefined environment and cannot be modified
18595 @item Remote_Call_Interface
18596 The unit contains a pragma Remote_Call_Interface.
18602 @node Examples of gnatls Usage
18603 @section Example of @code{gnatls} Usage
18607 Example of using the verbose switch. Note how the source and
18608 object paths are affected by the -I switch.
18611 $ gnatls -v -I.. demo1.o
18613 GNATLS 5.03w (20041123-34)
18614 Copyright 1997-2004 Free Software Foundation, Inc.
18616 Source Search Path:
18617 <Current_Directory>
18619 /home/comar/local/adainclude/
18621 Object Search Path:
18622 <Current_Directory>
18624 /home/comar/local/lib/gcc-lib/x86-linux/3.4.3/adalib/
18626 Project Search Path:
18627 <Current_Directory>
18628 /home/comar/local/lib/gnat/
18633 Kind => subprogram body
18634 Flags => No_Elab_Code
18635 Source => demo1.adb modified
18639 The following is an example of use of the dependency list.
18640 Note the use of the -s switch
18641 which gives a straight list of source files. This can be useful for
18642 building specialized scripts.
18645 $ gnatls -d demo2.o
18646 ./demo2.o demo2 OK demo2.adb
18652 $ gnatls -d -s -a demo1.o
18654 /home/comar/local/adainclude/ada.ads
18655 /home/comar/local/adainclude/a-finali.ads
18656 /home/comar/local/adainclude/a-filico.ads
18657 /home/comar/local/adainclude/a-stream.ads
18658 /home/comar/local/adainclude/a-tags.ads
18661 /home/comar/local/adainclude/gnat.ads
18662 /home/comar/local/adainclude/g-io.ads
18664 /home/comar/local/adainclude/system.ads
18665 /home/comar/local/adainclude/s-exctab.ads
18666 /home/comar/local/adainclude/s-finimp.ads
18667 /home/comar/local/adainclude/s-finroo.ads
18668 /home/comar/local/adainclude/s-secsta.ads
18669 /home/comar/local/adainclude/s-stalib.ads
18670 /home/comar/local/adainclude/s-stoele.ads
18671 /home/comar/local/adainclude/s-stratt.ads
18672 /home/comar/local/adainclude/s-tasoli.ads
18673 /home/comar/local/adainclude/s-unstyp.ads
18674 /home/comar/local/adainclude/unchconv.ads
18680 GNAT LIST /DEPENDENCIES /OUTPUT=SOURCES /ALL_UNITS DEMO1.ADB
18682 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]ada.ads
18683 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]a-finali.ads
18684 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]a-filico.ads
18685 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]a-stream.ads
18686 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]a-tags.ads
18690 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]gnat.ads
18691 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]g-io.ads
18693 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]system.ads
18694 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]s-exctab.ads
18695 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]s-finimp.ads
18696 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]s-finroo.ads
18697 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]s-secsta.ads
18698 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]s-stalib.ads
18699 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]s-stoele.ads
18700 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]s-stratt.ads
18701 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]s-tasoli.ads
18702 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]s-unstyp.ads
18703 GNU:[LIB.OPENVMS7_1.2_8_1.ADALIB]unchconv.ads
18707 @node Cleaning Up Using gnatclean
18708 @chapter Cleaning Up Using @code{gnatclean}
18710 @cindex Cleaning tool
18713 @code{gnatclean} is a tool that allows the deletion of files produced by the
18714 compiler, binder and linker, including ALI files, object files, tree files,
18715 expanded source files, library files, interface copy source files, binder
18716 generated files and executable files.
18719 * Running gnatclean::
18720 * Switches for gnatclean::
18721 @c * Examples of gnatclean Usage::
18724 @node Running gnatclean
18725 @section Running @code{gnatclean}
18728 The @code{gnatclean} command has the form:
18731 $ gnatclean switches @var{names}
18735 @var{names} is a list of source file names. Suffixes @code{.^ads^ADS^} and
18736 @code{^adb^ADB^} may be omitted. If a project file is specified using switch
18737 @code{^-P^/PROJECT_FILE=^}, then @var{names} may be completely omitted.
18740 In normal mode, @code{gnatclean} delete the files produced by the compiler and,
18741 if switch @code{^-c^/COMPILER_FILES_ONLY^} is not specified, by the binder and
18742 the linker. In informative-only mode, specified by switch
18743 @code{^-n^/NODELETE^}, the list of files that would have been deleted in
18744 normal mode is listed, but no file is actually deleted.
18746 @node Switches for gnatclean
18747 @section Switches for @code{gnatclean}
18750 @code{gnatclean} recognizes the following switches:
18754 @cindex @option{--version} @command{gnatclean}
18755 Display Copyright and version, then exit disregarding all other options.
18758 @cindex @option{--help} @command{gnatclean}
18759 If @option{--version} was not used, display usage, then exit disregarding
18762 @item ^-c^/COMPILER_FILES_ONLY^
18763 @cindex @option{^-c^/COMPILER_FILES_ONLY^} (@code{gnatclean})
18764 Only attempt to delete the files produced by the compiler, not those produced
18765 by the binder or the linker. The files that are not to be deleted are library
18766 files, interface copy files, binder generated files and executable files.
18768 @item ^-D ^/DIRECTORY_OBJECTS=^@var{dir}
18769 @cindex @option{^-D^/DIRECTORY_OBJECTS^} (@code{gnatclean})
18770 Indicate that ALI and object files should normally be found in directory
18773 @item ^-F^/FULL_PATH_IN_BRIEF_MESSAGES^
18774 @cindex @option{^-F^/FULL_PATH_IN_BRIEF_MESSAGES^} (@code{gnatclean})
18775 When using project files, if some errors or warnings are detected during
18776 parsing and verbose mode is not in effect (no use of switch
18777 ^-v^/VERBOSE^), then error lines start with the full path name of the project
18778 file, rather than its simple file name.
18781 @cindex @option{^-h^/HELP^} (@code{gnatclean})
18782 Output a message explaining the usage of @code{^gnatclean^gnatclean^}.
18784 @item ^-n^/NODELETE^
18785 @cindex @option{^-n^/NODELETE^} (@code{gnatclean})
18786 Informative-only mode. Do not delete any files. Output the list of the files
18787 that would have been deleted if this switch was not specified.
18789 @item ^-P^/PROJECT_FILE=^@var{project}
18790 @cindex @option{^-P^/PROJECT_FILE^} (@code{gnatclean})
18791 Use project file @var{project}. Only one such switch can be used.
18792 When cleaning a project file, the files produced by the compilation of the
18793 immediate sources or inherited sources of the project files are to be
18794 deleted. This is not depending on the presence or not of executable names
18795 on the command line.
18798 @cindex @option{^-q^/QUIET^} (@code{gnatclean})
18799 Quiet output. If there are no errors, do not output anything, except in
18800 verbose mode (switch ^-v^/VERBOSE^) or in informative-only mode
18801 (switch ^-n^/NODELETE^).
18803 @item ^-r^/RECURSIVE^
18804 @cindex @option{^-r^/RECURSIVE^} (@code{gnatclean})
18805 When a project file is specified (using switch ^-P^/PROJECT_FILE=^),
18806 clean all imported and extended project files, recursively. If this switch
18807 is not specified, only the files related to the main project file are to be
18808 deleted. This switch has no effect if no project file is specified.
18810 @item ^-v^/VERBOSE^
18811 @cindex @option{^-v^/VERBOSE^} (@code{gnatclean})
18814 @item ^-vP^/MESSAGES_PROJECT_FILE=^@emph{x}
18815 @cindex @option{^-vP^/MESSAGES_PROJECT_FILE^} (@code{gnatclean})
18816 Indicates the verbosity of the parsing of GNAT project files.
18817 @xref{Switches Related to Project Files}.
18819 @item ^-X^/EXTERNAL_REFERENCE=^@var{name=value}
18820 @cindex @option{^-X^/EXTERNAL_REFERENCE^} (@code{gnatclean})
18821 Indicates that external variable @var{name} has the value @var{value}.
18822 The Project Manager will use this value for occurrences of
18823 @code{external(name)} when parsing the project file.
18824 @xref{Switches Related to Project Files}.
18826 @item ^-aO^/OBJECT_SEARCH=^@var{dir}
18827 @cindex @option{^-aO^/OBJECT_SEARCH^} (@code{gnatclean})
18828 When searching for ALI and object files, look in directory
18831 @item ^-I^/SEARCH=^@var{dir}
18832 @cindex @option{^-I^/SEARCH^} (@code{gnatclean})
18833 Equivalent to @option{^-aO^/OBJECT_SEARCH=^@var{dir}}.
18835 @item ^-I-^/NOCURRENT_DIRECTORY^
18836 @cindex @option{^-I-^/NOCURRENT_DIRECTORY^} (@code{gnatclean})
18837 @cindex Source files, suppressing search
18838 Do not look for ALI or object files in the directory
18839 where @code{gnatclean} was invoked.
18843 @c @node Examples of gnatclean Usage
18844 @c @section Examples of @code{gnatclean} Usage
18847 @node GNAT and Libraries
18848 @chapter GNAT and Libraries
18849 @cindex Library, building, installing, using
18852 This chapter describes how to build and use libraries with GNAT, and also shows
18853 how to recompile the GNAT run-time library. You should be familiar with the
18854 Project Manager facility (@pxref{GNAT Project Manager}) before reading this
18858 * Introduction to Libraries in GNAT::
18859 * General Ada Libraries::
18860 * Stand-alone Ada Libraries::
18861 * Rebuilding the GNAT Run-Time Library::
18864 @node Introduction to Libraries in GNAT
18865 @section Introduction to Libraries in GNAT
18868 A library is, conceptually, a collection of objects which does not have its
18869 own main thread of execution, but rather provides certain services to the
18870 applications that use it. A library can be either statically linked with the
18871 application, in which case its code is directly included in the application,
18872 or, on platforms that support it, be dynamically linked, in which case
18873 its code is shared by all applications making use of this library.
18875 GNAT supports both types of libraries.
18876 In the static case, the compiled code can be provided in different ways. The
18877 simplest approach is to provide directly the set of objects resulting from
18878 compilation of the library source files. Alternatively, you can group the
18879 objects into an archive using whatever commands are provided by the operating
18880 system. For the latter case, the objects are grouped into a shared library.
18882 In the GNAT environment, a library has three types of components:
18888 @xref{The Ada Library Information Files}.
18890 Object files, an archive or a shared library.
18894 A GNAT library may expose all its source files, which is useful for
18895 documentation purposes. Alternatively, it may expose only the units needed by
18896 an external user to make use of the library. That is to say, the specs
18897 reflecting the library services along with all the units needed to compile
18898 those specs, which can include generic bodies or any body implementing an
18899 inlined routine. In the case of @emph{stand-alone libraries} those exposed
18900 units are called @emph{interface units} (@pxref{Stand-alone Ada Libraries}).
18902 All compilation units comprising an application, including those in a library,
18903 need to be elaborated in an order partially defined by Ada's semantics. GNAT
18904 computes the elaboration order from the @file{ALI} files and this is why they
18905 constitute a mandatory part of GNAT libraries.
18906 @emph{Stand-alone libraries} are the exception to this rule because a specific
18907 library elaboration routine is produced independently of the application(s)
18910 @node General Ada Libraries
18911 @section General Ada Libraries
18914 * Building a library::
18915 * Installing a library::
18916 * Using a library::
18919 @node Building a library
18920 @subsection Building a library
18923 The easiest way to build a library is to use the Project Manager,
18924 which supports a special type of project called a @emph{Library Project}
18925 (@pxref{Library Projects}).
18927 A project is considered a library project, when two project-level attributes
18928 are defined in it: @code{Library_Name} and @code{Library_Dir}. In order to
18929 control different aspects of library configuration, additional optional
18930 project-level attributes can be specified:
18933 This attribute controls whether the library is to be static or dynamic
18935 @item Library_Version
18936 This attribute specifies the library version; this value is used
18937 during dynamic linking of shared libraries to determine if the currently
18938 installed versions of the binaries are compatible.
18940 @item Library_Options
18942 These attributes specify additional low-level options to be used during
18943 library generation, and redefine the actual application used to generate
18948 The GNAT Project Manager takes full care of the library maintenance task,
18949 including recompilation of the source files for which objects do not exist
18950 or are not up to date, assembly of the library archive, and installation of
18951 the library (i.e., copying associated source, object and @file{ALI} files
18952 to the specified location).
18954 Here is a simple library project file:
18955 @smallexample @c ada
18957 for Source_Dirs use ("src1", "src2");
18958 for Object_Dir use "obj";
18959 for Library_Name use "mylib";
18960 for Library_Dir use "lib";
18961 for Library_Kind use "dynamic";
18966 and the compilation command to build and install the library:
18968 @smallexample @c ada
18969 $ gnatmake -Pmy_lib
18973 It is not entirely trivial to perform manually all the steps required to
18974 produce a library. We recommend that you use the GNAT Project Manager
18975 for this task. In special cases where this is not desired, the necessary
18976 steps are discussed below.
18978 There are various possibilities for compiling the units that make up the
18979 library: for example with a Makefile (@pxref{Using the GNU make Utility}) or
18980 with a conventional script. For simple libraries, it is also possible to create
18981 a dummy main program which depends upon all the packages that comprise the
18982 interface of the library. This dummy main program can then be given to
18983 @command{gnatmake}, which will ensure that all necessary objects are built.
18985 After this task is accomplished, you should follow the standard procedure
18986 of the underlying operating system to produce the static or shared library.
18988 Here is an example of such a dummy program:
18989 @smallexample @c ada
18991 with My_Lib.Service1;
18992 with My_Lib.Service2;
18993 with My_Lib.Service3;
18994 procedure My_Lib_Dummy is
19002 Here are the generic commands that will build an archive or a shared library.
19005 # compiling the library
19006 $ gnatmake -c my_lib_dummy.adb
19008 # we don't need the dummy object itself
19009 $ rm my_lib_dummy.o my_lib_dummy.ali
19011 # create an archive with the remaining objects
19012 $ ar rc libmy_lib.a *.o
19013 # some systems may require "ranlib" to be run as well
19015 # or create a shared library
19016 $ gcc -shared -o libmy_lib.so *.o
19017 # some systems may require the code to have been compiled with -fPIC
19019 # remove the object files that are now in the library
19022 # Make the ALI files read-only so that gnatmake will not try to
19023 # regenerate the objects that are in the library
19028 Please note that the library must have a name of the form @file{lib@var{xxx}.a}
19029 or @file{lib@var{xxx}.so} (or @file{lib@var{xxx}.dll} on Windows) in order to
19030 be accessed by the directive @option{-l@var{xxx}} at link time.
19032 @node Installing a library
19033 @subsection Installing a library
19034 @cindex @code{ADA_PROJECT_PATH}
19037 If you use project files, library installation is part of the library build
19038 process. Thus no further action is needed in order to make use of the
19039 libraries that are built as part of the general application build. A usable
19040 version of the library is installed in the directory specified by the
19041 @code{Library_Dir} attribute of the library project file.
19043 You may want to install a library in a context different from where the library
19044 is built. This situation arises with third party suppliers, who may want
19045 to distribute a library in binary form where the user is not expected to be
19046 able to recompile the library. The simplest option in this case is to provide
19047 a project file slightly different from the one used to build the library, by
19048 using the @code{externally_built} attribute. For instance, the project
19049 file used to build the library in the previous section can be changed into the
19050 following one when the library is installed:
19052 @smallexample @c projectfile
19054 for Source_Dirs use ("src1", "src2");
19055 for Library_Name use "mylib";
19056 for Library_Dir use "lib";
19057 for Library_Kind use "dynamic";
19058 for Externally_Built use "true";
19063 This project file assumes that the directories @file{src1},
19064 @file{src2}, and @file{lib} exist in
19065 the directory containing the project file. The @code{externally_built}
19066 attribute makes it clear to the GNAT builder that it should not attempt to
19067 recompile any of the units from this library. It allows the library provider to
19068 restrict the source set to the minimum necessary for clients to make use of the
19069 library as described in the first section of this chapter. It is the
19070 responsibility of the library provider to install the necessary sources, ALI
19071 files and libraries in the directories mentioned in the project file. For
19072 convenience, the user's library project file should be installed in a location
19073 that will be searched automatically by the GNAT
19074 builder. These are the directories referenced in the @env{ADA_PROJECT_PATH}
19075 environment variable (@pxref{Importing Projects}), and also the default GNAT
19076 library location that can be queried with @command{gnatls -v} and is usually of
19077 the form $gnat_install_root/lib/gnat.
19079 When project files are not an option, it is also possible, but not recommended,
19080 to install the library so that the sources needed to use the library are on the
19081 Ada source path and the ALI files & libraries be on the Ada Object path (see
19082 @ref{Search Paths and the Run-Time Library (RTL)}. Alternatively, the system
19083 administrator can place general-purpose libraries in the default compiler
19084 paths, by specifying the libraries' location in the configuration files
19085 @file{ada_source_path} and @file{ada_object_path}. These configuration files
19086 must be located in the GNAT installation tree at the same place as the gcc spec
19087 file. The location of the gcc spec file can be determined as follows:
19093 The configuration files mentioned above have a simple format: each line
19094 must contain one unique directory name.
19095 Those names are added to the corresponding path
19096 in their order of appearance in the file. The names can be either absolute
19097 or relative; in the latter case, they are relative to where theses files
19100 The files @file{ada_source_path} and @file{ada_object_path} might not be
19102 GNAT installation, in which case, GNAT will look for its run-time library in
19103 the directories @file{adainclude} (for the sources) and @file{adalib} (for the
19104 objects and @file{ALI} files). When the files exist, the compiler does not
19105 look in @file{adainclude} and @file{adalib}, and thus the
19106 @file{ada_source_path} file
19107 must contain the location for the GNAT run-time sources (which can simply
19108 be @file{adainclude}). In the same way, the @file{ada_object_path} file must
19109 contain the location for the GNAT run-time objects (which can simply
19112 You can also specify a new default path to the run-time library at compilation
19113 time with the switch @option{--RTS=rts-path}. You can thus choose / change
19114 the run-time library you want your program to be compiled with. This switch is
19115 recognized by @command{gcc}, @command{gnatmake}, @command{gnatbind},
19116 @command{gnatls}, @command{gnatfind} and @command{gnatxref}.
19118 It is possible to install a library before or after the standard GNAT
19119 library, by reordering the lines in the configuration files. In general, a
19120 library must be installed before the GNAT library if it redefines
19123 @node Using a library
19124 @subsection Using a library
19126 @noindent Once again, the project facility greatly simplifies the use of
19127 libraries. In this context, using a library is just a matter of adding a
19128 @code{with} clause in the user project. For instance, to make use of the
19129 library @code{My_Lib} shown in examples in earlier sections, you can
19132 @smallexample @c projectfile
19139 Even if you have a third-party, non-Ada library, you can still use GNAT's
19140 Project Manager facility to provide a wrapper for it. For example, the
19141 following project, when @code{with}ed by your main project, will link with the
19142 third-party library @file{liba.a}:
19144 @smallexample @c projectfile
19147 for Externally_Built use "true";
19148 for Source_Files use ();
19149 for Library_Dir use "lib";
19150 for Library_Name use "a";
19151 for Library_Kind use "static";
19155 This is an alternative to the use of @code{pragma Linker_Options}. It is
19156 especially interesting in the context of systems with several interdependent
19157 static libraries where finding a proper linker order is not easy and best be
19158 left to the tools having visibility over project dependence information.
19161 In order to use an Ada library manually, you need to make sure that this
19162 library is on both your source and object path
19163 (see @ref{Search Paths and the Run-Time Library (RTL)}
19164 and @ref{Search Paths for gnatbind}). Furthermore, when the objects are grouped
19165 in an archive or a shared library, you need to specify the desired
19166 library at link time.
19168 For example, you can use the library @file{mylib} installed in
19169 @file{/dir/my_lib_src} and @file{/dir/my_lib_obj} with the following commands:
19172 $ gnatmake -aI/dir/my_lib_src -aO/dir/my_lib_obj my_appl \
19177 This can be expressed more simply:
19182 when the following conditions are met:
19185 @file{/dir/my_lib_src} has been added by the user to the environment
19186 variable @env{ADA_INCLUDE_PATH}, or by the administrator to the file
19187 @file{ada_source_path}
19189 @file{/dir/my_lib_obj} has been added by the user to the environment
19190 variable @env{ADA_OBJECTS_PATH}, or by the administrator to the file
19191 @file{ada_object_path}
19193 a pragma @code{Linker_Options} has been added to one of the sources.
19196 @smallexample @c ada
19197 pragma Linker_Options ("-lmy_lib");
19201 @node Stand-alone Ada Libraries
19202 @section Stand-alone Ada Libraries
19203 @cindex Stand-alone library, building, using
19206 * Introduction to Stand-alone Libraries::
19207 * Building a Stand-alone Library::
19208 * Creating a Stand-alone Library to be used in a non-Ada context::
19209 * Restrictions in Stand-alone Libraries::
19212 @node Introduction to Stand-alone Libraries
19213 @subsection Introduction to Stand-alone Libraries
19216 A Stand-alone Library (abbreviated ``SAL'') is a library that contains the
19218 elaborate the Ada units that are included in the library. In contrast with
19219 an ordinary library, which consists of all sources, objects and @file{ALI}
19221 library, a SAL may specify a restricted subset of compilation units
19222 to serve as a library interface. In this case, the fully
19223 self-sufficient set of files will normally consist of an objects
19224 archive, the sources of interface units' specs, and the @file{ALI}
19225 files of interface units.
19226 If an interface spec contains a generic unit or an inlined subprogram,
19228 source must also be provided; if the units that must be provided in the source
19229 form depend on other units, the source and @file{ALI} files of those must
19232 The main purpose of a SAL is to minimize the recompilation overhead of client
19233 applications when a new version of the library is installed. Specifically,
19234 if the interface sources have not changed, client applications do not need to
19235 be recompiled. If, furthermore, a SAL is provided in the shared form and its
19236 version, controlled by @code{Library_Version} attribute, is not changed,
19237 then the clients do not need to be relinked.
19239 SALs also allow the library providers to minimize the amount of library source
19240 text exposed to the clients. Such ``information hiding'' might be useful or
19241 necessary for various reasons.
19243 Stand-alone libraries are also well suited to be used in an executable whose
19244 main routine is not written in Ada.
19246 @node Building a Stand-alone Library
19247 @subsection Building a Stand-alone Library
19250 GNAT's Project facility provides a simple way of building and installing
19251 stand-alone libraries; see @ref{Stand-alone Library Projects}.
19252 To be a Stand-alone Library Project, in addition to the two attributes
19253 that make a project a Library Project (@code{Library_Name} and
19254 @code{Library_Dir}; see @ref{Library Projects}), the attribute
19255 @code{Library_Interface} must be defined. For example:
19257 @smallexample @c projectfile
19259 for Library_Dir use "lib_dir";
19260 for Library_Name use "dummy";
19261 for Library_Interface use ("int1", "int1.child");
19266 Attribute @code{Library_Interface} has a non-empty string list value,
19267 each string in the list designating a unit contained in an immediate source
19268 of the project file.
19270 When a Stand-alone Library is built, first the binder is invoked to build
19271 a package whose name depends on the library name
19272 (@file{^b~dummy.ads/b^B$DUMMY.ADS/B^} in the example above).
19273 This binder-generated package includes initialization and
19274 finalization procedures whose
19275 names depend on the library name (@code{dummyinit} and @code{dummyfinal}
19277 above). The object corresponding to this package is included in the library.
19279 You must ensure timely (e.g., prior to any use of interfaces in the SAL)
19280 calling of these procedures if a static SAL is built, or if a shared SAL
19282 with the project-level attribute @code{Library_Auto_Init} set to
19285 For a Stand-Alone Library, only the @file{ALI} files of the Interface Units
19286 (those that are listed in attribute @code{Library_Interface}) are copied to
19287 the Library Directory. As a consequence, only the Interface Units may be
19288 imported from Ada units outside of the library. If other units are imported,
19289 the binding phase will fail.
19291 The attribute @code{Library_Src_Dir} may be specified for a
19292 Stand-Alone Library. @code{Library_Src_Dir} is a simple attribute that has a
19293 single string value. Its value must be the path (absolute or relative to the
19294 project directory) of an existing directory. This directory cannot be the
19295 object directory or one of the source directories, but it can be the same as
19296 the library directory. The sources of the Interface
19297 Units of the library that are needed by an Ada client of the library will be
19298 copied to the designated directory, called the Interface Copy directory.
19299 These sources include the specs of the Interface Units, but they may also
19300 include bodies and subunits, when pragmas @code{Inline} or @code{Inline_Always}
19301 are used, or when there is a generic unit in the spec. Before the sources
19302 are copied to the Interface Copy directory, an attempt is made to delete all
19303 files in the Interface Copy directory.
19305 Building stand-alone libraries by hand is somewhat tedious, but for those
19306 occasions when it is necessary here are the steps that you need to perform:
19309 Compile all library sources.
19312 Invoke the binder with the switch @option{-n} (No Ada main program),
19313 with all the @file{ALI} files of the interfaces, and
19314 with the switch @option{-L} to give specific names to the @code{init}
19315 and @code{final} procedures. For example:
19317 gnatbind -n int1.ali int2.ali -Lsal1
19321 Compile the binder generated file:
19327 Link the dynamic library with all the necessary object files,
19328 indicating to the linker the names of the @code{init} (and possibly
19329 @code{final}) procedures for automatic initialization (and finalization).
19330 The built library should be placed in a directory different from
19331 the object directory.
19334 Copy the @code{ALI} files of the interface to the library directory,
19335 add in this copy an indication that it is an interface to a SAL
19336 (i.e., add a word @option{SL} on the line in the @file{ALI} file that starts
19337 with letter ``P'') and make the modified copy of the @file{ALI} file
19342 Using SALs is not different from using other libraries
19343 (see @ref{Using a library}).
19345 @node Creating a Stand-alone Library to be used in a non-Ada context
19346 @subsection Creating a Stand-alone Library to be used in a non-Ada context
19349 It is easy to adapt the SAL build procedure discussed above for use of a SAL in
19352 The only extra step required is to ensure that library interface subprograms
19353 are compatible with the main program, by means of @code{pragma Export}
19354 or @code{pragma Convention}.
19356 Here is an example of simple library interface for use with C main program:
19358 @smallexample @c ada
19359 package Interface is
19361 procedure Do_Something;
19362 pragma Export (C, Do_Something, "do_something");
19364 procedure Do_Something_Else;
19365 pragma Export (C, Do_Something_Else, "do_something_else");
19371 On the foreign language side, you must provide a ``foreign'' view of the
19372 library interface; remember that it should contain elaboration routines in
19373 addition to interface subprograms.
19375 The example below shows the content of @code{mylib_interface.h} (note
19376 that there is no rule for the naming of this file, any name can be used)
19378 /* the library elaboration procedure */
19379 extern void mylibinit (void);
19381 /* the library finalization procedure */
19382 extern void mylibfinal (void);
19384 /* the interface exported by the library */
19385 extern void do_something (void);
19386 extern void do_something_else (void);
19390 Libraries built as explained above can be used from any program, provided
19391 that the elaboration procedures (named @code{mylibinit} in the previous
19392 example) are called before the library services are used. Any number of
19393 libraries can be used simultaneously, as long as the elaboration
19394 procedure of each library is called.
19396 Below is an example of a C program that uses the @code{mylib} library.
19399 #include "mylib_interface.h"
19404 /* First, elaborate the library before using it */
19407 /* Main program, using the library exported entities */
19409 do_something_else ();
19411 /* Library finalization at the end of the program */
19418 Note that invoking any library finalization procedure generated by
19419 @code{gnatbind} shuts down the Ada run-time environment.
19421 finalization of all Ada libraries must be performed at the end of the program.
19422 No call to these libraries or to the Ada run-time library should be made
19423 after the finalization phase.
19425 @node Restrictions in Stand-alone Libraries
19426 @subsection Restrictions in Stand-alone Libraries
19429 The pragmas listed below should be used with caution inside libraries,
19430 as they can create incompatibilities with other Ada libraries:
19432 @item pragma @code{Locking_Policy}
19433 @item pragma @code{Queuing_Policy}
19434 @item pragma @code{Task_Dispatching_Policy}
19435 @item pragma @code{Unreserve_All_Interrupts}
19439 When using a library that contains such pragmas, the user must make sure
19440 that all libraries use the same pragmas with the same values. Otherwise,
19441 @code{Program_Error} will
19442 be raised during the elaboration of the conflicting
19443 libraries. The usage of these pragmas and its consequences for the user
19444 should therefore be well documented.
19446 Similarly, the traceback in the exception occurrence mechanism should be
19447 enabled or disabled in a consistent manner across all libraries.
19448 Otherwise, Program_Error will be raised during the elaboration of the
19449 conflicting libraries.
19451 If the @code{Version} or @code{Body_Version}
19452 attributes are used inside a library, then you need to
19453 perform a @code{gnatbind} step that specifies all @file{ALI} files in all
19454 libraries, so that version identifiers can be properly computed.
19455 In practice these attributes are rarely used, so this is unlikely
19456 to be a consideration.
19458 @node Rebuilding the GNAT Run-Time Library
19459 @section Rebuilding the GNAT Run-Time Library
19460 @cindex GNAT Run-Time Library, rebuilding
19461 @cindex Building the GNAT Run-Time Library
19462 @cindex Rebuilding the GNAT Run-Time Library
19463 @cindex Run-Time Library, rebuilding
19466 It may be useful to recompile the GNAT library in various contexts, the
19467 most important one being the use of partition-wide configuration pragmas
19468 such as @code{Normalize_Scalars}. A special Makefile called
19469 @code{Makefile.adalib} is provided to that effect and can be found in
19470 the directory containing the GNAT library. The location of this
19471 directory depends on the way the GNAT environment has been installed and can
19472 be determined by means of the command:
19479 The last entry in the object search path usually contains the
19480 gnat library. This Makefile contains its own documentation and in
19481 particular the set of instructions needed to rebuild a new library and
19484 @node Using the GNU make Utility
19485 @chapter Using the GNU @code{make} Utility
19489 This chapter offers some examples of makefiles that solve specific
19490 problems. It does not explain how to write a makefile (@pxref{Top,, GNU
19491 make, make, GNU @code{make}}), nor does it try to replace the
19492 @command{gnatmake} utility (@pxref{The GNAT Make Program gnatmake}).
19494 All the examples in this section are specific to the GNU version of
19495 make. Although @command{make} is a standard utility, and the basic language
19496 is the same, these examples use some advanced features found only in
19500 * Using gnatmake in a Makefile::
19501 * Automatically Creating a List of Directories::
19502 * Generating the Command Line Switches::
19503 * Overcoming Command Line Length Limits::
19506 @node Using gnatmake in a Makefile
19507 @section Using gnatmake in a Makefile
19512 Complex project organizations can be handled in a very powerful way by
19513 using GNU make combined with gnatmake. For instance, here is a Makefile
19514 which allows you to build each subsystem of a big project into a separate
19515 shared library. Such a makefile allows you to significantly reduce the link
19516 time of very big applications while maintaining full coherence at
19517 each step of the build process.
19519 The list of dependencies are handled automatically by
19520 @command{gnatmake}. The Makefile is simply used to call gnatmake in each of
19521 the appropriate directories.
19523 Note that you should also read the example on how to automatically
19524 create the list of directories
19525 (@pxref{Automatically Creating a List of Directories})
19526 which might help you in case your project has a lot of subdirectories.
19531 @font@heightrm=cmr8
19534 ## This Makefile is intended to be used with the following directory
19536 ## - The sources are split into a series of csc (computer software components)
19537 ## Each of these csc is put in its own directory.
19538 ## Their name are referenced by the directory names.
19539 ## They will be compiled into shared library (although this would also work
19540 ## with static libraries
19541 ## - The main program (and possibly other packages that do not belong to any
19542 ## csc is put in the top level directory (where the Makefile is).
19543 ## toplevel_dir __ first_csc (sources) __ lib (will contain the library)
19544 ## \_ second_csc (sources) __ lib (will contain the library)
19546 ## Although this Makefile is build for shared library, it is easy to modify
19547 ## to build partial link objects instead (modify the lines with -shared and
19550 ## With this makefile, you can change any file in the system or add any new
19551 ## file, and everything will be recompiled correctly (only the relevant shared
19552 ## objects will be recompiled, and the main program will be re-linked).
19554 # The list of computer software component for your project. This might be
19555 # generated automatically.
19558 # Name of the main program (no extension)
19561 # If we need to build objects with -fPIC, uncomment the following line
19564 # The following variable should give the directory containing libgnat.so
19565 # You can get this directory through 'gnatls -v'. This is usually the last
19566 # directory in the Object_Path.
19569 # The directories for the libraries
19570 # (This macro expands the list of CSC to the list of shared libraries, you
19571 # could simply use the expanded form:
19572 # LIB_DIR=aa/lib/libaa.so bb/lib/libbb.so cc/lib/libcc.so
19573 LIB_DIR=$@{foreach dir,$@{CSC_LIST@},$@{dir@}/lib/lib$@{dir@}.so@}
19575 $@{MAIN@}: objects $@{LIB_DIR@}
19576 gnatbind $@{MAIN@} $@{CSC_LIST:%=-aO%/lib@} -shared
19577 gnatlink $@{MAIN@} $@{CSC_LIST:%=-l%@}
19580 # recompile the sources
19581 gnatmake -c -i $@{MAIN@}.adb $@{NEED_FPIC@} $@{CSC_LIST:%=-I%@}
19583 # Note: In a future version of GNAT, the following commands will be simplified
19584 # by a new tool, gnatmlib
19586 mkdir -p $@{dir $@@ @}
19587 cd $@{dir $@@ @} && gcc -shared -o $@{notdir $@@ @} ../*.o -L$@{GLIB@} -lgnat
19588 cd $@{dir $@@ @} && cp -f ../*.ali .
19590 # The dependencies for the modules
19591 # Note that we have to force the expansion of *.o, since in some cases
19592 # make won't be able to do it itself.
19593 aa/lib/libaa.so: $@{wildcard aa/*.o@}
19594 bb/lib/libbb.so: $@{wildcard bb/*.o@}
19595 cc/lib/libcc.so: $@{wildcard cc/*.o@}
19597 # Make sure all of the shared libraries are in the path before starting the
19600 LD_LIBRARY_PATH=`pwd`/aa/lib:`pwd`/bb/lib:`pwd`/cc/lib ./$@{MAIN@}
19603 $@{RM@} -rf $@{CSC_LIST:%=%/lib@}
19604 $@{RM@} $@{CSC_LIST:%=%/*.ali@}
19605 $@{RM@} $@{CSC_LIST:%=%/*.o@}
19606 $@{RM@} *.o *.ali $@{MAIN@}
19609 @node Automatically Creating a List of Directories
19610 @section Automatically Creating a List of Directories
19613 In most makefiles, you will have to specify a list of directories, and
19614 store it in a variable. For small projects, it is often easier to
19615 specify each of them by hand, since you then have full control over what
19616 is the proper order for these directories, which ones should be
19619 However, in larger projects, which might involve hundreds of
19620 subdirectories, it might be more convenient to generate this list
19623 The example below presents two methods. The first one, although less
19624 general, gives you more control over the list. It involves wildcard
19625 characters, that are automatically expanded by @command{make}. Its
19626 shortcoming is that you need to explicitly specify some of the
19627 organization of your project, such as for instance the directory tree
19628 depth, whether some directories are found in a separate tree, @enddots{}
19630 The second method is the most general one. It requires an external
19631 program, called @command{find}, which is standard on all Unix systems. All
19632 the directories found under a given root directory will be added to the
19638 @font@heightrm=cmr8
19641 # The examples below are based on the following directory hierarchy:
19642 # All the directories can contain any number of files
19643 # ROOT_DIRECTORY -> a -> aa -> aaa
19646 # -> b -> ba -> baa
19649 # This Makefile creates a variable called DIRS, that can be reused any time
19650 # you need this list (see the other examples in this section)
19652 # The root of your project's directory hierarchy
19656 # First method: specify explicitly the list of directories
19657 # This allows you to specify any subset of all the directories you need.
19660 DIRS := a/aa/ a/ab/ b/ba/
19663 # Second method: use wildcards
19664 # Note that the argument(s) to wildcard below should end with a '/'.
19665 # Since wildcards also return file names, we have to filter them out
19666 # to avoid duplicate directory names.
19667 # We thus use make's @code{dir} and @code{sort} functions.
19668 # It sets DIRs to the following value (note that the directories aaa and baa
19669 # are not given, unless you change the arguments to wildcard).
19670 # DIRS= ./a/a/ ./b/ ./a/aa/ ./a/ab/ ./a/ac/ ./b/ba/ ./b/bb/ ./b/bc/
19673 DIRS := $@{sort $@{dir $@{wildcard $@{ROOT_DIRECTORY@}/*/
19674 $@{ROOT_DIRECTORY@}/*/*/@}@}@}
19677 # Third method: use an external program
19678 # This command is much faster if run on local disks, avoiding NFS slowdowns.
19679 # This is the most complete command: it sets DIRs to the following value:
19680 # DIRS= ./a ./a/aa ./a/aa/aaa ./a/ab ./a/ac ./b ./b/ba ./b/ba/baa ./b/bb ./b/bc
19683 DIRS := $@{shell find $@{ROOT_DIRECTORY@} -type d -print@}
19687 @node Generating the Command Line Switches
19688 @section Generating the Command Line Switches
19691 Once you have created the list of directories as explained in the
19692 previous section (@pxref{Automatically Creating a List of Directories}),
19693 you can easily generate the command line arguments to pass to gnatmake.
19695 For the sake of completeness, this example assumes that the source path
19696 is not the same as the object path, and that you have two separate lists
19700 # see "Automatically creating a list of directories" to create
19705 GNATMAKE_SWITCHES := $@{patsubst %,-aI%,$@{SOURCE_DIRS@}@}
19706 GNATMAKE_SWITCHES += $@{patsubst %,-aO%,$@{OBJECT_DIRS@}@}
19709 gnatmake $@{GNATMAKE_SWITCHES@} main_unit
19712 @node Overcoming Command Line Length Limits
19713 @section Overcoming Command Line Length Limits
19716 One problem that might be encountered on big projects is that many
19717 operating systems limit the length of the command line. It is thus hard to give
19718 gnatmake the list of source and object directories.
19720 This example shows how you can set up environment variables, which will
19721 make @command{gnatmake} behave exactly as if the directories had been
19722 specified on the command line, but have a much higher length limit (or
19723 even none on most systems).
19725 It assumes that you have created a list of directories in your Makefile,
19726 using one of the methods presented in
19727 @ref{Automatically Creating a List of Directories}.
19728 For the sake of completeness, we assume that the object
19729 path (where the ALI files are found) is different from the sources patch.
19731 Note a small trick in the Makefile below: for efficiency reasons, we
19732 create two temporary variables (SOURCE_LIST and OBJECT_LIST), that are
19733 expanded immediately by @code{make}. This way we overcome the standard
19734 make behavior which is to expand the variables only when they are
19737 On Windows, if you are using the standard Windows command shell, you must
19738 replace colons with semicolons in the assignments to these variables.
19743 @font@heightrm=cmr8
19746 # In this example, we create both ADA_INCLUDE_PATH and ADA_OBJECT_PATH.
19747 # This is the same thing as putting the -I arguments on the command line.
19748 # (the equivalent of using -aI on the command line would be to define
19749 # only ADA_INCLUDE_PATH, the equivalent of -aO is ADA_OBJECT_PATH).
19750 # You can of course have different values for these variables.
19752 # Note also that we need to keep the previous values of these variables, since
19753 # they might have been set before running 'make' to specify where the GNAT
19754 # library is installed.
19756 # see "Automatically creating a list of directories" to create these
19762 space:=$@{empty@} $@{empty@}
19763 SOURCE_LIST := $@{subst $@{space@},:,$@{SOURCE_DIRS@}@}
19764 OBJECT_LIST := $@{subst $@{space@},:,$@{OBJECT_DIRS@}@}
19765 ADA_INCLUDE_PATH += $@{SOURCE_LIST@}
19766 ADA_OBJECT_PATH += $@{OBJECT_LIST@}
19767 export ADA_INCLUDE_PATH
19768 export ADA_OBJECT_PATH
19775 @node Memory Management Issues
19776 @chapter Memory Management Issues
19779 This chapter describes some useful memory pools provided in the GNAT library
19780 and in particular the GNAT Debug Pool facility, which can be used to detect
19781 incorrect uses of access values (including ``dangling references'').
19783 It also describes the @command{gnatmem} tool, which can be used to track down
19788 * Some Useful Memory Pools::
19789 * The GNAT Debug Pool Facility::
19791 * The gnatmem Tool::
19795 @node Some Useful Memory Pools
19796 @section Some Useful Memory Pools
19797 @findex Memory Pool
19798 @cindex storage, pool
19801 The @code{System.Pool_Global} package offers the Unbounded_No_Reclaim_Pool
19802 storage pool. Allocations use the standard system call @code{malloc} while
19803 deallocations use the standard system call @code{free}. No reclamation is
19804 performed when the pool goes out of scope. For performance reasons, the
19805 standard default Ada allocators/deallocators do not use any explicit storage
19806 pools but if they did, they could use this storage pool without any change in
19807 behavior. That is why this storage pool is used when the user
19808 manages to make the default implicit allocator explicit as in this example:
19809 @smallexample @c ada
19810 type T1 is access Something;
19811 -- no Storage pool is defined for T2
19812 type T2 is access Something_Else;
19813 for T2'Storage_Pool use T1'Storage_Pool;
19814 -- the above is equivalent to
19815 for T2'Storage_Pool use System.Pool_Global.Global_Pool_Object;
19819 The @code{System.Pool_Local} package offers the Unbounded_Reclaim_Pool storage
19820 pool. The allocation strategy is similar to @code{Pool_Local}'s
19821 except that the all
19822 storage allocated with this pool is reclaimed when the pool object goes out of
19823 scope. This pool provides a explicit mechanism similar to the implicit one
19824 provided by several Ada 83 compilers for allocations performed through a local
19825 access type and whose purpose was to reclaim memory when exiting the
19826 scope of a given local access. As an example, the following program does not
19827 leak memory even though it does not perform explicit deallocation:
19829 @smallexample @c ada
19830 with System.Pool_Local;
19831 procedure Pooloc1 is
19832 procedure Internal is
19833 type A is access Integer;
19834 X : System.Pool_Local.Unbounded_Reclaim_Pool;
19835 for A'Storage_Pool use X;
19838 for I in 1 .. 50 loop
19843 for I in 1 .. 100 loop
19850 The @code{System.Pool_Size} package implements the Stack_Bounded_Pool used when
19851 @code{Storage_Size} is specified for an access type.
19852 The whole storage for the pool is
19853 allocated at once, usually on the stack at the point where the access type is
19854 elaborated. It is automatically reclaimed when exiting the scope where the
19855 access type is defined. This package is not intended to be used directly by the
19856 user and it is implicitly used for each such declaration:
19858 @smallexample @c ada
19859 type T1 is access Something;
19860 for T1'Storage_Size use 10_000;
19863 @node The GNAT Debug Pool Facility
19864 @section The GNAT Debug Pool Facility
19866 @cindex storage, pool, memory corruption
19869 The use of unchecked deallocation and unchecked conversion can easily
19870 lead to incorrect memory references. The problems generated by such
19871 references are usually difficult to tackle because the symptoms can be
19872 very remote from the origin of the problem. In such cases, it is
19873 very helpful to detect the problem as early as possible. This is the
19874 purpose of the Storage Pool provided by @code{GNAT.Debug_Pools}.
19876 In order to use the GNAT specific debugging pool, the user must
19877 associate a debug pool object with each of the access types that may be
19878 related to suspected memory problems. See Ada Reference Manual 13.11.
19879 @smallexample @c ada
19880 type Ptr is access Some_Type;
19881 Pool : GNAT.Debug_Pools.Debug_Pool;
19882 for Ptr'Storage_Pool use Pool;
19886 @code{GNAT.Debug_Pools} is derived from a GNAT-specific kind of
19887 pool: the @code{Checked_Pool}. Such pools, like standard Ada storage pools,
19888 allow the user to redefine allocation and deallocation strategies. They
19889 also provide a checkpoint for each dereference, through the use of
19890 the primitive operation @code{Dereference} which is implicitly called at
19891 each dereference of an access value.
19893 Once an access type has been associated with a debug pool, operations on
19894 values of the type may raise four distinct exceptions,
19895 which correspond to four potential kinds of memory corruption:
19898 @code{GNAT.Debug_Pools.Accessing_Not_Allocated_Storage}
19900 @code{GNAT.Debug_Pools.Accessing_Deallocated_Storage}
19902 @code{GNAT.Debug_Pools.Freeing_Not_Allocated_Storage}
19904 @code{GNAT.Debug_Pools.Freeing_Deallocated_Storage }
19908 For types associated with a Debug_Pool, dynamic allocation is performed using
19909 the standard GNAT allocation routine. References to all allocated chunks of
19910 memory are kept in an internal dictionary. Several deallocation strategies are
19911 provided, whereupon the user can choose to release the memory to the system,
19912 keep it allocated for further invalid access checks, or fill it with an easily
19913 recognizable pattern for debug sessions. The memory pattern is the old IBM
19914 hexadecimal convention: @code{16#DEADBEEF#}.
19916 See the documentation in the file g-debpoo.ads for more information on the
19917 various strategies.
19919 Upon each dereference, a check is made that the access value denotes a
19920 properly allocated memory location. Here is a complete example of use of
19921 @code{Debug_Pools}, that includes typical instances of memory corruption:
19922 @smallexample @c ada
19926 with Gnat.Io; use Gnat.Io;
19927 with Unchecked_Deallocation;
19928 with Unchecked_Conversion;
19929 with GNAT.Debug_Pools;
19930 with System.Storage_Elements;
19931 with Ada.Exceptions; use Ada.Exceptions;
19932 procedure Debug_Pool_Test is
19934 type T is access Integer;
19935 type U is access all T;
19937 P : GNAT.Debug_Pools.Debug_Pool;
19938 for T'Storage_Pool use P;
19940 procedure Free is new Unchecked_Deallocation (Integer, T);
19941 function UC is new Unchecked_Conversion (U, T);
19944 procedure Info is new GNAT.Debug_Pools.Print_Info(Put_Line);
19954 Put_Line (Integer'Image(B.all));
19956 when E : others => Put_Line ("raised: " & Exception_Name (E));
19961 when E : others => Put_Line ("raised: " & Exception_Name (E));
19965 Put_Line (Integer'Image(B.all));
19967 when E : others => Put_Line ("raised: " & Exception_Name (E));
19972 when E : others => Put_Line ("raised: " & Exception_Name (E));
19975 end Debug_Pool_Test;
19979 The debug pool mechanism provides the following precise diagnostics on the
19980 execution of this erroneous program:
19983 Total allocated bytes : 0
19984 Total deallocated bytes : 0
19985 Current Water Mark: 0
19989 Total allocated bytes : 8
19990 Total deallocated bytes : 0
19991 Current Water Mark: 8
19994 raised: GNAT.DEBUG_POOLS.ACCESSING_DEALLOCATED_STORAGE
19995 raised: GNAT.DEBUG_POOLS.FREEING_DEALLOCATED_STORAGE
19996 raised: GNAT.DEBUG_POOLS.ACCESSING_NOT_ALLOCATED_STORAGE
19997 raised: GNAT.DEBUG_POOLS.FREEING_NOT_ALLOCATED_STORAGE
19999 Total allocated bytes : 8
20000 Total deallocated bytes : 4
20001 Current Water Mark: 4
20006 @node The gnatmem Tool
20007 @section The @command{gnatmem} Tool
20011 The @code{gnatmem} utility monitors dynamic allocation and
20012 deallocation activity in a program, and displays information about
20013 incorrect deallocations and possible sources of memory leaks.
20014 It is designed to work in association with a static runtime library
20015 only and in this context provides three types of information:
20018 General information concerning memory management, such as the total
20019 number of allocations and deallocations, the amount of allocated
20020 memory and the high water mark, i.e.@: the largest amount of allocated
20021 memory in the course of program execution.
20024 Backtraces for all incorrect deallocations, that is to say deallocations
20025 which do not correspond to a valid allocation.
20028 Information on each allocation that is potentially the origin of a memory
20033 * Running gnatmem::
20034 * Switches for gnatmem::
20035 * Example of gnatmem Usage::
20038 @node Running gnatmem
20039 @subsection Running @code{gnatmem}
20042 @code{gnatmem} makes use of the output created by the special version of
20043 allocation and deallocation routines that record call information. This
20044 allows to obtain accurate dynamic memory usage history at a minimal cost to
20045 the execution speed. Note however, that @code{gnatmem} is not supported on
20046 all platforms (currently, it is supported on AIX, HP-UX, GNU/Linux,
20047 Solaris and Windows NT/2000/XP (x86).
20050 The @code{gnatmem} command has the form
20053 $ gnatmem @ovar{switches} user_program
20057 The program must have been linked with the instrumented version of the
20058 allocation and deallocation routines. This is done by linking with the
20059 @file{libgmem.a} library. For correct symbolic backtrace information,
20060 the user program should be compiled with debugging options
20061 (see @ref{Switches for gcc}). For example to build @file{my_program}:
20064 $ gnatmake -g my_program -largs -lgmem
20068 As library @file{libgmem.a} contains an alternate body for package
20069 @code{System.Memory}, @file{s-memory.adb} should not be compiled and linked
20070 when an executable is linked with library @file{libgmem.a}. It is then not
20071 recommended to use @command{gnatmake} with switch @option{^-a^/ALL_FILES^}.
20074 When @file{my_program} is executed, the file @file{gmem.out} is produced.
20075 This file contains information about all allocations and deallocations
20076 performed by the program. It is produced by the instrumented allocations and
20077 deallocations routines and will be used by @code{gnatmem}.
20079 In order to produce symbolic backtrace information for allocations and
20080 deallocations performed by the GNAT run-time library, you need to use a
20081 version of that library that has been compiled with the @option{-g} switch
20082 (see @ref{Rebuilding the GNAT Run-Time Library}).
20084 Gnatmem must be supplied with the @file{gmem.out} file and the executable to
20085 examine. If the location of @file{gmem.out} file was not explicitly supplied by
20086 @option{-i} switch, gnatmem will assume that this file can be found in the
20087 current directory. For example, after you have executed @file{my_program},
20088 @file{gmem.out} can be analyzed by @code{gnatmem} using the command:
20091 $ gnatmem my_program
20095 This will produce the output with the following format:
20097 *************** debut cc
20099 $ gnatmem my_program
20103 Total number of allocations : 45
20104 Total number of deallocations : 6
20105 Final Water Mark (non freed mem) : 11.29 Kilobytes
20106 High Water Mark : 11.40 Kilobytes
20111 Allocation Root # 2
20112 -------------------
20113 Number of non freed allocations : 11
20114 Final Water Mark (non freed mem) : 1.16 Kilobytes
20115 High Water Mark : 1.27 Kilobytes
20117 my_program.adb:23 my_program.alloc
20123 The first block of output gives general information. In this case, the
20124 Ada construct ``@code{@b{new}}'' was executed 45 times, and only 6 calls to an
20125 Unchecked_Deallocation routine occurred.
20128 Subsequent paragraphs display information on all allocation roots.
20129 An allocation root is a specific point in the execution of the program
20130 that generates some dynamic allocation, such as a ``@code{@b{new}}''
20131 construct. This root is represented by an execution backtrace (or subprogram
20132 call stack). By default the backtrace depth for allocations roots is 1, so
20133 that a root corresponds exactly to a source location. The backtrace can
20134 be made deeper, to make the root more specific.
20136 @node Switches for gnatmem
20137 @subsection Switches for @code{gnatmem}
20140 @code{gnatmem} recognizes the following switches:
20145 @cindex @option{-q} (@code{gnatmem})
20146 Quiet. Gives the minimum output needed to identify the origin of the
20147 memory leaks. Omits statistical information.
20150 @cindex @var{N} (@code{gnatmem})
20151 N is an integer literal (usually between 1 and 10) which controls the
20152 depth of the backtraces defining allocation root. The default value for
20153 N is 1. The deeper the backtrace, the more precise the localization of
20154 the root. Note that the total number of roots can depend on this
20155 parameter. This parameter must be specified @emph{before} the name of the
20156 executable to be analyzed, to avoid ambiguity.
20159 @cindex @option{-b} (@code{gnatmem})
20160 This switch has the same effect as just depth parameter.
20162 @item -i @var{file}
20163 @cindex @option{-i} (@code{gnatmem})
20164 Do the @code{gnatmem} processing starting from @file{file}, rather than
20165 @file{gmem.out} in the current directory.
20168 @cindex @option{-m} (@code{gnatmem})
20169 This switch causes @code{gnatmem} to mask the allocation roots that have less
20170 than n leaks. The default value is 1. Specifying the value of 0 will allow to
20171 examine even the roots that didn't result in leaks.
20174 @cindex @option{-s} (@code{gnatmem})
20175 This switch causes @code{gnatmem} to sort the allocation roots according to the
20176 specified order of sort criteria, each identified by a single letter. The
20177 currently supported criteria are @code{n, h, w} standing respectively for
20178 number of unfreed allocations, high watermark, and final watermark
20179 corresponding to a specific root. The default order is @code{nwh}.
20183 @node Example of gnatmem Usage
20184 @subsection Example of @code{gnatmem} Usage
20187 The following example shows the use of @code{gnatmem}
20188 on a simple memory-leaking program.
20189 Suppose that we have the following Ada program:
20191 @smallexample @c ada
20194 with Unchecked_Deallocation;
20195 procedure Test_Gm is
20197 type T is array (1..1000) of Integer;
20198 type Ptr is access T;
20199 procedure Free is new Unchecked_Deallocation (T, Ptr);
20202 procedure My_Alloc is
20207 procedure My_DeAlloc is
20215 for I in 1 .. 5 loop
20216 for J in I .. 5 loop
20227 The program needs to be compiled with debugging option and linked with
20228 @code{gmem} library:
20231 $ gnatmake -g test_gm -largs -lgmem
20235 Then we execute the program as usual:
20242 Then @code{gnatmem} is invoked simply with
20248 which produces the following output (result may vary on different platforms):
20253 Total number of allocations : 18
20254 Total number of deallocations : 5
20255 Final Water Mark (non freed mem) : 53.00 Kilobytes
20256 High Water Mark : 56.90 Kilobytes
20258 Allocation Root # 1
20259 -------------------
20260 Number of non freed allocations : 11
20261 Final Water Mark (non freed mem) : 42.97 Kilobytes
20262 High Water Mark : 46.88 Kilobytes
20264 test_gm.adb:11 test_gm.my_alloc
20266 Allocation Root # 2
20267 -------------------
20268 Number of non freed allocations : 1
20269 Final Water Mark (non freed mem) : 10.02 Kilobytes
20270 High Water Mark : 10.02 Kilobytes
20272 s-secsta.adb:81 system.secondary_stack.ss_init
20274 Allocation Root # 3
20275 -------------------
20276 Number of non freed allocations : 1
20277 Final Water Mark (non freed mem) : 12 Bytes
20278 High Water Mark : 12 Bytes
20280 s-secsta.adb:181 system.secondary_stack.ss_init
20284 Note that the GNAT run time contains itself a certain number of
20285 allocations that have no corresponding deallocation,
20286 as shown here for root #2 and root
20287 #3. This is a normal behavior when the number of non-freed allocations
20288 is one, it allocates dynamic data structures that the run time needs for
20289 the complete lifetime of the program. Note also that there is only one
20290 allocation root in the user program with a single line back trace:
20291 test_gm.adb:11 test_gm.my_alloc, whereas a careful analysis of the
20292 program shows that 'My_Alloc' is called at 2 different points in the
20293 source (line 21 and line 24). If those two allocation roots need to be
20294 distinguished, the backtrace depth parameter can be used:
20297 $ gnatmem 3 test_gm
20301 which will give the following output:
20306 Total number of allocations : 18
20307 Total number of deallocations : 5
20308 Final Water Mark (non freed mem) : 53.00 Kilobytes
20309 High Water Mark : 56.90 Kilobytes
20311 Allocation Root # 1
20312 -------------------
20313 Number of non freed allocations : 10
20314 Final Water Mark (non freed mem) : 39.06 Kilobytes
20315 High Water Mark : 42.97 Kilobytes
20317 test_gm.adb:11 test_gm.my_alloc
20318 test_gm.adb:24 test_gm
20319 b_test_gm.c:52 main
20321 Allocation Root # 2
20322 -------------------
20323 Number of non freed allocations : 1
20324 Final Water Mark (non freed mem) : 10.02 Kilobytes
20325 High Water Mark : 10.02 Kilobytes
20327 s-secsta.adb:81 system.secondary_stack.ss_init
20328 s-secsta.adb:283 <system__secondary_stack___elabb>
20329 b_test_gm.c:33 adainit
20331 Allocation Root # 3
20332 -------------------
20333 Number of non freed allocations : 1
20334 Final Water Mark (non freed mem) : 3.91 Kilobytes
20335 High Water Mark : 3.91 Kilobytes
20337 test_gm.adb:11 test_gm.my_alloc
20338 test_gm.adb:21 test_gm
20339 b_test_gm.c:52 main
20341 Allocation Root # 4
20342 -------------------
20343 Number of non freed allocations : 1
20344 Final Water Mark (non freed mem) : 12 Bytes
20345 High Water Mark : 12 Bytes
20347 s-secsta.adb:181 system.secondary_stack.ss_init
20348 s-secsta.adb:283 <system__secondary_stack___elabb>
20349 b_test_gm.c:33 adainit
20353 The allocation root #1 of the first example has been split in 2 roots #1
20354 and #3 thanks to the more precise associated backtrace.
20358 @node Stack Related Facilities
20359 @chapter Stack Related Facilities
20362 This chapter describes some useful tools associated with stack
20363 checking and analysis. In
20364 particular, it deals with dynamic and static stack usage measurements.
20367 * Stack Overflow Checking::
20368 * Static Stack Usage Analysis::
20369 * Dynamic Stack Usage Analysis::
20372 @node Stack Overflow Checking
20373 @section Stack Overflow Checking
20374 @cindex Stack Overflow Checking
20375 @cindex -fstack-check
20378 For most operating systems, @command{gcc} does not perform stack overflow
20379 checking by default. This means that if the main environment task or
20380 some other task exceeds the available stack space, then unpredictable
20381 behavior will occur. Most native systems offer some level of protection by
20382 adding a guard page at the end of each task stack. This mechanism is usually
20383 not enough for dealing properly with stack overflow situations because
20384 a large local variable could ``jump'' above the guard page.
20385 Furthermore, when the
20386 guard page is hit, there may not be any space left on the stack for executing
20387 the exception propagation code. Enabling stack checking avoids
20390 To activate stack checking, compile all units with the gcc option
20391 @option{-fstack-check}. For example:
20394 gcc -c -fstack-check package1.adb
20398 Units compiled with this option will generate extra instructions to check
20399 that any use of the stack (for procedure calls or for declaring local
20400 variables in declare blocks) does not exceed the available stack space.
20401 If the space is exceeded, then a @code{Storage_Error} exception is raised.
20403 For declared tasks, the stack size is controlled by the size
20404 given in an applicable @code{Storage_Size} pragma or by the value specified
20405 at bind time with @option{-d} (@pxref{Switches for gnatbind}) or is set to
20406 the default size as defined in the GNAT runtime otherwise.
20408 For the environment task, the stack size depends on
20409 system defaults and is unknown to the compiler. Stack checking
20410 may still work correctly if a fixed
20411 size stack is allocated, but this cannot be guaranteed.
20413 To ensure that a clean exception is signalled for stack
20414 overflow, set the environment variable
20415 @env{GNAT_STACK_LIMIT} to indicate the maximum
20416 stack area that can be used, as in:
20417 @cindex GNAT_STACK_LIMIT
20420 SET GNAT_STACK_LIMIT 1600
20424 The limit is given in kilobytes, so the above declaration would
20425 set the stack limit of the environment task to 1.6 megabytes.
20426 Note that the only purpose of this usage is to limit the amount
20427 of stack used by the environment task. If it is necessary to
20428 increase the amount of stack for the environment task, then this
20429 is an operating systems issue, and must be addressed with the
20430 appropriate operating systems commands.
20433 To have a fixed size stack in the environment task, the stack must be put
20434 in the P0 address space and its size specified. Use these switches to
20438 gnatmake my_progs -largs "-Wl,--opt=STACK=4000,/p0image"
20442 The quotes are required to keep case. The number after @samp{STACK=} is the
20443 size of the environmental task stack in pagelets (512 bytes). In this example
20444 the stack size is about 2 megabytes.
20447 A consequence of the @option{/p0image} qualifier is also to makes RMS buffers
20448 be placed in P0 space. Refer to @cite{HP OpenVMS Linker Utility Manual} for
20449 more details about the @option{/p0image} qualifier and the @option{stack}
20453 @node Static Stack Usage Analysis
20454 @section Static Stack Usage Analysis
20455 @cindex Static Stack Usage Analysis
20456 @cindex -fstack-usage
20459 A unit compiled with @option{-fstack-usage} will generate an extra file
20461 the maximum amount of stack used, on a per-function basis.
20462 The file has the same
20463 basename as the target object file with a @file{.su} extension.
20464 Each line of this file is made up of three fields:
20468 The name of the function.
20472 One or more qualifiers: @code{static}, @code{dynamic}, @code{bounded}.
20475 The second field corresponds to the size of the known part of the function
20478 The qualifier @code{static} means that the function frame size
20480 It usually means that all local variables have a static size.
20481 In this case, the second field is a reliable measure of the function stack
20484 The qualifier @code{dynamic} means that the function frame size is not static.
20485 It happens mainly when some local variables have a dynamic size. When this
20486 qualifier appears alone, the second field is not a reliable measure
20487 of the function stack analysis. When it is qualified with @code{bounded}, it
20488 means that the second field is a reliable maximum of the function stack
20491 @node Dynamic Stack Usage Analysis
20492 @section Dynamic Stack Usage Analysis
20495 It is possible to measure the maximum amount of stack used by a task, by
20496 adding a switch to @command{gnatbind}, as:
20499 $ gnatbind -u0 file
20503 With this option, at each task termination, its stack usage is output on
20505 It is not always convenient to output the stack usage when the program
20506 is still running. Hence, it is possible to delay this output until program
20507 termination. for a given number of tasks specified as the argument of the
20508 @option{-u} option. For instance:
20511 $ gnatbind -u100 file
20515 will buffer the stack usage information of the first 100 tasks to terminate and
20516 output this info at program termination. Results are displayed in four
20520 Index | Task Name | Stack Size | Stack Usage [Value +/- Variation]
20527 is a number associated with each task.
20530 is the name of the task analyzed.
20533 is the maximum size for the stack.
20536 is the measure done by the stack analyzer. In order to prevent overflow, the stack
20537 is not entirely analyzed, and it's not possible to know exactly how
20538 much has actually been used. The report thus contains the theoretical stack usage
20539 (Value) and the possible variation (Variation) around this value.
20544 The environment task stack, e.g., the stack that contains the main unit, is
20545 only processed when the environment variable GNAT_STACK_LIMIT is set.
20548 @c *********************************
20550 @c *********************************
20551 @node Verifying Properties Using gnatcheck
20552 @chapter Verifying Properties Using @command{gnatcheck}
20554 @cindex @command{gnatcheck}
20557 The @command{gnatcheck} tool is an ASIS-based utility that checks properties
20558 of Ada source files according to a given set of semantic rules.
20561 In order to check compliance with a given rule, @command{gnatcheck} has to
20562 semantically analyze the Ada sources.
20563 Therefore, checks can only be performed on
20564 legal Ada units. Moreover, when a unit depends semantically upon units located
20565 outside the current directory, the source search path has to be provided when
20566 calling @command{gnatcheck}, either through a specified project file or
20567 through @command{gnatcheck} switches as described below.
20569 A number of rules are predefined in @command{gnatcheck} and are described
20570 later in this chapter.
20571 You can also add new rules, by modifying the @command{gnatcheck} code and
20572 rebuilding the tool. In order to add a simple rule making some local checks,
20573 a small amount of straightforward ASIS-based programming is usually needed.
20575 Project support for @command{gnatcheck} is provided by the GNAT
20576 driver (see @ref{The GNAT Driver and Project Files}).
20578 Invoking @command{gnatcheck} on the command line has the form:
20581 $ gnatcheck @ovar{switches} @{@var{filename}@}
20582 @r{[}^-files^/FILES^=@{@var{arg_list_filename}@}@r{]}
20583 @r{[}-cargs @var{gcc_switches}@r{]} @r{[}-rules @var{rule_options}@r{]}
20590 @var{switches} specify the general tool options
20593 Each @var{filename} is the name (including the extension) of a source
20594 file to process. ``Wildcards'' are allowed, and
20595 the file name may contain path information.
20598 Each @var{arg_list_filename} is the name (including the extension) of a text
20599 file containing the names of the source files to process, separated by spaces
20603 @var{gcc_switches} is a list of switches for
20604 @command{gcc}. They will be passed on to all compiler invocations made by
20605 @command{gnatcheck} to generate the ASIS trees. Here you can provide
20606 @option{^-I^/INCLUDE_DIRS=^} switches to form the source search path,
20607 and use the @option{-gnatec} switch to set the configuration file.
20610 @var{rule_options} is a list of options for controlling a set of
20611 rules to be checked by @command{gnatcheck} (@pxref{gnatcheck Rule Options}).
20615 Either a @file{@var{filename}} or an @file{@var{arg_list_filename}} must be supplied.
20618 * Format of the Report File::
20619 * General gnatcheck Switches::
20620 * gnatcheck Rule Options::
20621 * Adding the Results of Compiler Checks to gnatcheck Output::
20622 * Project-Wide Checks::
20623 * Predefined Rules::
20626 @node Format of the Report File
20627 @section Format of the Report File
20628 @cindex Report file (for @code{gnatcheck})
20631 The @command{gnatcheck} tool outputs on @file{stdout} all messages concerning
20633 It also creates a text file that
20634 contains the complete report of the last gnatcheck run. By default this file is
20635 named named @file{^gnatcheck.out^GNATCHECK.OUT^} and it is located in the current
20636 directory, @option{^-o^/OUTPUT^} option can be used to change the name and/or
20637 location of the report file. This report contains:
20639 @item a list of the Ada source files being checked,
20640 @item a list of enabled and disabled rules,
20641 @item a list of the diagnostic messages, ordered in three different ways
20642 and collected in three separate
20643 sections. Section 1 contains the raw list of diagnostic messages. It
20644 corresponds to the output going to @file{stdout}. Section 2 contains
20645 messages ordered by rules.
20646 Section 3 contains messages ordered by source files.
20649 @node General gnatcheck Switches
20650 @section General @command{gnatcheck} Switches
20653 The following switches control the general @command{gnatcheck} behavior
20657 @cindex @option{^-a^/ALL^} (@command{gnatcheck})
20659 Process all units including those with read-only ALI files such as
20660 those from GNAT Run-Time library.
20664 @cindex @option{-d} (@command{gnatcheck})
20669 @cindex @option{-dd} (@command{gnatcheck})
20671 Progress indicator mode (for use in GPS)
20674 @cindex @option{^-h^/HELP^} (@command{gnatcheck})
20676 List the predefined and user-defined rules. For more details see
20677 @ref{Predefined Rules}.
20679 @cindex @option{^-l^/LOCS^} (@command{gnatcheck})
20681 Use full source locations references in the report file. For a construct from
20682 a generic instantiation a full source location is a chain from the location
20683 of this construct in the generic unit to the place where this unit is
20686 @cindex @option{^-m^/DIAGNOSTIC_LIMIT^} (@command{gnatcheck})
20687 @item ^-m@i{nnn}^/DIAGNOSTIC_LIMIT=@i{nnn}^
20688 Maximum number of diagnoses to be sent to Stdout, @i{nnn} from o@dots{}1000,
20689 the default value is 500. Zero means that there is no limitation on
20690 the number of diagnostic messages to be printed into Stdout.
20692 @cindex @option{^-q^/QUIET^} (@command{gnatcheck})
20694 Quiet mode. All the diagnoses about rule violations are placed in the
20695 @command{gnatcheck} report file only, without duplicating in @file{stdout}.
20697 @cindex @option{^-s^/SHORT^} (@command{gnatcheck})
20699 Short format of the report file (no version information, no list of applied
20700 rules, no list of checked sources is included)
20702 @cindex @option{^-s1^/COMPILER_STYLE^} (@command{gnatcheck})
20703 @item ^-s1^/COMPILER_STYLE^
20704 Include the compiler-style section in the report file
20706 @cindex @option{^-s2^/BY_RULES^} (@command{gnatcheck})
20707 @item ^-s2^/BY_RULES^
20708 Include the section containing diagnoses ordered by rules in the report file
20710 @cindex @option{^-s3^/BY_FILES_BY_RULES^} (@command{gnatcheck})
20711 @item ^-s3^/BY_FILES_BY_RULES^
20712 Include the section containing diagnoses ordered by files and then by rules
20715 @cindex @option{^-v^/VERBOSE^} (@command{gnatcheck})
20716 @item ^-v^/VERBOSE^
20717 Verbose mode; @command{gnatcheck} generates version information and then
20718 a trace of sources being processed.
20721 @cindex @option{^-o ^/OUTPUT^} (@command{gnatcheck})
20722 @item ^-o ^/OUTPUT=^@var{report_file}
20723 Set name of report file file to @var{report_file} .
20728 Note that if any of the options @option{^-s1^/COMPILER_STYLE^},
20729 @option{^-s2^/BY_RULES^} or
20730 @option{^-s3^/BY_FILES_BY_RULES^} is specified,
20731 then the @command{gnatcheck} report file will only contain sections
20732 explicitly denoted by these options.
20734 @node gnatcheck Rule Options
20735 @section @command{gnatcheck} Rule Options
20738 The following options control the processing performed by
20739 @command{gnatcheck}.
20742 @cindex @option{+ALL} (@command{gnatcheck})
20744 Turn all the rule checks ON.
20746 @cindex @option{-ALL} (@command{gnatcheck})
20748 Turn all the rule checks OFF.
20750 @cindex @option{+R} (@command{gnatcheck})
20751 @item +R@var{rule_id}@r{[}:@var{param}@r{]}
20752 Turn on the check for a specified rule with the specified parameter, if any.
20753 @var{rule_id} must be the identifier of one of the currently implemented rules
20754 (use @option{^-h^/HELP^} for the list of implemented rules). Rule identifiers
20755 are not case-sensitive. The @var{param} item must
20756 be a string representing a valid parameter(s) for the specified rule.
20757 If it contains any space characters then this string must be enclosed in
20760 @cindex @option{-R} (@command{gnatcheck})
20761 @item -R@var{rule_id}@r{[}:@var{param}@r{]}
20762 Turn off the check for a specified rule with the specified parameter, if any.
20764 @cindex @option{-from} (@command{gnatcheck})
20765 @item -from=@var{rule_option_filename}
20766 Read the rule options from the text file @var{rule_option_filename}, referred as
20767 ``rule file'' below.
20772 The default behavior is that all the rule checks are disabled.
20774 A rule file is a text file containing a set of rule options.
20775 @cindex Rule file (for @code{gnatcheck})
20776 The file may contain empty lines and Ada-style comments (comment
20777 lines and end-of-line comments). The rule file has free format; that is,
20778 you do not have to start a new rule option on a new line.
20780 A rule file may contain other @option{-from=@var{rule_option_filename}}
20781 options, each such option being replaced with the content of the
20782 corresponding rule file during the rule files processing. In case a
20783 cycle is detected (that is, @file{@var{rule_file_1}} reads rule options
20784 from @file{@var{rule_file_2}}, and @file{@var{rule_file_2}} reads
20785 (directly or indirectly) rule options from @file{@var{rule_file_1}}),
20786 the processing of rule files is interrupted and a part of their content
20790 @node Adding the Results of Compiler Checks to gnatcheck Output
20791 @section Adding the Results of Compiler Checks to @command{gnatcheck} Output
20794 The @command{gnatcheck} tool can include in the generated diagnostic messages
20796 the report file the results of the checks performed by the compiler. Though
20797 disabled by default, this effect may be obtained by using @option{+R} with
20798 the following rule identifiers and parameters:
20802 To record restrictions violations (that are performed by the compiler if the
20803 pragma @code{Restrictions} or @code{Restriction_Warnings} are given),
20805 @code{Restrictions} with the same parameters as pragma
20806 @code{Restrictions} or @code{Restriction_Warnings}.
20809 To record compiler style checks(@pxref{Style Checking}), use the rule named
20810 @code{Style_Checks}. A parameter of this rule can be either @code{All_Checks},
20811 which enables all the standard style checks that corresponds to @option{-gnatyy}
20812 GNAT style check option, or a string that has exactly the same
20813 structure and semantics as the @code{string_LITERAL} parameter of GNAT pragma
20814 @code{Style_Checks} (for further information about this pragma,
20815 @pxref{Pragma Style_Checks,,, gnat_rm, GNAT Reference Manual}).
20818 To record compiler warnings (@pxref{Warning Message Control}), use the rule
20819 named @code{Warnings} with a parameter that is a valid
20820 @i{static_string_expression} argument of GNAT pragma @code{Warnings}
20821 (for further information about this pragma, @pxref{Pragma Warnings,,,
20822 gnat_rm, GNAT Reference Manual}). Note, that in case of gnatcheck
20823 's' parameter, that corresponds to the GNAT @option{-gnatws} option, disables
20824 all the specific warnings, but not suppresses the warning mode,
20825 and 'e' parameter, corresponding to @option{-gnatwe} that means
20826 "treat warnings as errors", does not have any effect.
20830 To disable a specific restriction check, use @code{-RStyle_Checks} gnatcheck
20831 option with the corresponding restriction name as a parameter. @code{-R} is
20832 not available for @code{Style_Checks} and @code{Warnings} options, to disable
20833 warnings and style checks, use the corresponding warning and style options.
20835 @node Project-Wide Checks
20836 @section Project-Wide Checks
20837 @cindex Project-wide checks (for @command{gnatcheck})
20840 In order to perform checks on all units of a given project, you can use
20841 the GNAT driver along with the @option{-P} option:
20843 gnat check -Pproj -rules -from=my_rules
20847 If the project @code{proj} depends upon other projects, you can perform
20848 checks on the project closure using the @option{-U} option:
20850 gnat check -Pproj -U -rules -from=my_rules
20854 Finally, if not all the units are relevant to a particular main
20855 program in the project closure, you can perform checks for the set
20856 of units needed to create a given main program (unit closure) using
20857 the @option{-U} option followed by the name of the main unit:
20859 gnat check -Pproj -U main -rules -from=my_rules
20863 @node Predefined Rules
20864 @section Predefined Rules
20865 @cindex Predefined rules (for @command{gnatcheck})
20868 @c (Jan 2007) Since the global rules are still under development and are not
20869 @c documented, there is no point in explaining the difference between
20870 @c global and local rules
20872 A rule in @command{gnatcheck} is either local or global.
20873 A @emph{local rule} is a rule that applies to a well-defined section
20874 of a program and that can be checked by analyzing only this section.
20875 A @emph{global rule} requires analysis of some global properties of the
20876 whole program (mostly related to the program call graph).
20877 As of @value{NOW}, the implementation of global rules should be
20878 considered to be at a preliminary stage. You can use the
20879 @option{+GLOBAL} option to enable all the global rules, and the
20880 @option{-GLOBAL} rule option to disable all the global rules.
20882 All the global rules in the list below are
20883 so indicated by marking them ``GLOBAL''.
20884 This +GLOBAL and -GLOBAL options are not
20885 included in the list of gnatcheck options above, because at the moment they
20886 are considered as a temporary debug options.
20888 @command{gnatcheck} performs rule checks for generic
20889 instances only for global rules. This limitation may be relaxed in a later
20894 The following subsections document the rules implemented in
20895 @command{gnatcheck}.
20896 The subsection title is the same as the rule identifier, which may be
20897 used as a parameter of the @option{+R} or @option{-R} options.
20901 * Abstract_Type_Declarations::
20902 * Anonymous_Arrays::
20903 * Anonymous_Subtypes::
20905 * Boolean_Relational_Operators::
20907 * Ceiling_Violations::
20909 * Controlled_Type_Declarations::
20910 * Declarations_In_Blocks::
20911 * Default_Parameters::
20912 * Discriminated_Records::
20913 * Enumeration_Ranges_In_CASE_Statements::
20914 * Exceptions_As_Control_Flow::
20915 * Exits_From_Conditional_Loops::
20916 * EXIT_Statements_With_No_Loop_Name::
20917 * Expanded_Loop_Exit_Names::
20918 * Explicit_Full_Discrete_Ranges::
20919 * Float_Equality_Checks::
20920 * Forbidden_Pragmas::
20921 * Function_Style_Procedures::
20922 * Generics_In_Subprograms::
20923 * GOTO_Statements::
20924 * Implicit_IN_Mode_Parameters::
20925 * Implicit_SMALL_For_Fixed_Point_Types::
20926 * Improperly_Located_Instantiations::
20927 * Improper_Returns::
20928 * Library_Level_Subprograms::
20931 * Improperly_Called_Protected_Entries::
20934 * Misnamed_Identifiers::
20935 * Multiple_Entries_In_Protected_Definitions::
20937 * Non_Qualified_Aggregates::
20938 * Non_Short_Circuit_Operators::
20939 * Non_SPARK_Attributes::
20940 * Non_Tagged_Derived_Types::
20941 * Non_Visible_Exceptions::
20942 * Numeric_Literals::
20943 * OTHERS_In_Aggregates::
20944 * OTHERS_In_CASE_Statements::
20945 * OTHERS_In_Exception_Handlers::
20946 * Outer_Loop_Exits::
20947 * Overloaded_Operators::
20948 * Overly_Nested_Control_Structures::
20949 * Parameters_Out_Of_Order::
20950 * Positional_Actuals_For_Defaulted_Generic_Parameters::
20951 * Positional_Actuals_For_Defaulted_Parameters::
20952 * Positional_Components::
20953 * Positional_Generic_Parameters::
20954 * Positional_Parameters::
20955 * Predefined_Numeric_Types::
20956 * Raising_External_Exceptions::
20957 * Raising_Predefined_Exceptions::
20958 * Separate_Numeric_Error_Handlers::
20961 * Side_Effect_Functions::
20964 * Unassigned_OUT_Parameters::
20965 * Uncommented_BEGIN_In_Package_Bodies::
20966 * Unconditional_Exits::
20967 * Unconstrained_Array_Returns::
20968 * Universal_Ranges::
20969 * Unnamed_Blocks_And_Loops::
20971 * Unused_Subprograms::
20973 * USE_PACKAGE_Clauses::
20974 * Volatile_Objects_Without_Address_Clauses::
20978 @node Abstract_Type_Declarations
20979 @subsection @code{Abstract_Type_Declarations}
20980 @cindex @code{Abstract_Type_Declarations} rule (for @command{gnatcheck})
20983 Flag all declarations of abstract types. For an abstract private
20984 type, both the private and full type declarations are flagged.
20986 This rule has no parameters.
20989 @node Anonymous_Arrays
20990 @subsection @code{Anonymous_Arrays}
20991 @cindex @code{Anonymous_Arrays} rule (for @command{gnatcheck})
20994 Flag all anonymous array type definitions (by Ada semantics these can only
20995 occur in object declarations).
20997 This rule has no parameters.
20999 @node Anonymous_Subtypes
21000 @subsection @code{Anonymous_Subtypes}
21001 @cindex @code{Anonymous_Subtypes} rule (for @command{gnatcheck})
21004 Flag all uses of anonymous subtypes. A use of an anonymous subtype is
21005 any instance of a subtype indication with a constraint, other than one
21006 that occurs immediately within a subtype declaration. Any use of a range
21007 other than as a constraint used immediately within a subtype declaration
21008 is considered as an anonymous subtype.
21010 An effect of this rule is that @code{for} loops such as the following are
21011 flagged (since @code{1..N} is formally a ``range''):
21013 @smallexample @c ada
21014 for I in 1 .. N loop
21020 Declaring an explicit subtype solves the problem:
21022 @smallexample @c ada
21023 subtype S is Integer range 1..N;
21031 This rule has no parameters.
21034 @subsection @code{Blocks}
21035 @cindex @code{Blocks} rule (for @command{gnatcheck})
21038 Flag each block statement.
21040 This rule has no parameters.
21042 @node Boolean_Relational_Operators
21043 @subsection @code{Boolean_Relational_Operators}
21044 @cindex @code{Boolean_Relational_Operators} rule (for @command{gnatcheck})
21047 Flag each call to a predefined relational operator (``<'', ``>'', ``<='',
21048 ``>='', ``='' and ``/='') for the predefined Boolean type.
21049 (This rule is useful in enforcing the SPARK language restrictions.)
21051 Calls to predefined relational operators of any type derived from
21052 @code{Standard.Boolean} are not detected. Calls to user-defined functions
21053 with these designators, and uses of operators that are renamings
21054 of the predefined relational operators for @code{Standard.Boolean},
21055 are likewise not detected.
21057 This rule has no parameters.
21060 @node Ceiling_Violations
21061 @subsection @code{Ceiling_Violations} (under construction, GLOBAL)
21062 @cindex @code{Ceiling_Violations} rule (for @command{gnatcheck})
21065 Flag invocations of a protected operation by a task whose priority exceeds
21066 the protected object's ceiling.
21068 As of @value{NOW}, this rule has the following limitations:
21073 We consider only pragmas Priority and Interrupt_Priority as means to define
21074 a task/protected operation priority. We do not consider the effect of using
21075 Ada.Dynamic_Priorities.Set_Priority procedure;
21078 We consider only base task priorities, and no priority inheritance. That is,
21079 we do not make a difference between calls issued during task activation and
21080 execution of the sequence of statements from task body;
21083 Any situation when the priority of protected operation caller is set by a
21084 dynamic expression (that is, the corresponding Priority or
21085 Interrupt_Priority pragma has a non-static expression as an argument) we
21086 treat as a priority inconsistency (and, therefore, detect this situation).
21090 At the moment the notion of the main subprogram is not implemented in
21091 gnatcheck, so any pragma Priority in a library level subprogram body (in case
21092 if this subprogram can be a main subprogram of a partition) changes the
21093 priority of an environment task. So if we have more then one such pragma in
21094 the set of processed sources, the pragma that is processed last, defines the
21095 priority of an environment task.
21097 This rule has no parameters.
21100 @node Controlled_Type_Declarations
21101 @subsection @code{Controlled_Type_Declarations}
21102 @cindex @code{Controlled_Type_Declarations} rule (for @command{gnatcheck})
21105 Flag all declarations of controlled types. A declaration of a private type
21106 is flagged if its full declaration declares a controlled type. A declaration
21107 of a derived type is flagged if its ancestor type is controlled. Subtype
21108 declarations are not checked. A declaration of a type that itself is not a
21109 descendant of a type declared in @code{Ada.Finalization} but has a controlled
21110 component is not checked.
21112 This rule has no parameters.
21116 @node Declarations_In_Blocks
21117 @subsection @code{Declarations_In_Blocks}
21118 @cindex @code{Declarations_In_Blocks} rule (for @command{gnatcheck})
21121 Flag all block statements containing local declarations. A @code{declare}
21122 block with an empty @i{declarative_part} or with a @i{declarative part}
21123 containing only pragmas and/or @code{use} clauses is not flagged.
21125 This rule has no parameters.
21128 @node Default_Parameters
21129 @subsection @code{Default_Parameters}
21130 @cindex @code{Default_Parameters} rule (for @command{gnatcheck})
21133 Flag all default expressions for subprogram parameters. Parameter
21134 declarations of formal and generic subprograms are also checked.
21136 This rule has no parameters.
21139 @node Discriminated_Records
21140 @subsection @code{Discriminated_Records}
21141 @cindex @code{Discriminated_Records} rule (for @command{gnatcheck})
21144 Flag all declarations of record types with discriminants. Only the
21145 declarations of record and record extension types are checked. Incomplete,
21146 formal, private, derived and private extension type declarations are not
21147 checked. Task and protected type declarations also are not checked.
21149 This rule has no parameters.
21152 @node Enumeration_Ranges_In_CASE_Statements
21153 @subsection @code{Enumeration_Ranges_In_CASE_Statements}
21154 @cindex @code{Enumeration_Ranges_In_CASE_Statements} (for @command{gnatcheck})
21157 Flag each use of a range of enumeration literals as a choice in a
21158 @code{case} statement.
21159 All forms for specifying a range (explicit ranges
21160 such as @code{A .. B}, subtype marks and @code{'Range} attributes) are flagged.
21161 An enumeration range is
21162 flagged even if contains exactly one enumeration value or no values at all. A
21163 type derived from an enumeration type is considered as an enumeration type.
21165 This rule helps prevent maintenance problems arising from adding an
21166 enumeration value to a type and having it implicitly handled by an existing
21167 @code{case} statement with an enumeration range that includes the new literal.
21169 This rule has no parameters.
21172 @node Exceptions_As_Control_Flow
21173 @subsection @code{Exceptions_As_Control_Flow}
21174 @cindex @code{Exceptions_As_Control_Flow} (for @command{gnatcheck})
21177 Flag each place where an exception is explicitly raised and handled in the
21178 same subprogram body. A @code{raise} statement in an exception handler,
21179 package body, task body or entry body is not flagged.
21181 The rule has no parameters.
21183 @node Exits_From_Conditional_Loops
21184 @subsection @code{Exits_From_Conditional_Loops}
21185 @cindex @code{Exits_From_Conditional_Loops} (for @command{gnatcheck})
21188 Flag any exit statement if it transfers the control out of a @code{for} loop
21189 or a @code{while} loop. This includes cases when the @code{exit} statement
21190 applies to a @code{FOR} or @code{while} loop, and cases when it is enclosed
21191 in some @code{for} or @code{while} loop, but transfers the control from some
21192 outer (inconditional) @code{loop} statement.
21194 The rule has no parameters.
21197 @node EXIT_Statements_With_No_Loop_Name
21198 @subsection @code{EXIT_Statements_With_No_Loop_Name}
21199 @cindex @code{EXIT_Statements_With_No_Loop_Name} (for @command{gnatcheck})
21202 Flag each @code{exit} statement that does not specify the name of the loop
21205 The rule has no parameters.
21208 @node Expanded_Loop_Exit_Names
21209 @subsection @code{Expanded_Loop_Exit_Names}
21210 @cindex @code{Expanded_Loop_Exit_Names} rule (for @command{gnatcheck})
21213 Flag all expanded loop names in @code{exit} statements.
21215 This rule has no parameters.
21217 @node Explicit_Full_Discrete_Ranges
21218 @subsection @code{Explicit_Full_Discrete_Ranges}
21219 @cindex @code{Explicit_Full_Discrete_Ranges} rule (for @command{gnatcheck})
21222 Flag each discrete range that has the form @code{A'First .. A'Last}.
21224 This rule has no parameters.
21226 @node Float_Equality_Checks
21227 @subsection @code{Float_Equality_Checks}
21228 @cindex @code{Float_Equality_Checks} rule (for @command{gnatcheck})
21231 Flag all calls to the predefined equality operations for floating-point types.
21232 Both ``@code{=}'' and ``@code{/=}'' operations are checked.
21233 User-defined equality operations are not flagged, nor are ``@code{=}''
21234 and ``@code{/=}'' operations for fixed-point types.
21236 This rule has no parameters.
21239 @node Forbidden_Pragmas
21240 @subsection @code{Forbidden_Pragmas}
21241 @cindex @code{Forbidden_Pragmas} rule (for @command{gnatcheck})
21244 Flag each use of the specified pragmas. The pragmas to be detected
21245 are named in the rule's parameters.
21247 This rule has the following parameters:
21250 @item For the @option{+R} option
21253 @item @emph{Pragma_Name}
21254 Adds the specified pragma to the set of pragmas to be
21255 checked and sets the checks for all the specified pragmas
21256 ON. @emph{Pragma_Name} is treated as a name of a pragma. If it
21257 does not correspond to any pragma name defined in the Ada
21258 standard or to the name of a GNAT-specific pragma defined
21259 in @ref{Implementation Defined Pragmas,,, gnat_rm, GNAT Reference
21260 Manual}, it is treated as the name of unknown pragma.
21263 All the GNAT-specific pragmas are detected; this sets
21264 the checks for all the specified pragmas ON.
21267 All pragmas are detected; this sets the rule ON.
21270 @item For the @option{-R} option
21272 @item @emph{Pragma_Name}
21273 Removes the specified pragma from the set of pragmas to be
21274 checked without affecting checks for
21275 other pragmas. @emph{Pragma_Name} is treated as a name
21276 of a pragma. If it does not correspond to any pragma
21277 defined in the Ada standard or to any name defined in
21278 @ref{Implementation Defined Pragmas,,, gnat_rm, GNAT Reference Manual},
21279 this option is treated as turning OFF detection of all unknown pragmas.
21282 Turn OFF detection of all GNAT-specific pragmas
21285 Clear the list of the pragmas to be detected and
21291 Parameters are not case sensitive. If @emph{Pragma_Name} does not have
21292 the syntax of an Ada identifier and therefore can not be considered
21293 as a pragma name, a diagnostic message is generated and the corresponding
21294 parameter is ignored.
21296 When more then one parameter is given in the same rule option, the parameters
21297 must be separated by a comma.
21299 If more then one option for this rule is specified for the @command{gnatcheck}
21300 call, a new option overrides the previous one(s).
21302 The @option{+R} option with no parameters turns the rule ON with the set of
21303 pragmas to be detected defined by the previous rule options.
21304 (By default this set is empty, so if the only option specified for the rule is
21305 @option{+RForbidden_Pragmas} (with
21306 no parameter), then the rule is enabled, but it does not detect anything).
21307 The @option{-R} option with no parameter turns the rule OFF, but it does not
21308 affect the set of pragmas to be detected.
21313 @node Function_Style_Procedures
21314 @subsection @code{Function_Style_Procedures}
21315 @cindex @code{Function_Style_Procedures} rule (for @command{gnatcheck})
21318 Flag each procedure that can be rewritten as a function. A procedure can be
21319 converted into a function if it has exactly one parameter of mode @code{out}
21320 and no parameters of mode @code{in out}. Procedure declarations,
21321 formal procedure declarations, and generic procedure declarations are always
21323 bodies and body stubs are flagged only if they do not have corresponding
21324 separate declarations. Procedure renamings and procedure instantiations are
21327 If a procedure can be rewritten as a function, but its @code{out} parameter is
21328 of a limited type, it is not flagged.
21330 Protected procedures are not flagged. Null procedures also are not flagged.
21332 This rule has no parameters.
21335 @node Generics_In_Subprograms
21336 @subsection @code{Generics_In_Subprograms}
21337 @cindex @code{Generics_In_Subprograms} rule (for @command{gnatcheck})
21340 Flag each declaration of a generic unit in a subprogram. Generic
21341 declarations in the bodies of generic subprograms are also flagged.
21342 A generic unit nested in another generic unit is not flagged.
21343 If a generic unit is
21344 declared in a local package that is declared in a subprogram body, the
21345 generic unit is flagged.
21347 This rule has no parameters.
21350 @node GOTO_Statements
21351 @subsection @code{GOTO_Statements}
21352 @cindex @code{GOTO_Statements} rule (for @command{gnatcheck})
21355 Flag each occurrence of a @code{goto} statement.
21357 This rule has no parameters.
21360 @node Implicit_IN_Mode_Parameters
21361 @subsection @code{Implicit_IN_Mode_Parameters}
21362 @cindex @code{Implicit_IN_Mode_Parameters} rule (for @command{gnatcheck})
21365 Flag each occurrence of a formal parameter with an implicit @code{in} mode.
21366 Note that @code{access} parameters, although they technically behave
21367 like @code{in} parameters, are not flagged.
21369 This rule has no parameters.
21372 @node Implicit_SMALL_For_Fixed_Point_Types
21373 @subsection @code{Implicit_SMALL_For_Fixed_Point_Types}
21374 @cindex @code{Implicit_SMALL_For_Fixed_Point_Types} rule (for @command{gnatcheck})
21377 Flag each fixed point type declaration that lacks an explicit
21378 representation clause to define its @code{'Small} value.
21379 Since @code{'Small} can be defined only for ordinary fixed point types,
21380 decimal fixed point type declarations are not checked.
21382 This rule has no parameters.
21385 @node Improperly_Located_Instantiations
21386 @subsection @code{Improperly_Located_Instantiations}
21387 @cindex @code{Improperly_Located_Instantiations} rule (for @command{gnatcheck})
21390 Flag all generic instantiations in library-level package specs
21391 (including library generic packages) and in all subprogram bodies.
21393 Instantiations in task and entry bodies are not flagged. Instantiations in the
21394 bodies of protected subprograms are flagged.
21396 This rule has no parameters.
21400 @node Improper_Returns
21401 @subsection @code{Improper_Returns}
21402 @cindex @code{Improper_Returns} rule (for @command{gnatcheck})
21405 Flag each explicit @code{return} statement in procedures, and
21406 multiple @code{return} statements in functions.
21407 Diagnostic messages are generated for all @code{return} statements
21408 in a procedure (thus each procedure must be written so that it
21409 returns implicitly at the end of its statement part),
21410 and for all @code{return} statements in a function after the first one.
21411 This rule supports the stylistic convention that each subprogram
21412 should have no more than one point of normal return.
21414 This rule has no parameters.
21417 @node Library_Level_Subprograms
21418 @subsection @code{Library_Level_Subprograms}
21419 @cindex @code{Library_Level_Subprograms} rule (for @command{gnatcheck})
21422 Flag all library-level subprograms (including generic subprogram instantiations).
21424 This rule has no parameters.
21427 @node Local_Packages
21428 @subsection @code{Local_Packages}
21429 @cindex @code{Local_Packages} rule (for @command{gnatcheck})
21432 Flag all local packages declared in package and generic package
21434 Local packages in bodies are not flagged.
21436 This rule has no parameters.
21439 @node Improperly_Called_Protected_Entries
21440 @subsection @code{Improperly_Called_Protected_Entries} (under construction, GLOBAL)
21441 @cindex @code{Improperly_Called_Protected_Entries} rule (for @command{gnatcheck})
21444 Flag each protected entry that can be called from more than one task.
21446 This rule has no parameters.
21450 @subsection @code{Metrics}
21451 @cindex @code{Metrics} rule (for @command{gnatcheck})
21454 There is a set of checks based on computing a metric value and comparing the
21455 result with the specified upper (or lower, depending on a specific metric)
21456 value specified for a given metric. A construct is flagged if a given metric
21457 is applicable (can be computed) for it and the computed value is greater
21458 then (lover then) the specified upper (lower) bound.
21460 The name of any metric-based rule consists of the prefix @code{Metrics_}
21461 followed by the name of the corresponding metric (see the table below).
21462 For @option{+R} option, each metric-based rule has a numeric parameter
21463 specifying the bound (integer or real, depending on a metric), @option{-R}
21464 option for metric rules does not have a parameter.
21466 The following table shows the metric names for that the corresponding
21467 metrics-based checks are supported by gnatcheck, including the
21468 constraint that must be satisfied by the bound that is specified for the check
21469 and what bound - upper (U) or lower (L) - should be specified.
21471 @multitable {@code{Cyclomatic_Complexity}}{Cyclomatic complexity}{Positive integer}
21473 @headitem Check Name @tab Description @tab Bounds Value
21476 @item @b{Check Name} @tab @b{Description} @tab @b{Bounds Value}
21478 @c Above conditional code is workaround to bug in texi2html (Feb 2008)
21479 @item @code{Essential_Complexity} @tab Essential complexity @tab Positive integer (U)
21480 @item @code{Cyclomatic_Complexity} @tab Cyclomatic complexity @tab Positive integer (U)
21481 @item @code{LSLOC} @tab Logical Source Lines of Code @tab Positive integer (U)
21485 The meaning and the computed values for all these metrics are exactly
21486 the same as for the corresponding metrics in @command{gnatmetric}.
21488 @emph{Example:} the rule
21490 +RMetrics_Cyclomatic_Complexity : 7
21493 means that all bodies with cyclomatic complexity exceeding 7 will be flagged.
21495 To turn OFF the check for cyclomatic complexity metric, use the following option:
21497 -RMetrics_Cyclomatic_Complexity
21500 @node Misnamed_Identifiers
21501 @subsection @code{Misnamed_Identifiers}
21502 @cindex @code{Misnamed_Identifiers} rule (for @command{gnatcheck})
21505 Flag the declaration of each identifier that does not have a suffix
21506 corresponding to the kind of entity being declared.
21507 The following declarations are checked:
21514 constant declarations (but not number declarations)
21517 package renaming declarations (but not generic package renaming
21522 This rule may have parameters. When used without parameters, the rule enforces
21523 the following checks:
21527 type-defining names end with @code{_T}, unless the type is an access type,
21528 in which case the suffix must be @code{_A}
21530 constant names end with @code{_C}
21532 names defining package renamings end with @code{_R}
21536 For a private or incomplete type declaration the following checks are
21537 made for the defining name suffix:
21541 For an incomplete type declaration: if the corresponding full type
21542 declaration is available, the defining identifier from the full type
21543 declaration is checked, but the defining identifier from the incomplete type
21544 declaration is not; otherwise the defining identifier from the incomplete
21545 type declaration is checked against the suffix specified for type
21549 For a private type declaration (including private extensions), the defining
21550 identifier from the private type declaration is checked against the type
21551 suffix (even if the corresponding full declaration is an access type
21552 declaration), and the defining identifier from the corresponding full type
21553 declaration is not checked.
21557 For a deferred constant, the defining name in the corresponding full constant
21558 declaration is not checked.
21560 Defining names of formal types are not checked.
21562 The rule may have the following parameters:
21566 For the @option{+R} option:
21569 Sets the default listed above for all the names to be checked.
21571 @item Type_Suffix=@emph{string}
21572 Specifies the suffix for a type name.
21574 @item Access_Suffix=@emph{string}
21575 Specifies the suffix for an access type name. If
21576 this parameter is set, it overrides for access
21577 types the suffix set by the @code{Type_Suffix} parameter.
21578 For access types, @emph{string} may have the following format:
21579 @emph{suffix1(suffix2)}. That means that an access type name
21580 should have the @emph{suffix1} suffix except for the case when
21581 the designated type is also an access type, in this case the
21582 type name should have the @emph{suffix1 & suffix2} suffix.
21584 @item Constant_Suffix=@emph{string}
21585 Specifies the suffix for a constant name.
21587 @item Renaming_Suffix=@emph{string}
21588 Specifies the suffix for a package renaming name.
21592 For the @option{-R} option:
21595 Remove all the suffixes specified for the
21596 identifier suffix checks, whether by default or
21597 as specified by other rule parameters. All the
21598 checks for this rule are disabled as a result.
21601 Removes the suffix specified for types. This
21602 disables checks for types but does not disable
21603 any other checks for this rule (including the
21604 check for access type names if @code{Access_Suffix} is
21607 @item Access_Suffix
21608 Removes the suffix specified for access types.
21609 This disables checks for access type names but
21610 does not disable any other checks for this rule.
21611 If @code{Type_Suffix} is set, access type names are
21612 checked as ordinary type names.
21614 @item Constant_Suffix
21615 Removes the suffix specified for constants. This
21616 disables checks for constant names but does not
21617 disable any other checks for this rule.
21619 @item Renaming_Suffix
21620 Removes the suffix specified for package
21621 renamings. This disables checks for package
21622 renamings but does not disable any other checks
21628 If more than one parameter is used, parameters must be separated by commas.
21630 If more than one option is specified for the @command{gnatcheck} invocation,
21631 a new option overrides the previous one(s).
21633 The @option{+RMisnamed_Identifiers} option (with no parameter) enables
21635 name suffixes specified by previous options used for this rule.
21637 The @option{-RMisnamed_Identifiers} option (with no parameter) disables
21638 all the checks but keeps
21639 all the suffixes specified by previous options used for this rule.
21641 The @emph{string} value must be a valid suffix for an Ada identifier (after
21642 trimming all the leading and trailing space characters, if any).
21643 Parameters are not case sensitive, except the @emph{string} part.
21645 If any error is detected in a rule parameter, the parameter is ignored.
21646 In such a case the options that are set for the rule are not
21651 @node Multiple_Entries_In_Protected_Definitions
21652 @subsection @code{Multiple_Entries_In_Protected_Definitions}
21653 @cindex @code{Multiple_Entries_In_Protected_Definitions} rule (for @command{gnatcheck})
21656 Flag each protected definition (i.e., each protected object/type declaration)
21657 that defines more than one entry.
21658 Diagnostic messages are generated for all the entry declarations
21659 except the first one. An entry family is counted as one entry. Entries from
21660 the private part of the protected definition are also checked.
21662 This rule has no parameters.
21665 @subsection @code{Name_Clashes}
21666 @cindex @code{Name_Clashes} rule (for @command{gnatcheck})
21669 Check that certain names are not used as defining identifiers. To activate
21670 this rule, you need to supply a reference to the dictionary file(s) as a rule
21671 parameter(s) (more then one dictionary file can be specified). If no
21672 dictionary file is set, this rule will not cause anything to be flagged.
21673 Only defining occurrences, not references, are checked.
21674 The check is not case-sensitive.
21676 This rule is enabled by default, but without setting any corresponding
21677 dictionary file(s); thus the default effect is to do no checks.
21679 A dictionary file is a plain text file. The maximum line length for this file
21680 is 1024 characters. If the line is longer then this limit, extra characters
21683 Each line can be either an empty line, a comment line, or a line containing
21684 a list of identifiers separated by space or HT characters.
21685 A comment is an Ada-style comment (from @code{--} to end-of-line).
21686 Identifiers must follow the Ada syntax for identifiers.
21687 A line containing one or more identifiers may end with a comment.
21689 @node Non_Qualified_Aggregates
21690 @subsection @code{Non_Qualified_Aggregates}
21691 @cindex @code{Non_Qualified_Aggregates} rule (for @command{gnatcheck})
21694 Flag each non-qualified aggregate.
21695 A non-qualified aggregate is an
21696 aggregate that is not the expression of a qualified expression. A
21697 string literal is not considered an aggregate, but an array
21698 aggregate of a string type is considered as a normal aggregate.
21699 Aggregates of anonymous array types are not flagged.
21701 This rule has no parameters.
21704 @node Non_Short_Circuit_Operators
21705 @subsection @code{Non_Short_Circuit_Operators}
21706 @cindex @code{Non_Short_Circuit_Operators} rule (for @command{gnatcheck})
21709 Flag all calls to predefined @code{and} and @code{or} operators for
21710 any boolean type. Calls to
21711 user-defined @code{and} and @code{or} and to operators defined by renaming
21712 declarations are not flagged. Calls to predefined @code{and} and @code{or}
21713 operators for modular types or boolean array types are not flagged.
21715 This rule has no parameters.
21719 @node Non_SPARK_Attributes
21720 @subsection @code{Non_SPARK_Attributes}
21721 @cindex @code{Non_SPARK_Attributes} rule (for @command{gnatcheck})
21724 The SPARK language defines the following subset of Ada 95 attribute
21725 designators as those that can be used in SPARK programs. The use of
21726 any other attribute is flagged.
21729 @item @code{'Adjacent}
21732 @item @code{'Ceiling}
21733 @item @code{'Component_Size}
21734 @item @code{'Compose}
21735 @item @code{'Copy_Sign}
21736 @item @code{'Delta}
21737 @item @code{'Denorm}
21738 @item @code{'Digits}
21739 @item @code{'Exponent}
21740 @item @code{'First}
21741 @item @code{'Floor}
21743 @item @code{'Fraction}
21745 @item @code{'Leading_Part}
21746 @item @code{'Length}
21747 @item @code{'Machine}
21748 @item @code{'Machine_Emax}
21749 @item @code{'Machine_Emin}
21750 @item @code{'Machine_Mantissa}
21751 @item @code{'Machine_Overflows}
21752 @item @code{'Machine_Radix}
21753 @item @code{'Machine_Rounds}
21756 @item @code{'Model}
21757 @item @code{'Model_Emin}
21758 @item @code{'Model_Epsilon}
21759 @item @code{'Model_Mantissa}
21760 @item @code{'Model_Small}
21761 @item @code{'Modulus}
21764 @item @code{'Range}
21765 @item @code{'Remainder}
21766 @item @code{'Rounding}
21767 @item @code{'Safe_First}
21768 @item @code{'Safe_Last}
21769 @item @code{'Scaling}
21770 @item @code{'Signed_Zeros}
21772 @item @code{'Small}
21774 @item @code{'Truncation}
21775 @item @code{'Unbiased_Rounding}
21777 @item @code{'Valid}
21781 This rule has no parameters.
21784 @node Non_Tagged_Derived_Types
21785 @subsection @code{Non_Tagged_Derived_Types}
21786 @cindex @code{Non_Tagged_Derived_Types} rule (for @command{gnatcheck})
21789 Flag all derived type declarations that do not have a record extension part.
21791 This rule has no parameters.
21795 @node Non_Visible_Exceptions
21796 @subsection @code{Non_Visible_Exceptions}
21797 @cindex @code{Non_Visible_Exceptions} rule (for @command{gnatcheck})
21800 Flag constructs leading to the possibility of propagating an exception
21801 out of the scope in which the exception is declared.
21802 Two cases are detected:
21806 An exception declaration in a subprogram body, task body or block
21807 statement is flagged if the body or statement does not contain a handler for
21808 that exception or a handler with an @code{others} choice.
21811 A @code{raise} statement in an exception handler of a subprogram body,
21812 task body or block statement is flagged if it (re)raises a locally
21813 declared exception. This may occur under the following circumstances:
21816 it explicitly raises a locally declared exception, or
21818 it does not specify an exception name (i.e., it is simply @code{raise;})
21819 and the enclosing handler contains a locally declared exception in its
21825 Renamings of local exceptions are not flagged.
21827 This rule has no parameters.
21830 @node Numeric_Literals
21831 @subsection @code{Numeric_Literals}
21832 @cindex @code{Numeric_Literals} rule (for @command{gnatcheck})
21835 Flag each use of a numeric literal in an index expression, and in any
21836 circumstance except for the following:
21840 a literal occurring in the initialization expression for a constant
21841 declaration or a named number declaration, or
21844 an integer literal that is less than or equal to a value
21845 specified by the @option{N} rule parameter.
21849 This rule may have the following parameters for the @option{+R} option:
21853 @emph{N} is an integer literal used as the maximal value that is not flagged
21854 (i.e., integer literals not exceeding this value are allowed)
21857 All integer literals are flagged
21861 If no parameters are set, the maximum unflagged value is 1.
21863 The last specified check limit (or the fact that there is no limit at
21864 all) is used when multiple @option{+R} options appear.
21866 The @option{-R} option for this rule has no parameters.
21867 It disables the rule but retains the last specified maximum unflagged value.
21868 If the @option{+R} option subsequently appears, this value is used as the
21869 threshold for the check.
21872 @node OTHERS_In_Aggregates
21873 @subsection @code{OTHERS_In_Aggregates}
21874 @cindex @code{OTHERS_In_Aggregates} rule (for @command{gnatcheck})
21877 Flag each use of an @code{others} choice in extension aggregates.
21878 In record and array aggregates, an @code{others} choice is flagged unless
21879 it is used to refer to all components, or to all but one component.
21881 If, in case of a named array aggregate, there are two associations, one
21882 with an @code{others} choice and another with a discrete range, the
21883 @code{others} choice is flagged even if the discrete range specifies
21884 exactly one component; for example, @code{(1..1 => 0, others => 1)}.
21886 This rule has no parameters.
21888 @node OTHERS_In_CASE_Statements
21889 @subsection @code{OTHERS_In_CASE_Statements}
21890 @cindex @code{OTHERS_In_CASE_Statements} rule (for @command{gnatcheck})
21893 Flag any use of an @code{others} choice in a @code{case} statement.
21895 This rule has no parameters.
21897 @node OTHERS_In_Exception_Handlers
21898 @subsection @code{OTHERS_In_Exception_Handlers}
21899 @cindex @code{OTHERS_In_Exception_Handlers} rule (for @command{gnatcheck})
21902 Flag any use of an @code{others} choice in an exception handler.
21904 This rule has no parameters.
21907 @node Outer_Loop_Exits
21908 @subsection @code{Outer_Loop_Exits}
21909 @cindex @code{Outer_Loop_Exits} rule (for @command{gnatcheck})
21912 Flag each @code{exit} statement containing a loop name that is not the name
21913 of the immediately enclosing @code{loop} statement.
21915 This rule has no parameters.
21918 @node Overloaded_Operators
21919 @subsection @code{Overloaded_Operators}
21920 @cindex @code{Overloaded_Operators} rule (for @command{gnatcheck})
21923 Flag each function declaration that overloads an operator symbol.
21924 A function body is checked only if the body does not have a
21925 separate spec. Formal functions are also checked. For a
21926 renaming declaration, only renaming-as-declaration is checked
21928 This rule has no parameters.
21931 @node Overly_Nested_Control_Structures
21932 @subsection @code{Overly_Nested_Control_Structures}
21933 @cindex @code{Overly_Nested_Control_Structures} rule (for @command{gnatcheck})
21936 Flag each control structure whose nesting level exceeds the value provided
21937 in the rule parameter.
21939 The control structures checked are the following:
21942 @item @code{if} statement
21943 @item @code{case} statement
21944 @item @code{loop} statement
21945 @item Selective accept statement
21946 @item Timed entry call statement
21947 @item Conditional entry call
21948 @item Asynchronous select statement
21952 The rule has the following parameter for the @option{+R} option:
21956 Positive integer specifying the maximal control structure nesting
21957 level that is not flagged
21961 If the parameter for the @option{+R} option is not specified or
21962 if it is not a positive integer, @option{+R} option is ignored.
21964 If more then one option is specified for the gnatcheck call, the later option and
21965 new parameter override the previous one(s).
21968 @node Parameters_Out_Of_Order
21969 @subsection @code{Parameters_Out_Of_Order}
21970 @cindex @code{Parameters_Out_Of_Order} rule (for @command{gnatcheck})
21973 Flag each subprogram and entry declaration whose formal parameters are not
21974 ordered according to the following scheme:
21978 @item @code{in} and @code{access} parameters first,
21979 then @code{in out} parameters,
21980 and then @code{out} parameters;
21982 @item for @code{in} mode, parameters with default initialization expressions
21987 Only the first violation of the described order is flagged.
21989 The following constructs are checked:
21992 @item subprogram declarations (including null procedures);
21993 @item generic subprogram declarations;
21994 @item formal subprogram declarations;
21995 @item entry declarations;
21996 @item subprogram bodies and subprogram body stubs that do not
21997 have separate specifications
22001 Subprogram renamings are not checked.
22003 This rule has no parameters.
22006 @node Positional_Actuals_For_Defaulted_Generic_Parameters
22007 @subsection @code{Positional_Actuals_For_Defaulted_Generic_Parameters}
22008 @cindex @code{Positional_Actuals_For_Defaulted_Generic_Parameters} rule (for @command{gnatcheck})
22011 Flag each generic actual parameter corresponding to a generic formal
22012 parameter with a default initialization, if positional notation is used.
22014 This rule has no parameters.
22016 @node Positional_Actuals_For_Defaulted_Parameters
22017 @subsection @code{Positional_Actuals_For_Defaulted_Parameters}
22018 @cindex @code{Positional_Actuals_For_Defaulted_Parameters} rule (for @command{gnatcheck})
22021 Flag each actual parameter to a subprogram or entry call where the
22022 corresponding formal parameter has a default expression, if positional
22025 This rule has no parameters.
22027 @node Positional_Components
22028 @subsection @code{Positional_Components}
22029 @cindex @code{Positional_Components} rule (for @command{gnatcheck})
22032 Flag each array, record and extension aggregate that includes positional
22035 This rule has no parameters.
22038 @node Positional_Generic_Parameters
22039 @subsection @code{Positional_Generic_Parameters}
22040 @cindex @code{Positional_Generic_Parameters} rule (for @command{gnatcheck})
22043 Flag each instantiation using positional parameter notation.
22045 This rule has no parameters.
22048 @node Positional_Parameters
22049 @subsection @code{Positional_Parameters}
22050 @cindex @code{Positional_Parameters} rule (for @command{gnatcheck})
22053 Flag each subprogram or entry call using positional parameter notation,
22054 except for the following:
22058 Invocations of prefix or infix operators are not flagged
22060 If the called subprogram or entry has only one formal parameter,
22061 the call is not flagged;
22063 If a subprogram call uses the @emph{Object.Operation} notation, then
22066 the first parameter (that is, @emph{Object}) is not flagged;
22068 if the called subprogram has only two parameters, the second parameter
22069 of the call is not flagged;
22074 This rule has no parameters.
22079 @node Predefined_Numeric_Types
22080 @subsection @code{Predefined_Numeric_Types}
22081 @cindex @code{Predefined_Numeric_Types} rule (for @command{gnatcheck})
22084 Flag each explicit use of the name of any numeric type or subtype defined
22085 in package @code{Standard}.
22087 The rationale for this rule is to detect when the
22088 program may depend on platform-specific characteristics of the implementation
22089 of the predefined numeric types. Note that this rule is over-pessimistic;
22090 for example, a program that uses @code{String} indexing
22091 likely needs a variable of type @code{Integer}.
22092 Another example is the flagging of predefined numeric types with explicit
22095 @smallexample @c ada
22096 subtype My_Integer is Integer range Left .. Right;
22097 Vy_Var : My_Integer;
22101 This rule detects only numeric types and subtypes defined in
22102 @code{Standard}. The use of numeric types and subtypes defined in other
22103 predefined packages (such as @code{System.Any_Priority} or
22104 @code{Ada.Text_IO.Count}) is not flagged
22106 This rule has no parameters.
22110 @node Raising_External_Exceptions
22111 @subsection @code{Raising_External_Exceptions}
22112 @cindex @code{Raising_External_Exceptions} rule (for @command{gnatcheck})
22115 Flag any @code{raise} statement, in a program unit declared in a library
22116 package or in a generic library package, for an exception that is
22117 neither a predefined exception nor an exception that is also declared (or
22118 renamed) in the visible part of the package.
22120 This rule has no parameters.
22124 @node Raising_Predefined_Exceptions
22125 @subsection @code{Raising_Predefined_Exceptions}
22126 @cindex @code{Raising_Predefined_Exceptions} rule (for @command{gnatcheck})
22129 Flag each @code{raise} statement that raises a predefined exception
22130 (i.e., one of the exceptions @code{Constraint_Error}, @code{Numeric_Error},
22131 @code{Program_Error}, @code{Storage_Error}, or @code{Tasking_Error}).
22133 This rule has no parameters.
22135 @node Separate_Numeric_Error_Handlers
22136 @subsection @code{Separate_Numeric_Error_Handlers}
22137 @cindex @code{Separate_Numeric_Error_Handlers} rule (for @command{gnatcheck})
22140 Flags each exception handler that contains a choice for
22141 the predefined @code{Constraint_Error} exception, but does not contain
22142 the choice for the predefined @code{Numeric_Error} exception, or
22143 that contains the choice for @code{Numeric_Error}, but does not contain the
22144 choice for @code{Constraint_Error}.
22146 This rule has no parameters.
22150 @subsection @code{Recursion} (under construction, GLOBAL)
22151 @cindex @code{Recursion} rule (for @command{gnatcheck})
22154 Flag recursive subprograms (cycles in the call graph). Declarations, and not
22155 calls, of recursive subprograms are detected.
22157 This rule has no parameters.
22161 @node Side_Effect_Functions
22162 @subsection @code{Side_Effect_Functions} (under construction, GLOBAL)
22163 @cindex @code{Side_Effect_Functions} rule (for @command{gnatcheck})
22166 Flag functions with side effects.
22168 We define a side effect as changing any data object that is not local for the
22169 body of this function.
22171 At the moment, we do NOT consider a side effect any input-output operations
22172 (changing a state or a content of any file).
22174 We do not consider protected functions for this rule (???)
22176 There are the following sources of side effect:
22179 @item Explicit (or direct) side-effect:
22183 direct assignment to a non-local variable;
22186 direct call to an entity that is known to change some data object that is
22187 not local for the body of this function (Note, that if F1 calls F2 and F2
22188 does have a side effect, this does not automatically mean that F1 also
22189 have a side effect, because it may be the case that F2 is declared in
22190 F1's body and it changes some data object that is global for F2, but
22194 @item Indirect side-effect:
22197 Subprogram calls implicitly issued by:
22200 computing initialization expressions from type declarations as a part
22201 of object elaboration or allocator evaluation;
22203 computing implicit parameters of subprogram or entry calls or generic
22208 activation of a task that change some non-local data object (directly or
22212 elaboration code of a package that is a result of a package instantiation;
22215 controlled objects;
22218 @item Situations when we can suspect a side-effect, but the full static check
22219 is either impossible or too hard:
22222 assignment to access variables or to the objects pointed by access
22226 call to a subprogram pointed by access-to-subprogram value
22234 This rule has no parameters.
22238 @subsection @code{Slices}
22239 @cindex @code{Slices} rule (for @command{gnatcheck})
22242 Flag all uses of array slicing
22244 This rule has no parameters.
22247 @node Unassigned_OUT_Parameters
22248 @subsection @code{Unassigned_OUT_Parameters}
22249 @cindex @code{Unassigned_OUT_Parameters} rule (for @command{gnatcheck})
22252 Flags procedures' @code{out} parameters that are not assigned, and
22253 identifies the contexts in which the assignments are missing.
22255 An @code{out} parameter is flagged in the statements in the procedure
22256 body's handled sequence of statements (before the procedure body's
22257 @code{exception} part, if any) if this sequence of statements contains
22258 no assignments to the parameter.
22260 An @code{out} parameter is flagged in an exception handler in the exception
22261 part of the procedure body's handled sequence of statements if the handler
22262 contains no assignment to the parameter.
22264 Bodies of generic procedures are also considered.
22266 The following are treated as assignments to an @code{out} parameter:
22270 an assignment statement, with the parameter or some component as the target;
22273 passing the parameter (or one of its components) as an @code{out} or
22274 @code{in out} parameter.
22278 This rule does not have any parameters.
22282 @node Uncommented_BEGIN_In_Package_Bodies
22283 @subsection @code{Uncommented_BEGIN_In_Package_Bodies}
22284 @cindex @code{Uncommented_BEGIN_In_Package_Bodies} rule (for @command{gnatcheck})
22287 Flags each package body with declarations and a statement part that does not
22288 include a trailing comment on the line containing the @code{begin} keyword;
22289 this trailing comment needs to specify the package name and nothing else.
22290 The @code{begin} is not flagged if the package body does not
22291 contain any declarations.
22293 If the @code{begin} keyword is placed on the
22294 same line as the last declaration or the first statement, it is flagged
22295 independently of whether the line contains a trailing comment. The
22296 diagnostic message is attached to the line containing the first statement.
22298 This rule has no parameters.
22300 @node Unconditional_Exits
22301 @subsection @code{Unconditional_Exits}
22302 @cindex @code{Unconditional_Exits} rule (for @command{gnatcheck})
22305 Flag unconditional @code{exit} statements.
22307 This rule has no parameters.
22309 @node Unconstrained_Array_Returns
22310 @subsection @code{Unconstrained_Array_Returns}
22311 @cindex @code{Unconstrained_Array_Returns} rule (for @command{gnatcheck})
22314 Flag each function returning an unconstrained array. Function declarations,
22315 function bodies (and body stubs) having no separate specifications,
22316 and generic function instantiations are checked.
22317 Generic function declarations, function calls and function renamings are
22320 This rule has no parameters.
22322 @node Universal_Ranges
22323 @subsection @code{Universal_Ranges}
22324 @cindex @code{Universal_Ranges} rule (for @command{gnatcheck})
22327 Flag discrete ranges that are a part of an index constraint, constrained
22328 array definition, or @code{for}-loop parameter specification, and whose bounds
22329 are both of type @i{universal_integer}. Ranges that have at least one
22330 bound of a specific type (such as @code{1 .. N}, where @code{N} is a variable
22331 or an expression of non-universal type) are not flagged.
22333 This rule has no parameters.
22336 @node Unnamed_Blocks_And_Loops
22337 @subsection @code{Unnamed_Blocks_And_Loops}
22338 @cindex @code{Unnamed_Blocks_And_Loops} rule (for @command{gnatcheck})
22341 Flag each unnamed block statement and loop statement.
22343 The rule has no parameters.
22348 @node Unused_Subprograms
22349 @subsection @code{Unused_Subprograms} (under construction, GLOBAL)
22350 @cindex @code{Unused_Subprograms} rule (for @command{gnatcheck})
22353 Flag all unused subprograms.
22355 This rule has no parameters.
22361 @node USE_PACKAGE_Clauses
22362 @subsection @code{USE_PACKAGE_Clauses}
22363 @cindex @code{USE_PACKAGE_Clauses} rule (for @command{gnatcheck})
22366 Flag all @code{use} clauses for packages; @code{use type} clauses are
22369 This rule has no parameters.
22373 @node Volatile_Objects_Without_Address_Clauses
22374 @subsection @code{Volatile_Objects_Without_Address_Clauses}
22375 @cindex @code{Volatile_Objects_Without_Address_Clauses} rule (for @command{gnatcheck})
22378 Flag each volatile object that does not have an address clause.
22380 The following check is made: if the pragma @code{Volatile} is applied to a
22381 data object or to its type, then an address clause must
22382 be supplied for this object.
22384 This rule does not check the components of data objects,
22385 array components that are volatile as a result of the pragma
22386 @code{Volatile_Components}, or objects that are volatile because
22387 they are atomic as a result of pragmas @code{Atomic} or
22388 @code{Atomic_Components}.
22390 Only variable declarations, and not constant declarations, are checked.
22392 This rule has no parameters.
22395 @c *********************************
22396 @node Creating Sample Bodies Using gnatstub
22397 @chapter Creating Sample Bodies Using @command{gnatstub}
22401 @command{gnatstub} creates body stubs, that is, empty but compilable bodies
22402 for library unit declarations.
22404 Note: to invoke @code{gnatstub} with a project file, use the @code{gnat}
22405 driver (see @ref{The GNAT Driver and Project Files}).
22407 To create a body stub, @command{gnatstub} has to compile the library
22408 unit declaration. Therefore, bodies can be created only for legal
22409 library units. Moreover, if a library unit depends semantically upon
22410 units located outside the current directory, you have to provide
22411 the source search path when calling @command{gnatstub}, see the description
22412 of @command{gnatstub} switches below.
22414 By default, all the program unit body stubs generated by @code{gnatstub}
22415 raise the predefined @code{Program_Error} exception, which will catch
22416 accidental calls of generated stubs. This behavior can be changed with
22417 option @option{^--no-exception^/NO_EXCEPTION^} (see below).
22420 * Running gnatstub::
22421 * Switches for gnatstub::
22424 @node Running gnatstub
22425 @section Running @command{gnatstub}
22428 @command{gnatstub} has the command-line interface of the form
22431 $ gnatstub @ovar{switches} @var{filename} @ovar{directory}
22438 is the name of the source file that contains a library unit declaration
22439 for which a body must be created. The file name may contain the path
22441 The file name does not have to follow the GNAT file name conventions. If the
22443 does not follow GNAT file naming conventions, the name of the body file must
22445 explicitly as the value of the @option{^-o^/BODY=^@var{body-name}} option.
22446 If the file name follows the GNAT file naming
22447 conventions and the name of the body file is not provided,
22450 of the body file from the argument file name by replacing the @file{.ads}
22452 with the @file{.adb} suffix.
22455 indicates the directory in which the body stub is to be placed (the default
22460 is an optional sequence of switches as described in the next section
22463 @node Switches for gnatstub
22464 @section Switches for @command{gnatstub}
22470 @cindex @option{^-f^/FULL^} (@command{gnatstub})
22471 If the destination directory already contains a file with the name of the
22473 for the argument spec file, replace it with the generated body stub.
22475 @item ^-hs^/HEADER=SPEC^
22476 @cindex @option{^-hs^/HEADER=SPEC^} (@command{gnatstub})
22477 Put the comment header (i.e., all the comments preceding the
22478 compilation unit) from the source of the library unit declaration
22479 into the body stub.
22481 @item ^-hg^/HEADER=GENERAL^
22482 @cindex @option{^-hg^/HEADER=GENERAL^} (@command{gnatstub})
22483 Put a sample comment header into the body stub.
22485 @item ^--header-file=@var{filename}^/FROM_HEADER_FILE=@var{filename}^
22486 @cindex @option{^--header-file^/FROM_HEADER_FILE=^} (@command{gnatstub})
22487 Use the content of the file as the comment header for a generated body stub.
22491 @cindex @option{-IDIR} (@command{gnatstub})
22493 @cindex @option{-I-} (@command{gnatstub})
22496 @item /NOCURRENT_DIRECTORY
22497 @cindex @option{/NOCURRENT_DIRECTORY} (@command{gnatstub})
22499 ^These switches have ^This switch has^ the same meaning as in calls to
22501 ^They define ^It defines ^ the source search path in the call to
22502 @command{gcc} issued
22503 by @command{gnatstub} to compile an argument source file.
22505 @item ^-gnatec^/CONFIGURATION_PRAGMAS_FILE=^@var{PATH}
22506 @cindex @option{^-gnatec^/CONFIGURATION_PRAGMAS_FILE^} (@command{gnatstub})
22507 This switch has the same meaning as in calls to @command{gcc}.
22508 It defines the additional configuration file to be passed to the call to
22509 @command{gcc} issued
22510 by @command{gnatstub} to compile an argument source file.
22512 @item ^-gnatyM^/MAX_LINE_LENGTH=^@var{n}
22513 @cindex @option{^-gnatyM^/MAX_LINE_LENGTH^} (@command{gnatstub})
22514 (@var{n} is a non-negative integer). Set the maximum line length in the
22515 body stub to @var{n}; the default is 79. The maximum value that can be
22516 specified is 32767. Note that in the special case of configuration
22517 pragma files, the maximum is always 32767 regardless of whether or
22518 not this switch appears.
22520 @item ^-gnaty^/STYLE_CHECKS=^@var{n}
22521 @cindex @option{^-gnaty^/STYLE_CHECKS=^} (@command{gnatstub})
22522 (@var{n} is a non-negative integer from 1 to 9). Set the indentation level in
22523 the generated body sample to @var{n}.
22524 The default indentation is 3.
22526 @item ^-gnatyo^/ORDERED_SUBPROGRAMS^
22527 @cindex @option{^-gnato^/ORDERED_SUBPROGRAMS^} (@command{gnatstub})
22528 Order local bodies alphabetically. (By default local bodies are ordered
22529 in the same way as the corresponding local specs in the argument spec file.)
22531 @item ^-i^/INDENTATION=^@var{n}
22532 @cindex @option{^-i^/INDENTATION^} (@command{gnatstub})
22533 Same as @option{^-gnaty^/STYLE_CHECKS=^@var{n}}
22535 @item ^-k^/TREE_FILE=SAVE^
22536 @cindex @option{^-k^/TREE_FILE=SAVE^} (@command{gnatstub})
22537 Do not remove the tree file (i.e., the snapshot of the compiler internal
22538 structures used by @command{gnatstub}) after creating the body stub.
22540 @item ^-l^/LINE_LENGTH=^@var{n}
22541 @cindex @option{^-l^/LINE_LENGTH^} (@command{gnatstub})
22542 Same as @option{^-gnatyM^/MAX_LINE_LENGTH=^@var{n}}
22544 @item ^--no-exception^/NO_EXCEPTION^
22545 @cindex @option{^--no-exception^/NO_EXCEPTION^} (@command{gnatstub})
22546 Avoind raising PROGRAM_ERROR in the generated bodies of program unit stubs.
22547 This is not always possible for function stubs.
22549 @item ^-o ^/BODY=^@var{body-name}
22550 @cindex @option{^-o^/BODY^} (@command{gnatstub})
22551 Body file name. This should be set if the argument file name does not
22553 the GNAT file naming
22554 conventions. If this switch is omitted the default name for the body will be
22556 from the argument file name according to the GNAT file naming conventions.
22559 @cindex @option{^-q^/QUIET^} (@command{gnatstub})
22560 Quiet mode: do not generate a confirmation when a body is
22561 successfully created, and do not generate a message when a body is not
22565 @item ^-r^/TREE_FILE=REUSE^
22566 @cindex @option{^-r^/TREE_FILE=REUSE^} (@command{gnatstub})
22567 Reuse the tree file (if it exists) instead of creating it. Instead of
22568 creating the tree file for the library unit declaration, @command{gnatstub}
22569 tries to find it in the current directory and use it for creating
22570 a body. If the tree file is not found, no body is created. This option
22571 also implies @option{^-k^/SAVE^}, whether or not
22572 the latter is set explicitly.
22574 @item ^-t^/TREE_FILE=OVERWRITE^
22575 @cindex @option{^-t^/TREE_FILE=OVERWRITE^} (@command{gnatstub})
22576 Overwrite the existing tree file. If the current directory already
22577 contains the file which, according to the GNAT file naming rules should
22578 be considered as a tree file for the argument source file,
22580 will refuse to create the tree file needed to create a sample body
22581 unless this option is set.
22583 @item ^-v^/VERBOSE^
22584 @cindex @option{^-v^/VERBOSE^} (@command{gnatstub})
22585 Verbose mode: generate version information.
22589 @c *********************************
22590 @node Generating Ada Bindings for C and C++ headers
22591 @chapter Generating Ada Bindings for C and C++ headers
22595 GNAT now comes with a new experimental binding generator for C and C++
22596 headers which is intended to do 95% of the tedious work of generating
22597 Ada specs from C or C++ header files. Note that this still is a work in
22598 progress, not designed to generate 100% correct Ada specs.
22600 The code generated is using the Ada 2005 syntax, which makes it
22601 easier to interface with other languages than previous versions of Ada.
22604 * Running the binding generator::
22605 * Generating bindings for C++ headers::
22609 @node Running the binding generator
22610 @section Running the binding generator
22613 The binding generator is part of the @command{gcc} compiler and can be
22614 invoked via the @option{-fdump-ada-spec} switch, which will generate Ada
22615 spec files for the header files specified on the command line, and all
22616 header files needed by these files transitivitely. For example:
22619 $ g++ -c -fdump-ada-spec -C /usr/include/time.h
22620 $ gcc -c -gnat05 *.ads
22623 will generate, under GNU/Linux, the following files: @file{time_h.ads},
22624 @file{bits_time_h.ads}, @file{stddef_h.ads}, @file{bits_types_h.ads} which
22625 correspond to the files @file{/usr/include/time.h},
22626 @file{/usr/include/bits/time.h}, etc@dots{}, and will then compile in Ada 2005
22627 mode these Ada specs.
22629 The @code{-C} switch tells @command{gcc} to extract comments from headers,
22630 and will attempt to generate corresponding Ada comments.
22632 If you want to generate a single Ada file and not the transitive closure, you
22633 can use instead the @option{-fdump-ada-spec-slim} switch.
22635 Note that we recommend when possible to use the @command{g++} driver to
22636 generate bindings, even for most C headers, since this will in general
22637 generate better Ada specs. For generating bindings for C++ headers, it is
22638 mandatory to use the @command{g++} command, or @command{gcc -x c++} which
22639 is equivalent in this case. If @command{g++} cannot work on your C headers
22640 because of incompatibilities between C and C++, then you can fallback to
22641 @command{gcc} instead.
22643 For an example of better bindings generated from the C++ front-end,
22644 the name of the parameters (when available) are actually ignored by the C
22645 front-end. Consider the following C header:
22648 extern void foo (int variable);
22651 with the C front-end, @code{variable} is ignored, and the above is handled as:
22654 extern void foo (int);
22657 generating a generic:
22660 procedure foo (param1 : int);
22663 with the C++ front-end, the name is available, and we generate:
22666 procedure foo (variable : int);
22669 In some cases, the generated bindings will be more complete or more meaningful
22670 when defining some macros, which you can do via the @option{-D} switch. This
22671 is for example the case with @file{Xlib.h} under GNU/Linux:
22674 g++ -c -fdump-ada-spec -DXLIB_ILLEGAL_ACCESS -C /usr/include/X11/Xlib.h
22677 The above will generate more complete bindings than a straight call without
22678 the @option{-DXLIB_ILLEGAL_ACCESS} switch.
22680 In other cases, it is not possible to parse a header file in a stand alone
22681 manner, because other include files need to be included first. In this
22682 case, the solution is to create a small header file including the needed
22683 @code{#include} and possible @code{#define} directives. For example, to
22684 generate Ada bindings for @file{readline/readline.h}, you need to first
22685 include @file{stdio.h}, so you can create a file with the following two
22686 lines in e.g. @file{readline1.h}:
22690 #include <readline/readline.h>
22693 and then generate Ada bindings from this file:
22696 $ g++ -c -fdump-ada-spec readline1.h
22699 @node Generating bindings for C++ headers
22700 @section Generating bindings for C++ headers
22703 Generating bindings for C++ headers is done using the same options, always
22704 with the @command{g++} compiler.
22706 In this mode, C++ classes will be mapped to Ada tagged types, constructors
22707 will be mapped using the @code{CPP_Constructor} pragma, and when possible,
22708 multiple inheritance of abstract classes will be mapped to Ada interfaces
22709 (@xref{Interfacing to C++,,,gnat_rm, GNAT Reference Manual}, for additional
22710 information on interfacing to C++).
22712 For example, given the following C++ header file:
22719 virtual int Number_Of_Teeth () = 0;
22724 virtual void Set_Owner (char* Name) = 0;
22730 virtual void Set_Age (int New_Age);
22733 class Dog : Animal, Carnivore, Domestic @{
22738 virtual int Number_Of_Teeth ();
22739 virtual void Set_Owner (char* Name);
22747 The corresponding Ada code is generated:
22749 @smallexample @c ada
22752 package Class_Carnivore is
22753 type Carnivore is limited interface;
22754 pragma Import (CPP, Carnivore);
22756 function Number_Of_Teeth (this : access Carnivore) return int is abstract;
22758 use Class_Carnivore;
22760 package Class_Domestic is
22761 type Domestic is limited interface;
22762 pragma Import (CPP, Domestic);
22764 procedure Set_Owner
22765 (this : access Domestic;
22766 Name : Interfaces.C.Strings.chars_ptr) is abstract;
22768 use Class_Domestic;
22770 package Class_Animal is
22771 type Animal is tagged limited record
22772 Age_Count : aliased int;
22774 pragma Import (CPP, Animal);
22776 procedure Set_Age (this : access Animal; New_Age : int);
22777 pragma Import (CPP, Set_Age, "_ZN6Animal7Set_AgeEi");
22781 package Class_Dog is
22782 type Dog is new Animal and Carnivore and Domestic with record
22783 Tooth_Count : aliased int;
22784 Owner : Interfaces.C.Strings.chars_ptr;
22786 pragma Import (CPP, Dog);
22788 function Number_Of_Teeth (this : access Dog) return int;
22789 pragma Import (CPP, Number_Of_Teeth, "_ZN3Dog15Number_Of_TeethEv");
22791 procedure Set_Owner
22792 (this : access Dog; Name : Interfaces.C.Strings.chars_ptr);
22793 pragma Import (CPP, Set_Owner, "_ZN3Dog9Set_OwnerEPc");
22795 function New_Dog return Dog'Class;
22796 pragma CPP_Constructor (New_Dog);
22797 pragma Import (CPP, New_Dog, "_ZN3DogC1Ev");
22808 @item -fdump-ada-spec
22809 @cindex @option{-fdump-ada-spec} (@command{gcc})
22810 Generate Ada spec files for the given header files transitively (including
22811 all header files that these headers depend upon).
22813 @item -fdump-ada-spec-slim
22814 @cindex @option{-fdump-ada-spec-slim} (@command{gcc})
22815 Generate Ada spec files for the header files specified on the command line
22819 @cindex @option{-C} (@command{gcc})
22820 Extract comments from headers and generate Ada comments in the Ada spec files.
22823 @node Other Utility Programs
22824 @chapter Other Utility Programs
22827 This chapter discusses some other utility programs available in the Ada
22831 * Using Other Utility Programs with GNAT::
22832 * The External Symbol Naming Scheme of GNAT::
22833 * Converting Ada Files to html with gnathtml::
22834 * Installing gnathtml::
22841 @node Using Other Utility Programs with GNAT
22842 @section Using Other Utility Programs with GNAT
22845 The object files generated by GNAT are in standard system format and in
22846 particular the debugging information uses this format. This means
22847 programs generated by GNAT can be used with existing utilities that
22848 depend on these formats.
22851 In general, any utility program that works with C will also often work with
22852 Ada programs generated by GNAT. This includes software utilities such as
22853 gprof (a profiling program), @code{gdb} (the FSF debugger), and utilities such
22857 @node The External Symbol Naming Scheme of GNAT
22858 @section The External Symbol Naming Scheme of GNAT
22861 In order to interpret the output from GNAT, when using tools that are
22862 originally intended for use with other languages, it is useful to
22863 understand the conventions used to generate link names from the Ada
22866 All link names are in all lowercase letters. With the exception of library
22867 procedure names, the mechanism used is simply to use the full expanded
22868 Ada name with dots replaced by double underscores. For example, suppose
22869 we have the following package spec:
22871 @smallexample @c ada
22882 The variable @code{MN} has a full expanded Ada name of @code{QRS.MN}, so
22883 the corresponding link name is @code{qrs__mn}.
22885 Of course if a @code{pragma Export} is used this may be overridden:
22887 @smallexample @c ada
22892 pragma Export (Var1, C, External_Name => "var1_name");
22894 pragma Export (Var2, C, Link_Name => "var2_link_name");
22901 In this case, the link name for @var{Var1} is whatever link name the
22902 C compiler would assign for the C function @var{var1_name}. This typically
22903 would be either @var{var1_name} or @var{_var1_name}, depending on operating
22904 system conventions, but other possibilities exist. The link name for
22905 @var{Var2} is @var{var2_link_name}, and this is not operating system
22909 One exception occurs for library level procedures. A potential ambiguity
22910 arises between the required name @code{_main} for the C main program,
22911 and the name we would otherwise assign to an Ada library level procedure
22912 called @code{Main} (which might well not be the main program).
22914 To avoid this ambiguity, we attach the prefix @code{_ada_} to such
22915 names. So if we have a library level procedure such as
22917 @smallexample @c ada
22920 procedure Hello (S : String);
22926 the external name of this procedure will be @var{_ada_hello}.
22929 @node Converting Ada Files to html with gnathtml
22930 @section Converting Ada Files to HTML with @code{gnathtml}
22933 This @code{Perl} script allows Ada source files to be browsed using
22934 standard Web browsers. For installation procedure, see the section
22935 @xref{Installing gnathtml}.
22937 Ada reserved keywords are highlighted in a bold font and Ada comments in
22938 a blue font. Unless your program was compiled with the gcc @option{-gnatx}
22939 switch to suppress the generation of cross-referencing information, user
22940 defined variables and types will appear in a different color; you will
22941 be able to click on any identifier and go to its declaration.
22943 The command line is as follow:
22945 $ perl gnathtml.pl @ovar{^switches^options^} @var{ada-files}
22949 You can pass it as many Ada files as you want. @code{gnathtml} will generate
22950 an html file for every ada file, and a global file called @file{index.htm}.
22951 This file is an index of every identifier defined in the files.
22953 The available ^switches^options^ are the following ones:
22957 @cindex @option{-83} (@code{gnathtml})
22958 Only the Ada 83 subset of keywords will be highlighted.
22960 @item -cc @var{color}
22961 @cindex @option{-cc} (@code{gnathtml})
22962 This option allows you to change the color used for comments. The default
22963 value is green. The color argument can be any name accepted by html.
22966 @cindex @option{-d} (@code{gnathtml})
22967 If the Ada files depend on some other files (for instance through
22968 @code{with} clauses, the latter files will also be converted to html.
22969 Only the files in the user project will be converted to html, not the files
22970 in the run-time library itself.
22973 @cindex @option{-D} (@code{gnathtml})
22974 This command is the same as @option{-d} above, but @command{gnathtml} will
22975 also look for files in the run-time library, and generate html files for them.
22977 @item -ext @var{extension}
22978 @cindex @option{-ext} (@code{gnathtml})
22979 This option allows you to change the extension of the generated HTML files.
22980 If you do not specify an extension, it will default to @file{htm}.
22983 @cindex @option{-f} (@code{gnathtml})
22984 By default, gnathtml will generate html links only for global entities
22985 ('with'ed units, global variables and types,@dots{}). If you specify
22986 @option{-f} on the command line, then links will be generated for local
22989 @item -l @var{number}
22990 @cindex @option{-l} (@code{gnathtml})
22991 If this ^switch^option^ is provided and @var{number} is not 0, then
22992 @code{gnathtml} will number the html files every @var{number} line.
22995 @cindex @option{-I} (@code{gnathtml})
22996 Specify a directory to search for library files (@file{.ALI} files) and
22997 source files. You can provide several -I switches on the command line,
22998 and the directories will be parsed in the order of the command line.
23001 @cindex @option{-o} (@code{gnathtml})
23002 Specify the output directory for html files. By default, gnathtml will
23003 saved the generated html files in a subdirectory named @file{html/}.
23005 @item -p @var{file}
23006 @cindex @option{-p} (@code{gnathtml})
23007 If you are using Emacs and the most recent Emacs Ada mode, which provides
23008 a full Integrated Development Environment for compiling, checking,
23009 running and debugging applications, you may use @file{.gpr} files
23010 to give the directories where Emacs can find sources and object files.
23012 Using this ^switch^option^, you can tell gnathtml to use these files.
23013 This allows you to get an html version of your application, even if it
23014 is spread over multiple directories.
23016 @item -sc @var{color}
23017 @cindex @option{-sc} (@code{gnathtml})
23018 This ^switch^option^ allows you to change the color used for symbol
23020 The default value is red. The color argument can be any name accepted by html.
23022 @item -t @var{file}
23023 @cindex @option{-t} (@code{gnathtml})
23024 This ^switch^option^ provides the name of a file. This file contains a list of
23025 file names to be converted, and the effect is exactly as though they had
23026 appeared explicitly on the command line. This
23027 is the recommended way to work around the command line length limit on some
23032 @node Installing gnathtml
23033 @section Installing @code{gnathtml}
23036 @code{Perl} needs to be installed on your machine to run this script.
23037 @code{Perl} is freely available for almost every architecture and
23038 Operating System via the Internet.
23040 On Unix systems, you may want to modify the first line of the script
23041 @code{gnathtml}, to explicitly tell the Operating system where Perl
23042 is. The syntax of this line is:
23044 #!full_path_name_to_perl
23048 Alternatively, you may run the script using the following command line:
23051 $ perl gnathtml.pl @ovar{switches} @var{files}
23060 The GNAT distribution provides an Ada 95 template for the HP Language
23061 Sensitive Editor (LSE), a component of DECset. In order to
23062 access it, invoke LSE with the qualifier /ENVIRONMENT=GNU:[LIB]ADA95.ENV.
23069 GNAT supports The HP Performance Coverage Analyzer (PCA), a component
23070 of DECset. To use it proceed as outlined under ``HELP PCA'', except for running
23071 the collection phase with the /DEBUG qualifier.
23074 $ GNAT MAKE /DEBUG <PROGRAM_NAME>
23075 $ DEFINE LIB$DEBUG PCA$COLLECTOR
23076 $ RUN/DEBUG <PROGRAM_NAME>
23082 @c ******************************
23083 @node Code Coverage and Profiling
23084 @chapter Code Coverage and Profiling
23085 @cindex Code Coverage
23089 This chapter describes how to use @code{gcov} - coverage testing tool - and
23090 @code{gprof} - profiler tool - on your Ada programs.
23093 * Code Coverage of Ada Programs using gcov::
23094 * Profiling an Ada Program using gprof::
23097 @node Code Coverage of Ada Programs using gcov
23098 @section Code Coverage of Ada Programs using gcov
23100 @cindex -fprofile-arcs
23101 @cindex -ftest-coverage
23103 @cindex Code Coverage
23106 @code{gcov} is a test coverage program: it analyzes the execution of a given
23107 program on selected tests, to help you determine the portions of the program
23108 that are still untested.
23110 @code{gcov} is part of the GCC suite, and is described in detail in the GCC
23111 User's Guide. You can refer to this documentation for a more complete
23114 This chapter provides a quick startup guide, and
23115 details some Gnat-specific features.
23118 * Quick startup guide::
23122 @node Quick startup guide
23123 @subsection Quick startup guide
23125 In order to perform coverage analysis of a program using @code{gcov}, 3
23130 Code instrumentation during the compilation process
23132 Execution of the instrumented program
23134 Execution of the @code{gcov} tool to generate the result.
23137 The code instrumentation needed by gcov is created at the object level:
23138 The source code is not modified in any way, because the instrumentation code is
23139 inserted by gcc during the compilation process. To compile your code with code
23140 coverage activated, you need to recompile your whole project using the
23142 @code{-fprofile-arcs} and @code{-ftest-coverage}, and link it using
23143 @code{-fprofile-arcs}.
23146 $ gnatmake -P my_project.gpr -f -cargs -fprofile-arcs -ftest-coverage \
23147 -largs -fprofile-arcs
23150 This compilation process will create @file{.gcno} files together with
23151 the usual object files.
23153 Once the program is compiled with coverage instrumentation, you can
23154 run it as many times as needed - on portions of a test suite for
23155 example. The first execution will produce @file{.gcda} files at the
23156 same location as the @file{.gcno} files. The following executions
23157 will update those files, so that a cumulative result of the covered
23158 portions of the program is generated.
23160 Finally, you need to call the @code{gcov} tool. The different options of
23161 @code{gcov} are available in the GCC User's Guide, section 'Invoking gcov'.
23163 This will create annotated source files with a @file{.gcov} extension:
23164 @file{my_main.adb} file will be analysed in @file{my_main.adb.gcov}.
23166 @node Gnat specifics
23167 @subsection Gnat specifics
23169 Because Ada semantics, portions of the source code may be shared among
23170 several object files. This is the case for example when generics are
23171 involved, when inlining is active or when declarations generate initialisation
23172 calls. In order to take
23173 into account this shared code, you need to call @code{gcov} on all
23174 source files of the tested program at once.
23176 The list of source files might exceed the system's maximum command line
23177 length. In order to bypass this limitation, a new mechanism has been
23178 implemented in @code{gcov}: you can now list all your project's files into a
23179 text file, and provide this file to gcov as a parameter, preceded by a @@
23180 (e.g. @samp{gcov @@mysrclist.txt}).
23182 Note that on AIX compiling a static library with @code{-fprofile-arcs} is
23183 not supported as there can be unresolved symbols during the final link.
23185 @node Profiling an Ada Program using gprof
23186 @section Profiling an Ada Program using gprof
23192 This section is not meant to be an exhaustive documentation of @code{gprof}.
23193 Full documentation for it can be found in the GNU Profiler User's Guide
23194 documentation that is part of this GNAT distribution.
23196 Profiling a program helps determine the parts of a program that are executed
23197 most often, and are therefore the most time-consuming.
23199 @code{gprof} is the standard GNU profiling tool; it has been enhanced to
23200 better handle Ada programs and multitasking.
23201 It is currently supported on the following platforms
23206 solaris sparc/sparc64/x86
23212 In order to profile a program using @code{gprof}, 3 steps are needed:
23216 Code instrumentation, requiring a full recompilation of the project with the
23219 Execution of the program under the analysis conditions, i.e. with the desired
23222 Analysis of the results using the @code{gprof} tool.
23226 The following sections detail the different steps, and indicate how
23227 to interpret the results:
23229 * Compilation for profiling::
23230 * Program execution::
23232 * Interpretation of profiling results::
23235 @node Compilation for profiling
23236 @subsection Compilation for profiling
23240 In order to profile a program the first step is to tell the compiler
23241 to generate the necessary profiling information. The compiler switch to be used
23242 is @code{-pg}, which must be added to other compilation switches. This
23243 switch needs to be specified both during compilation and link stages, and can
23244 be specified once when using gnatmake:
23247 gnatmake -f -pg -P my_project
23251 Note that only the objects that were compiled with the @samp{-pg} switch will be
23252 profiled; if you need to profile your whole project, use the
23253 @samp{-f} gnatmake switch to force full recompilation.
23255 @node Program execution
23256 @subsection Program execution
23259 Once the program has been compiled for profiling, you can run it as usual.
23261 The only constraint imposed by profiling is that the program must terminate
23262 normally. An interrupted program (via a Ctrl-C, kill, etc.) will not be
23265 Once the program completes execution, a data file called @file{gmon.out} is
23266 generated in the directory where the program was launched from. If this file
23267 already exists, it will be overwritten.
23269 @node Running gprof
23270 @subsection Running gprof
23273 The @code{gprof} tool is called as follow:
23276 gprof my_prog gmon.out
23287 The complete form of the gprof command line is the following:
23290 gprof [^switches^options^] [executable [data-file]]
23294 @code{gprof} supports numerous ^switch^options^. The order of these
23295 ^switch^options^ does not matter. The full list of options can be found in
23296 the GNU Profiler User's Guide documentation that comes with this documentation.
23298 The following is the subset of those switches that is most relevant:
23302 @item --demangle[=@var{style}]
23303 @itemx --no-demangle
23304 @cindex @option{--demangle} (@code{gprof})
23305 These options control whether symbol names should be demangled when
23306 printing output. The default is to demangle C++ symbols. The
23307 @code{--no-demangle} option may be used to turn off demangling. Different
23308 compilers have different mangling styles. The optional demangling style
23309 argument can be used to choose an appropriate demangling style for your
23310 compiler, in particular Ada symbols generated by GNAT can be demangled using
23311 @code{--demangle=gnat}.
23313 @item -e @var{function_name}
23314 @cindex @option{-e} (@code{gprof})
23315 The @samp{-e @var{function}} option tells @code{gprof} not to print
23316 information about the function @var{function_name} (and its
23317 children@dots{}) in the call graph. The function will still be listed
23318 as a child of any functions that call it, but its index number will be
23319 shown as @samp{[not printed]}. More than one @samp{-e} option may be
23320 given; only one @var{function_name} may be indicated with each @samp{-e}
23323 @item -E @var{function_name}
23324 @cindex @option{-E} (@code{gprof})
23325 The @code{-E @var{function}} option works like the @code{-e} option, but
23326 execution time spent in the function (and children who were not called from
23327 anywhere else), will not be used to compute the percentages-of-time for
23328 the call graph. More than one @samp{-E} option may be given; only one
23329 @var{function_name} may be indicated with each @samp{-E} option.
23331 @item -f @var{function_name}
23332 @cindex @option{-f} (@code{gprof})
23333 The @samp{-f @var{function}} option causes @code{gprof} to limit the
23334 call graph to the function @var{function_name} and its children (and
23335 their children@dots{}). More than one @samp{-f} option may be given;
23336 only one @var{function_name} may be indicated with each @samp{-f}
23339 @item -F @var{function_name}
23340 @cindex @option{-F} (@code{gprof})
23341 The @samp{-F @var{function}} option works like the @code{-f} option, but
23342 only time spent in the function and its children (and their
23343 children@dots{}) will be used to determine total-time and
23344 percentages-of-time for the call graph. More than one @samp{-F} option
23345 may be given; only one @var{function_name} may be indicated with each
23346 @samp{-F} option. The @samp{-F} option overrides the @samp{-E} option.
23350 @node Interpretation of profiling results
23351 @subsection Interpretation of profiling results
23355 The results of the profiling analysis are represented by two arrays: the
23356 'flat profile' and the 'call graph'. Full documentation of those outputs
23357 can be found in the GNU Profiler User's Guide.
23359 The flat profile shows the time spent in each function of the program, and how
23360 many time it has been called. This allows you to locate easily the most
23361 time-consuming functions.
23363 The call graph shows, for each subprogram, the subprograms that call it,
23364 and the subprograms that it calls. It also provides an estimate of the time
23365 spent in each of those callers/called subprograms.
23368 @c ******************************
23369 @node Running and Debugging Ada Programs
23370 @chapter Running and Debugging Ada Programs
23374 This chapter discusses how to debug Ada programs.
23376 It applies to GNAT on the Alpha OpenVMS platform;
23377 for I64 OpenVMS please refer to the @cite{OpenVMS Debugger Manual},
23378 since HP has implemented Ada support in the OpenVMS debugger on I64.
23381 An incorrect Ada program may be handled in three ways by the GNAT compiler:
23385 The illegality may be a violation of the static semantics of Ada. In
23386 that case GNAT diagnoses the constructs in the program that are illegal.
23387 It is then a straightforward matter for the user to modify those parts of
23391 The illegality may be a violation of the dynamic semantics of Ada. In
23392 that case the program compiles and executes, but may generate incorrect
23393 results, or may terminate abnormally with some exception.
23396 When presented with a program that contains convoluted errors, GNAT
23397 itself may terminate abnormally without providing full diagnostics on
23398 the incorrect user program.
23402 * The GNAT Debugger GDB::
23404 * Introduction to GDB Commands::
23405 * Using Ada Expressions::
23406 * Calling User-Defined Subprograms::
23407 * Using the Next Command in a Function::
23410 * Debugging Generic Units::
23411 * GNAT Abnormal Termination or Failure to Terminate::
23412 * Naming Conventions for GNAT Source Files::
23413 * Getting Internal Debugging Information::
23414 * Stack Traceback::
23420 @node The GNAT Debugger GDB
23421 @section The GNAT Debugger GDB
23424 @code{GDB} is a general purpose, platform-independent debugger that
23425 can be used to debug mixed-language programs compiled with @command{gcc},
23426 and in particular is capable of debugging Ada programs compiled with
23427 GNAT. The latest versions of @code{GDB} are Ada-aware and can handle
23428 complex Ada data structures.
23430 @xref{Top,, Debugging with GDB, gdb, Debugging with GDB},
23432 located in the GNU:[DOCS] directory,
23434 for full details on the usage of @code{GDB}, including a section on
23435 its usage on programs. This manual should be consulted for full
23436 details. The section that follows is a brief introduction to the
23437 philosophy and use of @code{GDB}.
23439 When GNAT programs are compiled, the compiler optionally writes debugging
23440 information into the generated object file, including information on
23441 line numbers, and on declared types and variables. This information is
23442 separate from the generated code. It makes the object files considerably
23443 larger, but it does not add to the size of the actual executable that
23444 will be loaded into memory, and has no impact on run-time performance. The
23445 generation of debug information is triggered by the use of the
23446 ^-g^/DEBUG^ switch in the @command{gcc} or @command{gnatmake} command
23447 used to carry out the compilations. It is important to emphasize that
23448 the use of these options does not change the generated code.
23450 The debugging information is written in standard system formats that
23451 are used by many tools, including debuggers and profilers. The format
23452 of the information is typically designed to describe C types and
23453 semantics, but GNAT implements a translation scheme which allows full
23454 details about Ada types and variables to be encoded into these
23455 standard C formats. Details of this encoding scheme may be found in
23456 the file exp_dbug.ads in the GNAT source distribution. However, the
23457 details of this encoding are, in general, of no interest to a user,
23458 since @code{GDB} automatically performs the necessary decoding.
23460 When a program is bound and linked, the debugging information is
23461 collected from the object files, and stored in the executable image of
23462 the program. Again, this process significantly increases the size of
23463 the generated executable file, but it does not increase the size of
23464 the executable program itself. Furthermore, if this program is run in
23465 the normal manner, it runs exactly as if the debug information were
23466 not present, and takes no more actual memory.
23468 However, if the program is run under control of @code{GDB}, the
23469 debugger is activated. The image of the program is loaded, at which
23470 point it is ready to run. If a run command is given, then the program
23471 will run exactly as it would have if @code{GDB} were not present. This
23472 is a crucial part of the @code{GDB} design philosophy. @code{GDB} is
23473 entirely non-intrusive until a breakpoint is encountered. If no
23474 breakpoint is ever hit, the program will run exactly as it would if no
23475 debugger were present. When a breakpoint is hit, @code{GDB} accesses
23476 the debugging information and can respond to user commands to inspect
23477 variables, and more generally to report on the state of execution.
23481 @section Running GDB
23484 This section describes how to initiate the debugger.
23485 @c The above sentence is really just filler, but it was otherwise
23486 @c clumsy to get the first paragraph nonindented given the conditional
23487 @c nature of the description
23490 The debugger can be launched from a @code{GPS} menu or
23491 directly from the command line. The description below covers the latter use.
23492 All the commands shown can be used in the @code{GPS} debug console window,
23493 but there are usually more GUI-based ways to achieve the same effect.
23496 The command to run @code{GDB} is
23499 $ ^gdb program^GDB PROGRAM^
23503 where @code{^program^PROGRAM^} is the name of the executable file. This
23504 activates the debugger and results in a prompt for debugger commands.
23505 The simplest command is simply @code{run}, which causes the program to run
23506 exactly as if the debugger were not present. The following section
23507 describes some of the additional commands that can be given to @code{GDB}.
23509 @c *******************************
23510 @node Introduction to GDB Commands
23511 @section Introduction to GDB Commands
23514 @code{GDB} contains a large repertoire of commands. @xref{Top,,
23515 Debugging with GDB, gdb, Debugging with GDB},
23517 located in the GNU:[DOCS] directory,
23519 for extensive documentation on the use
23520 of these commands, together with examples of their use. Furthermore,
23521 the command @command{help} invoked from within GDB activates a simple help
23522 facility which summarizes the available commands and their options.
23523 In this section we summarize a few of the most commonly
23524 used commands to give an idea of what @code{GDB} is about. You should create
23525 a simple program with debugging information and experiment with the use of
23526 these @code{GDB} commands on the program as you read through the
23530 @item set args @var{arguments}
23531 The @var{arguments} list above is a list of arguments to be passed to
23532 the program on a subsequent run command, just as though the arguments
23533 had been entered on a normal invocation of the program. The @code{set args}
23534 command is not needed if the program does not require arguments.
23537 The @code{run} command causes execution of the program to start from
23538 the beginning. If the program is already running, that is to say if
23539 you are currently positioned at a breakpoint, then a prompt will ask
23540 for confirmation that you want to abandon the current execution and
23543 @item breakpoint @var{location}
23544 The breakpoint command sets a breakpoint, that is to say a point at which
23545 execution will halt and @code{GDB} will await further
23546 commands. @var{location} is
23547 either a line number within a file, given in the format @code{file:linenumber},
23548 or it is the name of a subprogram. If you request that a breakpoint be set on
23549 a subprogram that is overloaded, a prompt will ask you to specify on which of
23550 those subprograms you want to breakpoint. You can also
23551 specify that all of them should be breakpointed. If the program is run
23552 and execution encounters the breakpoint, then the program
23553 stops and @code{GDB} signals that the breakpoint was encountered by
23554 printing the line of code before which the program is halted.
23556 @item breakpoint exception @var{name}
23557 A special form of the breakpoint command which breakpoints whenever
23558 exception @var{name} is raised.
23559 If @var{name} is omitted,
23560 then a breakpoint will occur when any exception is raised.
23562 @item print @var{expression}
23563 This will print the value of the given expression. Most simple
23564 Ada expression formats are properly handled by @code{GDB}, so the expression
23565 can contain function calls, variables, operators, and attribute references.
23568 Continues execution following a breakpoint, until the next breakpoint or the
23569 termination of the program.
23572 Executes a single line after a breakpoint. If the next statement
23573 is a subprogram call, execution continues into (the first statement of)
23574 the called subprogram.
23577 Executes a single line. If this line is a subprogram call, executes and
23578 returns from the call.
23581 Lists a few lines around the current source location. In practice, it
23582 is usually more convenient to have a separate edit window open with the
23583 relevant source file displayed. Successive applications of this command
23584 print subsequent lines. The command can be given an argument which is a
23585 line number, in which case it displays a few lines around the specified one.
23588 Displays a backtrace of the call chain. This command is typically
23589 used after a breakpoint has occurred, to examine the sequence of calls that
23590 leads to the current breakpoint. The display includes one line for each
23591 activation record (frame) corresponding to an active subprogram.
23594 At a breakpoint, @code{GDB} can display the values of variables local
23595 to the current frame. The command @code{up} can be used to
23596 examine the contents of other active frames, by moving the focus up
23597 the stack, that is to say from callee to caller, one frame at a time.
23600 Moves the focus of @code{GDB} down from the frame currently being
23601 examined to the frame of its callee (the reverse of the previous command),
23603 @item frame @var{n}
23604 Inspect the frame with the given number. The value 0 denotes the frame
23605 of the current breakpoint, that is to say the top of the call stack.
23610 The above list is a very short introduction to the commands that
23611 @code{GDB} provides. Important additional capabilities, including conditional
23612 breakpoints, the ability to execute command sequences on a breakpoint,
23613 the ability to debug at the machine instruction level and many other
23614 features are described in detail in @ref{Top,, Debugging with GDB, gdb,
23615 Debugging with GDB}. Note that most commands can be abbreviated
23616 (for example, c for continue, bt for backtrace).
23618 @node Using Ada Expressions
23619 @section Using Ada Expressions
23620 @cindex Ada expressions
23623 @code{GDB} supports a fairly large subset of Ada expression syntax, with some
23624 extensions. The philosophy behind the design of this subset is
23628 That @code{GDB} should provide basic literals and access to operations for
23629 arithmetic, dereferencing, field selection, indexing, and subprogram calls,
23630 leaving more sophisticated computations to subprograms written into the
23631 program (which therefore may be called from @code{GDB}).
23634 That type safety and strict adherence to Ada language restrictions
23635 are not particularly important to the @code{GDB} user.
23638 That brevity is important to the @code{GDB} user.
23642 Thus, for brevity, the debugger acts as if there were
23643 implicit @code{with} and @code{use} clauses in effect for all user-written
23644 packages, thus making it unnecessary to fully qualify most names with
23645 their packages, regardless of context. Where this causes ambiguity,
23646 @code{GDB} asks the user's intent.
23648 For details on the supported Ada syntax, see @ref{Top,, Debugging with
23649 GDB, gdb, Debugging with GDB}.
23651 @node Calling User-Defined Subprograms
23652 @section Calling User-Defined Subprograms
23655 An important capability of @code{GDB} is the ability to call user-defined
23656 subprograms while debugging. This is achieved simply by entering
23657 a subprogram call statement in the form:
23660 call subprogram-name (parameters)
23664 The keyword @code{call} can be omitted in the normal case where the
23665 @code{subprogram-name} does not coincide with any of the predefined
23666 @code{GDB} commands.
23668 The effect is to invoke the given subprogram, passing it the
23669 list of parameters that is supplied. The parameters can be expressions and
23670 can include variables from the program being debugged. The
23671 subprogram must be defined
23672 at the library level within your program, and @code{GDB} will call the
23673 subprogram within the environment of your program execution (which
23674 means that the subprogram is free to access or even modify variables
23675 within your program).
23677 The most important use of this facility is in allowing the inclusion of
23678 debugging routines that are tailored to particular data structures
23679 in your program. Such debugging routines can be written to provide a suitably
23680 high-level description of an abstract type, rather than a low-level dump
23681 of its physical layout. After all, the standard
23682 @code{GDB print} command only knows the physical layout of your
23683 types, not their abstract meaning. Debugging routines can provide information
23684 at the desired semantic level and are thus enormously useful.
23686 For example, when debugging GNAT itself, it is crucial to have access to
23687 the contents of the tree nodes used to represent the program internally.
23688 But tree nodes are represented simply by an integer value (which in turn
23689 is an index into a table of nodes).
23690 Using the @code{print} command on a tree node would simply print this integer
23691 value, which is not very useful. But the PN routine (defined in file
23692 treepr.adb in the GNAT sources) takes a tree node as input, and displays
23693 a useful high level representation of the tree node, which includes the
23694 syntactic category of the node, its position in the source, the integers
23695 that denote descendant nodes and parent node, as well as varied
23696 semantic information. To study this example in more detail, you might want to
23697 look at the body of the PN procedure in the stated file.
23699 @node Using the Next Command in a Function
23700 @section Using the Next Command in a Function
23703 When you use the @code{next} command in a function, the current source
23704 location will advance to the next statement as usual. A special case
23705 arises in the case of a @code{return} statement.
23707 Part of the code for a return statement is the ``epilog'' of the function.
23708 This is the code that returns to the caller. There is only one copy of
23709 this epilog code, and it is typically associated with the last return
23710 statement in the function if there is more than one return. In some
23711 implementations, this epilog is associated with the first statement
23714 The result is that if you use the @code{next} command from a return
23715 statement that is not the last return statement of the function you
23716 may see a strange apparent jump to the last return statement or to
23717 the start of the function. You should simply ignore this odd jump.
23718 The value returned is always that from the first return statement
23719 that was stepped through.
23721 @node Ada Exceptions
23722 @section Breaking on Ada Exceptions
23726 You can set breakpoints that trip when your program raises
23727 selected exceptions.
23730 @item break exception
23731 Set a breakpoint that trips whenever (any task in the) program raises
23734 @item break exception @var{name}
23735 Set a breakpoint that trips whenever (any task in the) program raises
23736 the exception @var{name}.
23738 @item break exception unhandled
23739 Set a breakpoint that trips whenever (any task in the) program raises an
23740 exception for which there is no handler.
23742 @item info exceptions
23743 @itemx info exceptions @var{regexp}
23744 The @code{info exceptions} command permits the user to examine all defined
23745 exceptions within Ada programs. With a regular expression, @var{regexp}, as
23746 argument, prints out only those exceptions whose name matches @var{regexp}.
23754 @code{GDB} allows the following task-related commands:
23758 This command shows a list of current Ada tasks, as in the following example:
23765 ID TID P-ID Thread Pri State Name
23766 1 8088000 0 807e000 15 Child Activation Wait main_task
23767 2 80a4000 1 80ae000 15 Accept/Select Wait b
23768 3 809a800 1 80a4800 15 Child Activation Wait a
23769 * 4 80ae800 3 80b8000 15 Running c
23773 In this listing, the asterisk before the first task indicates it to be the
23774 currently running task. The first column lists the task ID that is used
23775 to refer to tasks in the following commands.
23777 @item break @var{linespec} task @var{taskid}
23778 @itemx break @var{linespec} task @var{taskid} if @dots{}
23779 @cindex Breakpoints and tasks
23780 These commands are like the @code{break @dots{} thread @dots{}}.
23781 @var{linespec} specifies source lines.
23783 Use the qualifier @samp{task @var{taskid}} with a breakpoint command
23784 to specify that you only want @code{GDB} to stop the program when a
23785 particular Ada task reaches this breakpoint. @var{taskid} is one of the
23786 numeric task identifiers assigned by @code{GDB}, shown in the first
23787 column of the @samp{info tasks} display.
23789 If you do not specify @samp{task @var{taskid}} when you set a
23790 breakpoint, the breakpoint applies to @emph{all} tasks of your
23793 You can use the @code{task} qualifier on conditional breakpoints as
23794 well; in this case, place @samp{task @var{taskid}} before the
23795 breakpoint condition (before the @code{if}).
23797 @item task @var{taskno}
23798 @cindex Task switching
23800 This command allows to switch to the task referred by @var{taskno}. In
23801 particular, This allows to browse the backtrace of the specified
23802 task. It is advised to switch back to the original task before
23803 continuing execution otherwise the scheduling of the program may be
23808 For more detailed information on the tasking support,
23809 see @ref{Top,, Debugging with GDB, gdb, Debugging with GDB}.
23811 @node Debugging Generic Units
23812 @section Debugging Generic Units
23813 @cindex Debugging Generic Units
23817 GNAT always uses code expansion for generic instantiation. This means that
23818 each time an instantiation occurs, a complete copy of the original code is
23819 made, with appropriate substitutions of formals by actuals.
23821 It is not possible to refer to the original generic entities in
23822 @code{GDB}, but it is always possible to debug a particular instance of
23823 a generic, by using the appropriate expanded names. For example, if we have
23825 @smallexample @c ada
23830 generic package k is
23831 procedure kp (v1 : in out integer);
23835 procedure kp (v1 : in out integer) is
23841 package k1 is new k;
23842 package k2 is new k;
23844 var : integer := 1;
23857 Then to break on a call to procedure kp in the k2 instance, simply
23861 (gdb) break g.k2.kp
23865 When the breakpoint occurs, you can step through the code of the
23866 instance in the normal manner and examine the values of local variables, as for
23869 @node GNAT Abnormal Termination or Failure to Terminate
23870 @section GNAT Abnormal Termination or Failure to Terminate
23871 @cindex GNAT Abnormal Termination or Failure to Terminate
23874 When presented with programs that contain serious errors in syntax
23876 GNAT may on rare occasions experience problems in operation, such
23878 segmentation fault or illegal memory access, raising an internal
23879 exception, terminating abnormally, or failing to terminate at all.
23880 In such cases, you can activate
23881 various features of GNAT that can help you pinpoint the construct in your
23882 program that is the likely source of the problem.
23884 The following strategies are presented in increasing order of
23885 difficulty, corresponding to your experience in using GNAT and your
23886 familiarity with compiler internals.
23890 Run @command{gcc} with the @option{-gnatf}. This first
23891 switch causes all errors on a given line to be reported. In its absence,
23892 only the first error on a line is displayed.
23894 The @option{-gnatdO} switch causes errors to be displayed as soon as they
23895 are encountered, rather than after compilation is terminated. If GNAT
23896 terminates prematurely or goes into an infinite loop, the last error
23897 message displayed may help to pinpoint the culprit.
23900 Run @command{gcc} with the @option{^-v (verbose)^/VERBOSE^} switch. In this
23901 mode, @command{gcc} produces ongoing information about the progress of the
23902 compilation and provides the name of each procedure as code is
23903 generated. This switch allows you to find which Ada procedure was being
23904 compiled when it encountered a code generation problem.
23907 @cindex @option{-gnatdc} switch
23908 Run @command{gcc} with the @option{-gnatdc} switch. This is a GNAT specific
23909 switch that does for the front-end what @option{^-v^VERBOSE^} does
23910 for the back end. The system prints the name of each unit,
23911 either a compilation unit or nested unit, as it is being analyzed.
23913 Finally, you can start
23914 @code{gdb} directly on the @code{gnat1} executable. @code{gnat1} is the
23915 front-end of GNAT, and can be run independently (normally it is just
23916 called from @command{gcc}). You can use @code{gdb} on @code{gnat1} as you
23917 would on a C program (but @pxref{The GNAT Debugger GDB} for caveats). The
23918 @code{where} command is the first line of attack; the variable
23919 @code{lineno} (seen by @code{print lineno}), used by the second phase of
23920 @code{gnat1} and by the @command{gcc} backend, indicates the source line at
23921 which the execution stopped, and @code{input_file name} indicates the name of
23925 @node Naming Conventions for GNAT Source Files
23926 @section Naming Conventions for GNAT Source Files
23929 In order to examine the workings of the GNAT system, the following
23930 brief description of its organization may be helpful:
23934 Files with prefix @file{^sc^SC^} contain the lexical scanner.
23937 All files prefixed with @file{^par^PAR^} are components of the parser. The
23938 numbers correspond to chapters of the Ada Reference Manual. For example,
23939 parsing of select statements can be found in @file{par-ch9.adb}.
23942 All files prefixed with @file{^sem^SEM^} perform semantic analysis. The
23943 numbers correspond to chapters of the Ada standard. For example, all
23944 issues involving context clauses can be found in @file{sem_ch10.adb}. In
23945 addition, some features of the language require sufficient special processing
23946 to justify their own semantic files: sem_aggr for aggregates, sem_disp for
23947 dynamic dispatching, etc.
23950 All files prefixed with @file{^exp^EXP^} perform normalization and
23951 expansion of the intermediate representation (abstract syntax tree, or AST).
23952 these files use the same numbering scheme as the parser and semantics files.
23953 For example, the construction of record initialization procedures is done in
23954 @file{exp_ch3.adb}.
23957 The files prefixed with @file{^bind^BIND^} implement the binder, which
23958 verifies the consistency of the compilation, determines an order of
23959 elaboration, and generates the bind file.
23962 The files @file{atree.ads} and @file{atree.adb} detail the low-level
23963 data structures used by the front-end.
23966 The files @file{sinfo.ads} and @file{sinfo.adb} detail the structure of
23967 the abstract syntax tree as produced by the parser.
23970 The files @file{einfo.ads} and @file{einfo.adb} detail the attributes of
23971 all entities, computed during semantic analysis.
23974 Library management issues are dealt with in files with prefix
23980 Ada files with the prefix @file{^a-^A-^} are children of @code{Ada}, as
23981 defined in Annex A.
23986 Files with prefix @file{^i-^I-^} are children of @code{Interfaces}, as
23987 defined in Annex B.
23991 Files with prefix @file{^s-^S-^} are children of @code{System}. This includes
23992 both language-defined children and GNAT run-time routines.
23996 Files with prefix @file{^g-^G-^} are children of @code{GNAT}. These are useful
23997 general-purpose packages, fully documented in their specs. All
23998 the other @file{.c} files are modifications of common @command{gcc} files.
24001 @node Getting Internal Debugging Information
24002 @section Getting Internal Debugging Information
24005 Most compilers have internal debugging switches and modes. GNAT
24006 does also, except GNAT internal debugging switches and modes are not
24007 secret. A summary and full description of all the compiler and binder
24008 debug flags are in the file @file{debug.adb}. You must obtain the
24009 sources of the compiler to see the full detailed effects of these flags.
24011 The switches that print the source of the program (reconstructed from
24012 the internal tree) are of general interest for user programs, as are the
24014 the full internal tree, and the entity table (the symbol table
24015 information). The reconstructed source provides a readable version of the
24016 program after the front-end has completed analysis and expansion,
24017 and is useful when studying the performance of specific constructs.
24018 For example, constraint checks are indicated, complex aggregates
24019 are replaced with loops and assignments, and tasking primitives
24020 are replaced with run-time calls.
24022 @node Stack Traceback
24023 @section Stack Traceback
24025 @cindex stack traceback
24026 @cindex stack unwinding
24029 Traceback is a mechanism to display the sequence of subprogram calls that
24030 leads to a specified execution point in a program. Often (but not always)
24031 the execution point is an instruction at which an exception has been raised.
24032 This mechanism is also known as @i{stack unwinding} because it obtains
24033 its information by scanning the run-time stack and recovering the activation
24034 records of all active subprograms. Stack unwinding is one of the most
24035 important tools for program debugging.
24037 The first entry stored in traceback corresponds to the deepest calling level,
24038 that is to say the subprogram currently executing the instruction
24039 from which we want to obtain the traceback.
24041 Note that there is no runtime performance penalty when stack traceback
24042 is enabled, and no exception is raised during program execution.
24045 * Non-Symbolic Traceback::
24046 * Symbolic Traceback::
24049 @node Non-Symbolic Traceback
24050 @subsection Non-Symbolic Traceback
24051 @cindex traceback, non-symbolic
24054 Note: this feature is not supported on all platforms. See
24055 @file{GNAT.Traceback spec in g-traceb.ads} for a complete list of supported
24059 * Tracebacks From an Unhandled Exception::
24060 * Tracebacks From Exception Occurrences (non-symbolic)::
24061 * Tracebacks From Anywhere in a Program (non-symbolic)::
24064 @node Tracebacks From an Unhandled Exception
24065 @subsubsection Tracebacks From an Unhandled Exception
24068 A runtime non-symbolic traceback is a list of addresses of call instructions.
24069 To enable this feature you must use the @option{-E}
24070 @code{gnatbind}'s option. With this option a stack traceback is stored as part
24071 of exception information. You can retrieve this information using the
24072 @code{addr2line} tool.
24074 Here is a simple example:
24076 @smallexample @c ada
24082 raise Constraint_Error;
24097 $ gnatmake stb -bargs -E
24100 Execution terminated by unhandled exception
24101 Exception name: CONSTRAINT_ERROR
24103 Call stack traceback locations:
24104 0x401373 0x40138b 0x40139c 0x401335 0x4011c4 0x4011f1 0x77e892a4
24108 As we see the traceback lists a sequence of addresses for the unhandled
24109 exception @code{CONSTRAINT_ERROR} raised in procedure P1. It is easy to
24110 guess that this exception come from procedure P1. To translate these
24111 addresses into the source lines where the calls appear, the
24112 @code{addr2line} tool, described below, is invaluable. The use of this tool
24113 requires the program to be compiled with debug information.
24116 $ gnatmake -g stb -bargs -E
24119 Execution terminated by unhandled exception
24120 Exception name: CONSTRAINT_ERROR
24122 Call stack traceback locations:
24123 0x401373 0x40138b 0x40139c 0x401335 0x4011c4 0x4011f1 0x77e892a4
24125 $ addr2line --exe=stb 0x401373 0x40138b 0x40139c 0x401335 0x4011c4
24126 0x4011f1 0x77e892a4
24128 00401373 at d:/stb/stb.adb:5
24129 0040138B at d:/stb/stb.adb:10
24130 0040139C at d:/stb/stb.adb:14
24131 00401335 at d:/stb/b~stb.adb:104
24132 004011C4 at /build/@dots{}/crt1.c:200
24133 004011F1 at /build/@dots{}/crt1.c:222
24134 77E892A4 in ?? at ??:0
24138 The @code{addr2line} tool has several other useful options:
24142 to get the function name corresponding to any location
24144 @item --demangle=gnat
24145 to use the gnat decoding mode for the function names. Note that
24146 for binutils version 2.9.x the option is simply @option{--demangle}.
24150 $ addr2line --exe=stb --functions --demangle=gnat 0x401373 0x40138b
24151 0x40139c 0x401335 0x4011c4 0x4011f1
24153 00401373 in stb.p1 at d:/stb/stb.adb:5
24154 0040138B in stb.p2 at d:/stb/stb.adb:10
24155 0040139C in stb at d:/stb/stb.adb:14
24156 00401335 in main at d:/stb/b~stb.adb:104
24157 004011C4 in <__mingw_CRTStartup> at /build/@dots{}/crt1.c:200
24158 004011F1 in <mainCRTStartup> at /build/@dots{}/crt1.c:222
24162 From this traceback we can see that the exception was raised in
24163 @file{stb.adb} at line 5, which was reached from a procedure call in
24164 @file{stb.adb} at line 10, and so on. The @file{b~std.adb} is the binder file,
24165 which contains the call to the main program.
24166 @xref{Running gnatbind}. The remaining entries are assorted runtime routines,
24167 and the output will vary from platform to platform.
24169 It is also possible to use @code{GDB} with these traceback addresses to debug
24170 the program. For example, we can break at a given code location, as reported
24171 in the stack traceback:
24177 Furthermore, this feature is not implemented inside Windows DLL. Only
24178 the non-symbolic traceback is reported in this case.
24181 (gdb) break *0x401373
24182 Breakpoint 1 at 0x401373: file stb.adb, line 5.
24186 It is important to note that the stack traceback addresses
24187 do not change when debug information is included. This is particularly useful
24188 because it makes it possible to release software without debug information (to
24189 minimize object size), get a field report that includes a stack traceback
24190 whenever an internal bug occurs, and then be able to retrieve the sequence
24191 of calls with the same program compiled with debug information.
24193 @node Tracebacks From Exception Occurrences (non-symbolic)
24194 @subsubsection Tracebacks From Exception Occurrences
24197 Non-symbolic tracebacks are obtained by using the @option{-E} binder argument.
24198 The stack traceback is attached to the exception information string, and can
24199 be retrieved in an exception handler within the Ada program, by means of the
24200 Ada facilities defined in @code{Ada.Exceptions}. Here is a simple example:
24202 @smallexample @c ada
24204 with Ada.Exceptions;
24209 use Ada.Exceptions;
24217 Text_IO.Put_Line (Exception_Information (E));
24231 This program will output:
24236 Exception name: CONSTRAINT_ERROR
24237 Message: stb.adb:12
24238 Call stack traceback locations:
24239 0x4015e4 0x401633 0x401644 0x401461 0x4011c4 0x4011f1 0x77e892a4
24242 @node Tracebacks From Anywhere in a Program (non-symbolic)
24243 @subsubsection Tracebacks From Anywhere in a Program
24246 It is also possible to retrieve a stack traceback from anywhere in a
24247 program. For this you need to
24248 use the @code{GNAT.Traceback} API. This package includes a procedure called
24249 @code{Call_Chain} that computes a complete stack traceback, as well as useful
24250 display procedures described below. It is not necessary to use the
24251 @option{-E gnatbind} option in this case, because the stack traceback mechanism
24252 is invoked explicitly.
24255 In the following example we compute a traceback at a specific location in
24256 the program, and we display it using @code{GNAT.Debug_Utilities.Image} to
24257 convert addresses to strings:
24259 @smallexample @c ada
24261 with GNAT.Traceback;
24262 with GNAT.Debug_Utilities;
24268 use GNAT.Traceback;
24271 TB : Tracebacks_Array (1 .. 10);
24272 -- We are asking for a maximum of 10 stack frames.
24274 -- Len will receive the actual number of stack frames returned.
24276 Call_Chain (TB, Len);
24278 Text_IO.Put ("In STB.P1 : ");
24280 for K in 1 .. Len loop
24281 Text_IO.Put (Debug_Utilities.Image (TB (K)));
24302 In STB.P1 : 16#0040_F1E4# 16#0040_14F2# 16#0040_170B# 16#0040_171C#
24303 16#0040_1461# 16#0040_11C4# 16#0040_11F1# 16#77E8_92A4#
24307 You can then get further information by invoking the @code{addr2line}
24308 tool as described earlier (note that the hexadecimal addresses
24309 need to be specified in C format, with a leading ``0x'').
24311 @node Symbolic Traceback
24312 @subsection Symbolic Traceback
24313 @cindex traceback, symbolic
24316 A symbolic traceback is a stack traceback in which procedure names are
24317 associated with each code location.
24320 Note that this feature is not supported on all platforms. See
24321 @file{GNAT.Traceback.Symbolic spec in g-trasym.ads} for a complete
24322 list of currently supported platforms.
24325 Note that the symbolic traceback requires that the program be compiled
24326 with debug information. If it is not compiled with debug information
24327 only the non-symbolic information will be valid.
24330 * Tracebacks From Exception Occurrences (symbolic)::
24331 * Tracebacks From Anywhere in a Program (symbolic)::
24334 @node Tracebacks From Exception Occurrences (symbolic)
24335 @subsubsection Tracebacks From Exception Occurrences
24337 @smallexample @c ada
24339 with GNAT.Traceback.Symbolic;
24345 raise Constraint_Error;
24362 Ada.Text_IO.Put_Line (GNAT.Traceback.Symbolic.Symbolic_Traceback (E));
24367 $ gnatmake -g .\stb -bargs -E -largs -lgnat -laddr2line -lintl
24370 0040149F in stb.p1 at stb.adb:8
24371 004014B7 in stb.p2 at stb.adb:13
24372 004014CF in stb.p3 at stb.adb:18
24373 004015DD in ada.stb at stb.adb:22
24374 00401461 in main at b~stb.adb:168
24375 004011C4 in __mingw_CRTStartup at crt1.c:200
24376 004011F1 in mainCRTStartup at crt1.c:222
24377 77E892A4 in ?? at ??:0
24381 In the above example the ``.\'' syntax in the @command{gnatmake} command
24382 is currently required by @command{addr2line} for files that are in
24383 the current working directory.
24384 Moreover, the exact sequence of linker options may vary from platform
24386 The above @option{-largs} section is for Windows platforms. By contrast,
24387 under Unix there is no need for the @option{-largs} section.
24388 Differences across platforms are due to details of linker implementation.
24390 @node Tracebacks From Anywhere in a Program (symbolic)
24391 @subsubsection Tracebacks From Anywhere in a Program
24394 It is possible to get a symbolic stack traceback
24395 from anywhere in a program, just as for non-symbolic tracebacks.
24396 The first step is to obtain a non-symbolic
24397 traceback, and then call @code{Symbolic_Traceback} to compute the symbolic
24398 information. Here is an example:
24400 @smallexample @c ada
24402 with GNAT.Traceback;
24403 with GNAT.Traceback.Symbolic;
24408 use GNAT.Traceback;
24409 use GNAT.Traceback.Symbolic;
24412 TB : Tracebacks_Array (1 .. 10);
24413 -- We are asking for a maximum of 10 stack frames.
24415 -- Len will receive the actual number of stack frames returned.
24417 Call_Chain (TB, Len);
24418 Text_IO.Put_Line (Symbolic_Traceback (TB (1 .. Len)));
24431 @c ******************************
24433 @node Compatibility with HP Ada
24434 @chapter Compatibility with HP Ada
24435 @cindex Compatibility
24440 @cindex Compatibility between GNAT and HP Ada
24441 This chapter compares HP Ada (formerly known as ``DEC Ada'')
24442 for OpenVMS Alpha and GNAT for OpenVMS for Alpha and for I64.
24443 GNAT is highly compatible
24444 with HP Ada, and it should generally be straightforward to port code
24445 from the HP Ada environment to GNAT. However, there are a few language
24446 and implementation differences of which the user must be aware. These
24447 differences are discussed in this chapter. In
24448 addition, the operating environment and command structure for the
24449 compiler are different, and these differences are also discussed.
24451 For further details on these and other compatibility issues,
24452 see Appendix E of the HP publication
24453 @cite{HP Ada, Technical Overview and Comparison on HP Platforms}.
24455 Except where otherwise indicated, the description of GNAT for OpenVMS
24456 applies to both the Alpha and I64 platforms.
24458 For information on porting Ada code from GNAT on Alpha OpenVMS to GNAT on
24459 I64 OpenVMS, see @ref{Transitioning to 64-Bit GNAT for OpenVMS}.
24461 The discussion in this chapter addresses specifically the implementation
24462 of Ada 83 for HP OpenVMS Alpha Systems. In cases where the implementation
24463 of HP Ada differs between OpenVMS Alpha Systems and OpenVMS VAX Systems,
24464 GNAT always follows the Alpha implementation.
24466 For GNAT running on other than VMS systems, all the HP Ada 83 pragmas and
24467 attributes are recognized, although only a subset of them can sensibly
24468 be implemented. The description of pragmas in
24469 @xref{Implementation Defined Pragmas,,, gnat_rm, GNAT Reference Manual}
24470 indicates whether or not they are applicable to non-VMS systems.
24473 * Ada Language Compatibility::
24474 * Differences in the Definition of Package System::
24475 * Language-Related Features::
24476 * The Package STANDARD::
24477 * The Package SYSTEM::
24478 * Tasking and Task-Related Features::
24479 * Pragmas and Pragma-Related Features::
24480 * Library of Predefined Units::
24482 * Main Program Definition::
24483 * Implementation-Defined Attributes::
24484 * Compiler and Run-Time Interfacing::
24485 * Program Compilation and Library Management::
24487 * Implementation Limits::
24488 * Tools and Utilities::
24491 @node Ada Language Compatibility
24492 @section Ada Language Compatibility
24495 GNAT handles Ada 95 and Ada 2005 as well as Ada 83, whereas HP Ada is only
24496 for Ada 83. Ada 95 and Ada 2005 are almost completely upwards compatible
24497 with Ada 83, and therefore Ada 83 programs will compile
24498 and run under GNAT with
24499 no changes or only minor changes. The @cite{Annotated Ada Reference Manual}
24500 provides details on specific incompatibilities.
24502 GNAT provides the switch @option{/83} on the @command{GNAT COMPILE} command,
24503 as well as the pragma @code{ADA_83}, to force the compiler to
24504 operate in Ada 83 mode. This mode does not guarantee complete
24505 conformance to Ada 83, but in practice is sufficient to
24506 eliminate most sources of incompatibilities.
24507 In particular, it eliminates the recognition of the
24508 additional Ada 95 and Ada 2005 keywords, so that their use as identifiers
24509 in Ada 83 programs is legal, and handles the cases of packages
24510 with optional bodies, and generics that instantiate unconstrained
24511 types without the use of @code{(<>)}.
24513 @node Differences in the Definition of Package System
24514 @section Differences in the Definition of Package @code{System}
24517 An Ada compiler is allowed to add
24518 implementation-dependent declarations to package @code{System}.
24520 GNAT does not take advantage of this permission, and the version of
24521 @code{System} provided by GNAT exactly matches that defined in the Ada
24524 However, HP Ada adds an extensive set of declarations to package
24526 as fully documented in the HP Ada manuals. To minimize changes required
24527 for programs that make use of these extensions, GNAT provides the pragma
24528 @code{Extend_System} for extending the definition of package System. By using:
24529 @cindex pragma @code{Extend_System}
24530 @cindex @code{Extend_System} pragma
24532 @smallexample @c ada
24535 pragma Extend_System (Aux_DEC);
24541 the set of definitions in @code{System} is extended to include those in
24542 package @code{System.Aux_DEC}.
24543 @cindex @code{System.Aux_DEC} package
24544 @cindex @code{Aux_DEC} package (child of @code{System})
24545 These definitions are incorporated directly into package @code{System},
24546 as though they had been declared there. For a
24547 list of the declarations added, see the spec of this package,
24548 which can be found in the file @file{s-auxdec.ads} in the GNAT library.
24549 @cindex @file{s-auxdec.ads} file
24550 The pragma @code{Extend_System} is a configuration pragma, which means that
24551 it can be placed in the file @file{gnat.adc}, so that it will automatically
24552 apply to all subsequent compilations. See @ref{Configuration Pragmas},
24553 for further details.
24555 An alternative approach that avoids the use of the non-standard
24556 @code{Extend_System} pragma is to add a context clause to the unit that
24557 references these facilities:
24559 @smallexample @c ada
24561 with System.Aux_DEC;
24562 use System.Aux_DEC;
24567 The effect is not quite semantically identical to incorporating
24568 the declarations directly into package @code{System},
24569 but most programs will not notice a difference
24570 unless they use prefix notation (e.g.@: @code{System.Integer_8})
24571 to reference the entities directly in package @code{System}.
24572 For units containing such references,
24573 the prefixes must either be removed, or the pragma @code{Extend_System}
24576 @node Language-Related Features
24577 @section Language-Related Features
24580 The following sections highlight differences in types,
24581 representations of types, operations, alignment, and
24585 * Integer Types and Representations::
24586 * Floating-Point Types and Representations::
24587 * Pragmas Float_Representation and Long_Float::
24588 * Fixed-Point Types and Representations::
24589 * Record and Array Component Alignment::
24590 * Address Clauses::
24591 * Other Representation Clauses::
24594 @node Integer Types and Representations
24595 @subsection Integer Types and Representations
24598 The set of predefined integer types is identical in HP Ada and GNAT.
24599 Furthermore the representation of these integer types is also identical,
24600 including the capability of size clauses forcing biased representation.
24603 HP Ada for OpenVMS Alpha systems has defined the
24604 following additional integer types in package @code{System}:
24621 @code{LARGEST_INTEGER}
24625 In GNAT, the first four of these types may be obtained from the
24626 standard Ada package @code{Interfaces}.
24627 Alternatively, by use of the pragma @code{Extend_System}, identical
24628 declarations can be referenced directly in package @code{System}.
24629 On both GNAT and HP Ada, the maximum integer size is 64 bits.
24631 @node Floating-Point Types and Representations
24632 @subsection Floating-Point Types and Representations
24633 @cindex Floating-Point types
24636 The set of predefined floating-point types is identical in HP Ada and GNAT.
24637 Furthermore the representation of these floating-point
24638 types is also identical. One important difference is that the default
24639 representation for HP Ada is @code{VAX_Float}, but the default representation
24642 Specific types may be declared to be @code{VAX_Float} or IEEE, using the
24643 pragma @code{Float_Representation} as described in the HP Ada
24645 For example, the declarations:
24647 @smallexample @c ada
24649 type F_Float is digits 6;
24650 pragma Float_Representation (VAX_Float, F_Float);
24655 declares a type @code{F_Float} that will be represented in @code{VAX_Float}
24657 This set of declarations actually appears in @code{System.Aux_DEC},
24659 the full set of additional floating-point declarations provided in
24660 the HP Ada version of package @code{System}.
24661 This and similar declarations may be accessed in a user program
24662 by using pragma @code{Extend_System}. The use of this
24663 pragma, and the related pragma @code{Long_Float} is described in further
24664 detail in the following section.
24666 @node Pragmas Float_Representation and Long_Float
24667 @subsection Pragmas @code{Float_Representation} and @code{Long_Float}
24670 HP Ada provides the pragma @code{Float_Representation}, which
24671 acts as a program library switch to allow control over
24672 the internal representation chosen for the predefined
24673 floating-point types declared in the package @code{Standard}.
24674 The format of this pragma is as follows:
24676 @smallexample @c ada
24678 pragma Float_Representation(VAX_Float | IEEE_Float);
24683 This pragma controls the representation of floating-point
24688 @code{VAX_Float} specifies that floating-point
24689 types are represented by default with the VAX system hardware types
24690 @code{F-floating}, @code{D-floating}, @code{G-floating}.
24691 Note that the @code{H-floating}
24692 type was available only on VAX systems, and is not available
24693 in either HP Ada or GNAT.
24696 @code{IEEE_Float} specifies that floating-point
24697 types are represented by default with the IEEE single and
24698 double floating-point types.
24702 GNAT provides an identical implementation of the pragma
24703 @code{Float_Representation}, except that it functions as a
24704 configuration pragma. Note that the
24705 notion of configuration pragma corresponds closely to the
24706 HP Ada notion of a program library switch.
24708 When no pragma is used in GNAT, the default is @code{IEEE_Float},
24710 from HP Ada 83, where the default is @code{VAX_Float}. In addition, the
24711 predefined libraries in GNAT are built using @code{IEEE_Float}, so it is not
24712 advisable to change the format of numbers passed to standard library
24713 routines, and if necessary explicit type conversions may be needed.
24715 The use of @code{IEEE_Float} is recommended in GNAT since it is more
24716 efficient, and (given that it conforms to an international standard)
24717 potentially more portable.
24718 The situation in which @code{VAX_Float} may be useful is in interfacing
24719 to existing code and data that expect the use of @code{VAX_Float}.
24720 In such a situation use the predefined @code{VAX_Float}
24721 types in package @code{System}, as extended by
24722 @code{Extend_System}. For example, use @code{System.F_Float}
24723 to specify the 32-bit @code{F-Float} format.
24726 On OpenVMS systems, HP Ada provides the pragma @code{Long_Float}
24727 to allow control over the internal representation chosen
24728 for the predefined type @code{Long_Float} and for floating-point
24729 type declarations with digits specified in the range 7 .. 15.
24730 The format of this pragma is as follows:
24732 @smallexample @c ada
24734 pragma Long_Float (D_FLOAT | G_FLOAT);
24738 @node Fixed-Point Types and Representations
24739 @subsection Fixed-Point Types and Representations
24742 On HP Ada for OpenVMS Alpha systems, rounding is
24743 away from zero for both positive and negative numbers.
24744 Therefore, @code{+0.5} rounds to @code{1},
24745 and @code{-0.5} rounds to @code{-1}.
24747 On GNAT the results of operations
24748 on fixed-point types are in accordance with the Ada
24749 rules. In particular, results of operations on decimal
24750 fixed-point types are truncated.
24752 @node Record and Array Component Alignment
24753 @subsection Record and Array Component Alignment
24756 On HP Ada for OpenVMS Alpha, all non-composite components
24757 are aligned on natural boundaries. For example, 1-byte
24758 components are aligned on byte boundaries, 2-byte
24759 components on 2-byte boundaries, 4-byte components on 4-byte
24760 byte boundaries, and so on. The OpenVMS Alpha hardware
24761 runs more efficiently with naturally aligned data.
24763 On GNAT, alignment rules are compatible
24764 with HP Ada for OpenVMS Alpha.
24766 @node Address Clauses
24767 @subsection Address Clauses
24770 In HP Ada and GNAT, address clauses are supported for
24771 objects and imported subprograms.
24772 The predefined type @code{System.Address} is a private type
24773 in both compilers on Alpha OpenVMS, with the same representation
24774 (it is simply a machine pointer). Addition, subtraction, and comparison
24775 operations are available in the standard Ada package
24776 @code{System.Storage_Elements}, or in package @code{System}
24777 if it is extended to include @code{System.Aux_DEC} using a
24778 pragma @code{Extend_System} as previously described.
24780 Note that code that @code{with}'s both this extended package @code{System}
24781 and the package @code{System.Storage_Elements} should not @code{use}
24782 both packages, or ambiguities will result. In general it is better
24783 not to mix these two sets of facilities. The Ada package was
24784 designed specifically to provide the kind of features that HP Ada
24785 adds directly to package @code{System}.
24787 The type @code{System.Address} is a 64-bit integer type in GNAT for
24788 I64 OpenVMS. For more information,
24789 see @ref{Transitioning to 64-Bit GNAT for OpenVMS}.
24791 GNAT is compatible with HP Ada in its handling of address
24792 clauses, except for some limitations in
24793 the form of address clauses for composite objects with
24794 initialization. Such address clauses are easily replaced
24795 by the use of an explicitly-defined constant as described
24796 in the Ada Reference Manual (13.1(22)). For example, the sequence
24799 @smallexample @c ada
24801 X, Y : Integer := Init_Func;
24802 Q : String (X .. Y) := "abc";
24804 for Q'Address use Compute_Address;
24809 will be rejected by GNAT, since the address cannot be computed at the time
24810 that @code{Q} is declared. To achieve the intended effect, write instead:
24812 @smallexample @c ada
24815 X, Y : Integer := Init_Func;
24816 Q_Address : constant Address := Compute_Address;
24817 Q : String (X .. Y) := "abc";
24819 for Q'Address use Q_Address;
24825 which will be accepted by GNAT (and other Ada compilers), and is also
24826 compatible with Ada 83. A fuller description of the restrictions
24827 on address specifications is found in @ref{Top, GNAT Reference Manual,
24828 About This Guide, gnat_rm, GNAT Reference Manual}.
24830 @node Other Representation Clauses
24831 @subsection Other Representation Clauses
24834 GNAT implements in a compatible manner all the representation
24835 clauses supported by HP Ada. In addition, GNAT
24836 implements the representation clause forms that were introduced in Ada 95,
24837 including @code{COMPONENT_SIZE} and @code{SIZE} clauses for objects.
24839 @node The Package STANDARD
24840 @section The Package @code{STANDARD}
24843 The package @code{STANDARD}, as implemented by HP Ada, is fully
24844 described in the @cite{Ada Reference Manual} and in the
24845 @cite{HP Ada Language Reference Manual}. As implemented by GNAT, the
24846 package @code{STANDARD} is described in the @cite{Ada Reference Manual}.
24848 In addition, HP Ada supports the Latin-1 character set in
24849 the type @code{CHARACTER}. GNAT supports the Latin-1 character set
24850 in the type @code{CHARACTER} and also Unicode (ISO 10646 BMP) in
24851 the type @code{WIDE_CHARACTER}.
24853 The floating-point types supported by GNAT are those
24854 supported by HP Ada, but the defaults are different, and are controlled by
24855 pragmas. See @ref{Floating-Point Types and Representations}, for details.
24857 @node The Package SYSTEM
24858 @section The Package @code{SYSTEM}
24861 HP Ada provides a specific version of the package
24862 @code{SYSTEM} for each platform on which the language is implemented.
24863 For the complete spec of the package @code{SYSTEM}, see
24864 Appendix F of the @cite{HP Ada Language Reference Manual}.
24866 On HP Ada, the package @code{SYSTEM} includes the following conversion
24869 @item @code{TO_ADDRESS(INTEGER)}
24871 @item @code{TO_ADDRESS(UNSIGNED_LONGWORD)}
24873 @item @code{TO_ADDRESS(}@i{universal_integer}@code{)}
24875 @item @code{TO_INTEGER(ADDRESS)}
24877 @item @code{TO_UNSIGNED_LONGWORD(ADDRESS)}
24879 @item Function @code{IMPORT_VALUE return UNSIGNED_LONGWORD} and the
24880 functions @code{IMPORT_ADDRESS} and @code{IMPORT_LARGEST_VALUE}
24884 By default, GNAT supplies a version of @code{SYSTEM} that matches
24885 the definition given in the @cite{Ada Reference Manual}.
24887 is a subset of the HP system definitions, which is as
24888 close as possible to the original definitions. The only difference
24889 is that the definition of @code{SYSTEM_NAME} is different:
24891 @smallexample @c ada
24893 type Name is (SYSTEM_NAME_GNAT);
24894 System_Name : constant Name := SYSTEM_NAME_GNAT;
24899 Also, GNAT adds the Ada declarations for
24900 @code{BIT_ORDER} and @code{DEFAULT_BIT_ORDER}.
24902 However, the use of the following pragma causes GNAT
24903 to extend the definition of package @code{SYSTEM} so that it
24904 encompasses the full set of HP-specific extensions,
24905 including the functions listed above:
24907 @smallexample @c ada
24909 pragma Extend_System (Aux_DEC);
24914 The pragma @code{Extend_System} is a configuration pragma that
24915 is most conveniently placed in the @file{gnat.adc} file. @xref{Pragma
24916 Extend_System,,, gnat_rm, GNAT Reference Manual} for further details.
24918 HP Ada does not allow the recompilation of the package
24919 @code{SYSTEM}. Instead HP Ada provides several pragmas
24920 (@code{SYSTEM_NAME}, @code{STORAGE_UNIT}, and @code{MEMORY_SIZE})
24921 to modify values in the package @code{SYSTEM}.
24922 On OpenVMS Alpha systems, the pragma
24923 @code{SYSTEM_NAME} takes the enumeration literal @code{OPENVMS_AXP} as
24924 its single argument.
24926 GNAT does permit the recompilation of package @code{SYSTEM} using
24927 the special switch @option{-gnatg}, and this switch can be used if
24928 it is necessary to modify the definitions in @code{SYSTEM}. GNAT does
24929 not permit the specification of @code{SYSTEM_NAME}, @code{STORAGE_UNIT}
24930 or @code{MEMORY_SIZE} by any other means.
24932 On GNAT systems, the pragma @code{SYSTEM_NAME} takes the
24933 enumeration literal @code{SYSTEM_NAME_GNAT}.
24935 The definitions provided by the use of
24937 @smallexample @c ada
24938 pragma Extend_System (AUX_Dec);
24942 are virtually identical to those provided by the HP Ada 83 package
24943 @code{SYSTEM}. One important difference is that the name of the
24945 function for type @code{UNSIGNED_LONGWORD} is changed to
24946 @code{TO_ADDRESS_LONG}.
24947 @xref{Address Clauses,,, gnat_rm, GNAT Reference Manual} for a
24948 discussion of why this change was necessary.
24951 The version of @code{TO_ADDRESS} taking a @i{universal_integer} argument
24953 an extension to Ada 83 not strictly compatible with the reference manual.
24954 GNAT, in order to be exactly compatible with the standard,
24955 does not provide this capability. In HP Ada 83, the
24956 point of this definition is to deal with a call like:
24958 @smallexample @c ada
24959 TO_ADDRESS (16#12777#);
24963 Normally, according to Ada 83 semantics, one would expect this to be
24964 ambiguous, since it matches both the @code{INTEGER} and
24965 @code{UNSIGNED_LONGWORD} forms of @code{TO_ADDRESS}.
24966 However, in HP Ada 83, there is no ambiguity, since the
24967 definition using @i{universal_integer} takes precedence.
24969 In GNAT, since the version with @i{universal_integer} cannot be supplied,
24971 not possible to be 100% compatible. Since there are many programs using
24972 numeric constants for the argument to @code{TO_ADDRESS}, the decision in
24974 to change the name of the function in the @code{UNSIGNED_LONGWORD} case,
24975 so the declarations provided in the GNAT version of @code{AUX_Dec} are:
24977 @smallexample @c ada
24978 function To_Address (X : Integer) return Address;
24979 pragma Pure_Function (To_Address);
24981 function To_Address_Long (X : Unsigned_Longword) return Address;
24982 pragma Pure_Function (To_Address_Long);
24986 This means that programs using @code{TO_ADDRESS} for
24987 @code{UNSIGNED_LONGWORD} must change the name to @code{TO_ADDRESS_LONG}.
24989 @node Tasking and Task-Related Features
24990 @section Tasking and Task-Related Features
24993 This section compares the treatment of tasking in GNAT
24994 and in HP Ada for OpenVMS Alpha.
24995 The GNAT description applies to both Alpha and I64 OpenVMS.
24996 For detailed information on tasking in
24997 HP Ada, see the @cite{HP Ada Language Reference Manual} and the
24998 relevant run-time reference manual.
25001 * Implementation of Tasks in HP Ada for OpenVMS Alpha Systems::
25002 * Assigning Task IDs::
25003 * Task IDs and Delays::
25004 * Task-Related Pragmas::
25005 * Scheduling and Task Priority::
25007 * External Interrupts::
25010 @node Implementation of Tasks in HP Ada for OpenVMS Alpha Systems
25011 @subsection Implementation of Tasks in HP Ada for OpenVMS Alpha Systems
25014 On OpenVMS Alpha systems, each Ada task (except a passive
25015 task) is implemented as a single stream of execution
25016 that is created and managed by the kernel. On these
25017 systems, HP Ada tasking support is based on DECthreads,
25018 an implementation of the POSIX standard for threads.
25020 Also, on OpenVMS Alpha systems, HP Ada tasks and foreign
25021 code that calls DECthreads routines can be used together.
25022 The interaction between Ada tasks and DECthreads routines
25023 can have some benefits. For example when on OpenVMS Alpha,
25024 HP Ada can call C code that is already threaded.
25026 GNAT uses the facilities of DECthreads,
25027 and Ada tasks are mapped to threads.
25029 @node Assigning Task IDs
25030 @subsection Assigning Task IDs
25033 The HP Ada Run-Time Library always assigns @code{%TASK 1} to
25034 the environment task that executes the main program. On
25035 OpenVMS Alpha systems, @code{%TASK 0} is often used for tasks
25036 that have been created but are not yet activated.
25038 On OpenVMS Alpha systems, task IDs are assigned at
25039 activation. On GNAT systems, task IDs are also assigned at
25040 task creation but do not have the same form or values as
25041 task ID values in HP Ada. There is no null task, and the
25042 environment task does not have a specific task ID value.
25044 @node Task IDs and Delays
25045 @subsection Task IDs and Delays
25048 On OpenVMS Alpha systems, tasking delays are implemented
25049 using Timer System Services. The Task ID is used for the
25050 identification of the timer request (the @code{REQIDT} parameter).
25051 If Timers are used in the application take care not to use
25052 @code{0} for the identification, because cancelling such a timer
25053 will cancel all timers and may lead to unpredictable results.
25055 @node Task-Related Pragmas
25056 @subsection Task-Related Pragmas
25059 Ada supplies the pragma @code{TASK_STORAGE}, which allows
25060 specification of the size of the guard area for a task
25061 stack. (The guard area forms an area of memory that has no
25062 read or write access and thus helps in the detection of
25063 stack overflow.) On OpenVMS Alpha systems, if the pragma
25064 @code{TASK_STORAGE} specifies a value of zero, a minimal guard
25065 area is created. In the absence of a pragma @code{TASK_STORAGE},
25066 a default guard area is created.
25068 GNAT supplies the following task-related pragmas:
25071 @item @code{TASK_INFO}
25073 This pragma appears within a task definition and
25074 applies to the task in which it appears. The argument
25075 must be of type @code{SYSTEM.TASK_INFO.TASK_INFO_TYPE}.
25077 @item @code{TASK_STORAGE}
25079 GNAT implements pragma @code{TASK_STORAGE} in the same way as HP Ada.
25080 Both HP Ada and GNAT supply the pragmas @code{PASSIVE},
25081 @code{SUPPRESS}, and @code{VOLATILE}.
25083 @node Scheduling and Task Priority
25084 @subsection Scheduling and Task Priority
25087 HP Ada implements the Ada language requirement that
25088 when two tasks are eligible for execution and they have
25089 different priorities, the lower priority task does not
25090 execute while the higher priority task is waiting. The HP
25091 Ada Run-Time Library keeps a task running until either the
25092 task is suspended or a higher priority task becomes ready.
25094 On OpenVMS Alpha systems, the default strategy is round-
25095 robin with preemption. Tasks of equal priority take turns
25096 at the processor. A task is run for a certain period of
25097 time and then placed at the tail of the ready queue for
25098 its priority level.
25100 HP Ada provides the implementation-defined pragma @code{TIME_SLICE},
25101 which can be used to enable or disable round-robin
25102 scheduling of tasks with the same priority.
25103 See the relevant HP Ada run-time reference manual for
25104 information on using the pragmas to control HP Ada task
25107 GNAT follows the scheduling rules of Annex D (Real-Time
25108 Annex) of the @cite{Ada Reference Manual}. In general, this
25109 scheduling strategy is fully compatible with HP Ada
25110 although it provides some additional constraints (as
25111 fully documented in Annex D).
25112 GNAT implements time slicing control in a manner compatible with
25113 HP Ada 83, by means of the pragma @code{Time_Slice}, whose semantics
25114 are identical to the HP Ada 83 pragma of the same name.
25115 Note that it is not possible to mix GNAT tasking and
25116 HP Ada 83 tasking in the same program, since the two run-time
25117 libraries are not compatible.
25119 @node The Task Stack
25120 @subsection The Task Stack
25123 In HP Ada, a task stack is allocated each time a
25124 non-passive task is activated. As soon as the task is
25125 terminated, the storage for the task stack is deallocated.
25126 If you specify a size of zero (bytes) with @code{T'STORAGE_SIZE},
25127 a default stack size is used. Also, regardless of the size
25128 specified, some additional space is allocated for task
25129 management purposes. On OpenVMS Alpha systems, at least
25130 one page is allocated.
25132 GNAT handles task stacks in a similar manner. In accordance with
25133 the Ada rules, it provides the pragma @code{STORAGE_SIZE} as
25134 an alternative method for controlling the task stack size.
25135 The specification of the attribute @code{T'STORAGE_SIZE} is also
25136 supported in a manner compatible with HP Ada.
25138 @node External Interrupts
25139 @subsection External Interrupts
25142 On HP Ada, external interrupts can be associated with task entries.
25143 GNAT is compatible with HP Ada in its handling of external interrupts.
25145 @node Pragmas and Pragma-Related Features
25146 @section Pragmas and Pragma-Related Features
25149 Both HP Ada and GNAT supply all language-defined pragmas
25150 as specified by the Ada 83 standard. GNAT also supplies all
25151 language-defined pragmas introduced by Ada 95 and Ada 2005.
25152 In addition, GNAT implements the implementation-defined pragmas
25156 @item @code{AST_ENTRY}
25158 @item @code{COMMON_OBJECT}
25160 @item @code{COMPONENT_ALIGNMENT}
25162 @item @code{EXPORT_EXCEPTION}
25164 @item @code{EXPORT_FUNCTION}
25166 @item @code{EXPORT_OBJECT}
25168 @item @code{EXPORT_PROCEDURE}
25170 @item @code{EXPORT_VALUED_PROCEDURE}
25172 @item @code{FLOAT_REPRESENTATION}
25176 @item @code{IMPORT_EXCEPTION}
25178 @item @code{IMPORT_FUNCTION}
25180 @item @code{IMPORT_OBJECT}
25182 @item @code{IMPORT_PROCEDURE}
25184 @item @code{IMPORT_VALUED_PROCEDURE}
25186 @item @code{INLINE_GENERIC}
25188 @item @code{INTERFACE_NAME}
25190 @item @code{LONG_FLOAT}
25192 @item @code{MAIN_STORAGE}
25194 @item @code{PASSIVE}
25196 @item @code{PSECT_OBJECT}
25198 @item @code{SHARE_GENERIC}
25200 @item @code{SUPPRESS_ALL}
25202 @item @code{TASK_STORAGE}
25204 @item @code{TIME_SLICE}
25210 These pragmas are all fully implemented, with the exception of @code{TITLE},
25211 @code{PASSIVE}, and @code{SHARE_GENERIC}, which are
25212 recognized, but which have no
25213 effect in GNAT. The effect of @code{PASSIVE} may be obtained by the
25214 use of Ada protected objects. In GNAT, all generics are inlined.
25216 Unlike HP Ada, the GNAT ``@code{EXPORT_}@i{subprogram}'' pragmas require
25217 a separate subprogram specification which must appear before the
25220 GNAT also supplies a number of implementation-defined pragmas as follows:
25222 @item @code{ABORT_DEFER}
25224 @item @code{ADA_83}
25226 @item @code{ADA_95}
25228 @item @code{ADA_05}
25230 @item @code{ANNOTATE}
25232 @item @code{ASSERT}
25234 @item @code{C_PASS_BY_COPY}
25236 @item @code{CPP_CLASS}
25238 @item @code{CPP_CONSTRUCTOR}
25240 @item @code{CPP_DESTRUCTOR}
25244 @item @code{EXTEND_SYSTEM}
25246 @item @code{LINKER_ALIAS}
25248 @item @code{LINKER_SECTION}
25250 @item @code{MACHINE_ATTRIBUTE}
25252 @item @code{NO_RETURN}
25254 @item @code{PURE_FUNCTION}
25256 @item @code{SOURCE_FILE_NAME}
25258 @item @code{SOURCE_REFERENCE}
25260 @item @code{TASK_INFO}
25262 @item @code{UNCHECKED_UNION}
25264 @item @code{UNIMPLEMENTED_UNIT}
25266 @item @code{UNIVERSAL_DATA}
25268 @item @code{UNSUPPRESS}
25270 @item @code{WARNINGS}
25272 @item @code{WEAK_EXTERNAL}
25276 For full details on these GNAT implementation-defined pragmas,
25277 see @ref{Implementation Defined Pragmas,,, gnat_rm, GNAT Reference
25281 * Restrictions on the Pragma INLINE::
25282 * Restrictions on the Pragma INTERFACE::
25283 * Restrictions on the Pragma SYSTEM_NAME::
25286 @node Restrictions on the Pragma INLINE
25287 @subsection Restrictions on Pragma @code{INLINE}
25290 HP Ada enforces the following restrictions on the pragma @code{INLINE}:
25292 @item Parameters cannot have a task type.
25294 @item Function results cannot be task types, unconstrained
25295 array types, or unconstrained types with discriminants.
25297 @item Bodies cannot declare the following:
25299 @item Subprogram body or stub (imported subprogram is allowed)
25303 @item Generic declarations
25305 @item Instantiations
25309 @item Access types (types derived from access types allowed)
25311 @item Array or record types
25313 @item Dependent tasks
25315 @item Direct recursive calls of subprogram or containing
25316 subprogram, directly or via a renaming
25322 In GNAT, the only restriction on pragma @code{INLINE} is that the
25323 body must occur before the call if both are in the same
25324 unit, and the size must be appropriately small. There are
25325 no other specific restrictions which cause subprograms to
25326 be incapable of being inlined.
25328 @node Restrictions on the Pragma INTERFACE
25329 @subsection Restrictions on Pragma @code{INTERFACE}
25332 The following restrictions on pragma @code{INTERFACE}
25333 are enforced by both HP Ada and GNAT:
25335 @item Languages accepted: Ada, Bliss, C, Fortran, Default.
25336 Default is the default on OpenVMS Alpha systems.
25338 @item Parameter passing: Language specifies default
25339 mechanisms but can be overridden with an @code{EXPORT} pragma.
25342 @item Ada: Use internal Ada rules.
25344 @item Bliss, C: Parameters must be mode @code{in}; cannot be
25345 record or task type. Result cannot be a string, an
25346 array, or a record.
25348 @item Fortran: Parameters cannot have a task type. Result cannot
25349 be a string, an array, or a record.
25354 GNAT is entirely upwards compatible with HP Ada, and in addition allows
25355 record parameters for all languages.
25357 @node Restrictions on the Pragma SYSTEM_NAME
25358 @subsection Restrictions on Pragma @code{SYSTEM_NAME}
25361 For HP Ada for OpenVMS Alpha, the enumeration literal
25362 for the type @code{NAME} is @code{OPENVMS_AXP}.
25363 In GNAT, the enumeration
25364 literal for the type @code{NAME} is @code{SYSTEM_NAME_GNAT}.
25366 @node Library of Predefined Units
25367 @section Library of Predefined Units
25370 A library of predefined units is provided as part of the
25371 HP Ada and GNAT implementations. HP Ada does not provide
25372 the package @code{MACHINE_CODE} but instead recommends importing
25375 The GNAT versions of the HP Ada Run-Time Library (@code{ADA$PREDEFINED:})
25376 units are taken from the OpenVMS Alpha version, not the OpenVMS VAX
25378 The HP Ada Predefined Library units are modified to remove post-Ada 83
25379 incompatibilities and to make them interoperable with GNAT
25380 (@pxref{Changes to DECLIB}, for details).
25381 The units are located in the @file{DECLIB} directory.
25383 The GNAT RTL is contained in
25384 the @file{ADALIB} directory, and
25385 the default search path is set up to find @code{DECLIB} units in preference
25386 to @code{ADALIB} units with the same name (@code{TEXT_IO},
25387 @code{SEQUENTIAL_IO}, and @code{DIRECT_IO}, for example).
25390 * Changes to DECLIB::
25393 @node Changes to DECLIB
25394 @subsection Changes to @code{DECLIB}
25397 The changes made to the HP Ada predefined library for GNAT and post-Ada 83
25398 compatibility are minor and include the following:
25401 @item Adjusting the location of pragmas and record representation
25402 clauses to obey Ada 95 (and thus Ada 2005) rules
25404 @item Adding the proper notation to generic formal parameters
25405 that take unconstrained types in instantiation
25407 @item Adding pragma @code{ELABORATE_BODY} to package specs
25408 that have package bodies not otherwise allowed
25410 @item Replacing occurrences of the identifier ``@code{PROTECTED}'' by
25411 ``@code{PROTECTD}''.
25412 Currently these are found only in the @code{STARLET} package spec.
25414 @item Changing @code{SYSTEM.ADDRESS} to @code{SYSTEM.SHORT_ADDRESS}
25415 where the address size is constrained to 32 bits.
25419 None of the above changes is visible to users.
25425 On OpenVMS Alpha, HP Ada provides the following strongly-typed bindings:
25428 @item Command Language Interpreter (CLI interface)
25430 @item DECtalk Run-Time Library (DTK interface)
25432 @item Librarian utility routines (LBR interface)
25434 @item General Purpose Run-Time Library (LIB interface)
25436 @item Math Run-Time Library (MTH interface)
25438 @item National Character Set Run-Time Library (NCS interface)
25440 @item Compiled Code Support Run-Time Library (OTS interface)
25442 @item Parallel Processing Run-Time Library (PPL interface)
25444 @item Screen Management Run-Time Library (SMG interface)
25446 @item Sort Run-Time Library (SOR interface)
25448 @item String Run-Time Library (STR interface)
25450 @item STARLET System Library
25453 @item X Window System Version 11R4 and 11R5 (X, XLIB interface)
25455 @item X Windows Toolkit (XT interface)
25457 @item X/Motif Version 1.1.3 and 1.2 (XM interface)
25461 GNAT provides implementations of these HP bindings in the @code{DECLIB}
25462 directory, on both the Alpha and I64 OpenVMS platforms.
25464 The X/Motif bindings used to build @code{DECLIB} are whatever versions are
25466 HP Ada @file{ADA$PREDEFINED} directory with extension @file{.ADC}.
25467 A pragma @code{Linker_Options} has been added to packages @code{Xm},
25468 @code{Xt}, and @code{X_Lib}
25469 causing the default X/Motif sharable image libraries to be linked in. This
25470 is done via options files named @file{xm.opt}, @file{xt.opt}, and
25471 @file{x_lib.opt} (also located in the @file{DECLIB} directory).
25473 It may be necessary to edit these options files to update or correct the
25474 library names if, for example, the newer X/Motif bindings from
25475 @file{ADA$EXAMPLES}
25476 had been (previous to installing GNAT) copied and renamed to supersede the
25477 default @file{ADA$PREDEFINED} versions.
25480 * Shared Libraries and Options Files::
25481 * Interfaces to C::
25484 @node Shared Libraries and Options Files
25485 @subsection Shared Libraries and Options Files
25488 When using the HP Ada
25489 predefined X and Motif bindings, the linking with their sharable images is
25490 done automatically by @command{GNAT LINK}.
25491 When using other X and Motif bindings, you need
25492 to add the corresponding sharable images to the command line for
25493 @code{GNAT LINK}. When linking with shared libraries, or with
25494 @file{.OPT} files, you must
25495 also add them to the command line for @command{GNAT LINK}.
25497 A shared library to be used with GNAT is built in the same way as other
25498 libraries under VMS. The VMS Link command can be used in standard fashion.
25500 @node Interfaces to C
25501 @subsection Interfaces to C
25505 provides the following Ada types and operations:
25508 @item C types package (@code{C_TYPES})
25510 @item C strings (@code{C_TYPES.NULL_TERMINATED})
25512 @item Other_types (@code{SHORT_INT})
25516 Interfacing to C with GNAT, you can use the above approach
25517 described for HP Ada or the facilities of Annex B of
25518 the @cite{Ada Reference Manual} (packages @code{INTERFACES.C},
25519 @code{INTERFACES.C.STRINGS} and @code{INTERFACES.C.POINTERS}). For more
25520 information, see @ref{Interfacing to C,,, gnat_rm, GNAT Reference Manual}.
25522 The @option{-gnatF} qualifier forces default and explicit
25523 @code{External_Name} parameters in pragmas @code{Import} and @code{Export}
25524 to be uppercased for compatibility with the default behavior
25525 of HP C. The qualifier has no effect on @code{Link_Name} parameters.
25527 @node Main Program Definition
25528 @section Main Program Definition
25531 The following section discusses differences in the
25532 definition of main programs on HP Ada and GNAT.
25533 On HP Ada, main programs are defined to meet the
25534 following conditions:
25536 @item Procedure with no formal parameters (returns @code{0} upon
25539 @item Procedure with no formal parameters (returns @code{42} when
25540 an unhandled exception is raised)
25542 @item Function with no formal parameters whose returned value
25543 is of a discrete type
25545 @item Procedure with one @code{out} formal of a discrete type for
25546 which a specification of pragma @code{EXPORT_VALUED_PROCEDURE} is given.
25551 When declared with the pragma @code{EXPORT_VALUED_PROCEDURE},
25552 a main function or main procedure returns a discrete
25553 value whose size is less than 64 bits (32 on VAX systems),
25554 the value is zero- or sign-extended as appropriate.
25555 On GNAT, main programs are defined as follows:
25557 @item Must be a non-generic, parameterless subprogram that
25558 is either a procedure or function returning an Ada
25559 @code{STANDARD.INTEGER} (the predefined type)
25561 @item Cannot be a generic subprogram or an instantiation of a
25565 @node Implementation-Defined Attributes
25566 @section Implementation-Defined Attributes
25569 GNAT provides all HP Ada implementation-defined
25572 @node Compiler and Run-Time Interfacing
25573 @section Compiler and Run-Time Interfacing
25576 HP Ada provides the following qualifiers to pass options to the linker
25579 @item @option{/WAIT} and @option{/SUBMIT}
25581 @item @option{/COMMAND}
25583 @item @option{/@r{[}NO@r{]}MAP}
25585 @item @option{/OUTPUT=@var{file-spec}}
25587 @item @option{/@r{[}NO@r{]}DEBUG} and @option{/@r{[}NO@r{]}TRACEBACK}
25591 To pass options to the linker, GNAT provides the following
25595 @item @option{/EXECUTABLE=@var{exec-name}}
25597 @item @option{/VERBOSE}
25599 @item @option{/@r{[}NO@r{]}DEBUG} and @option{/@r{[}NO@r{]}TRACEBACK}
25603 For more information on these switches, see
25604 @ref{Switches for gnatlink}.
25605 In HP Ada, the command-line switch @option{/OPTIMIZE} is available
25606 to control optimization. HP Ada also supplies the
25609 @item @code{OPTIMIZE}
25611 @item @code{INLINE}
25613 @item @code{INLINE_GENERIC}
25615 @item @code{SUPPRESS_ALL}
25617 @item @code{PASSIVE}
25621 In GNAT, optimization is controlled strictly by command
25622 line parameters, as described in the corresponding section of this guide.
25623 The HP pragmas for control of optimization are
25624 recognized but ignored.
25626 Note that in GNAT, the default is optimization off, whereas in HP Ada
25627 the default is that optimization is turned on.
25629 @node Program Compilation and Library Management
25630 @section Program Compilation and Library Management
25633 HP Ada and GNAT provide a comparable set of commands to
25634 build programs. HP Ada also provides a program library,
25635 which is a concept that does not exist on GNAT. Instead,
25636 GNAT provides directories of sources that are compiled as
25639 The following table summarizes
25640 the HP Ada commands and provides
25641 equivalent GNAT commands. In this table, some GNAT
25642 equivalents reflect the fact that GNAT does not use the
25643 concept of a program library. Instead, it uses a model
25644 in which collections of source and object files are used
25645 in a manner consistent with other languages like C and
25646 Fortran. Therefore, standard system file commands are used
25647 to manipulate these elements. Those GNAT commands are marked with
25649 Note that, unlike HP Ada, none of the GNAT commands accepts wild cards.
25652 @multitable @columnfractions .35 .65
25654 @item @emph{HP Ada Command}
25655 @tab @emph{GNAT Equivalent / Description}
25657 @item @command{ADA}
25658 @tab @command{GNAT COMPILE}@*
25659 Invokes the compiler to compile one or more Ada source files.
25661 @item @command{ACS ATTACH}@*
25662 @tab [No equivalent]@*
25663 Switches control of terminal from current process running the program
25666 @item @command{ACS CHECK}
25667 @tab @command{GNAT MAKE /DEPENDENCY_LIST}@*
25668 Forms the execution closure of one
25669 or more compiled units and checks completeness and currency.
25671 @item @command{ACS COMPILE}
25672 @tab @command{GNAT MAKE /ACTIONS=COMPILE}@*
25673 Forms the execution closure of one or
25674 more specified units, checks completeness and currency,
25675 identifies units that have revised source files, compiles same,
25676 and recompiles units that are or will become obsolete.
25677 Also completes incomplete generic instantiations.
25679 @item @command{ACS COPY FOREIGN}
25681 Copies a foreign object file into the program library as a
25684 @item @command{ACS COPY UNIT}
25686 Copies a compiled unit from one program library to another.
25688 @item @command{ACS CREATE LIBRARY}
25689 @tab Create /directory (*)@*
25690 Creates a program library.
25692 @item @command{ACS CREATE SUBLIBRARY}
25693 @tab Create /directory (*)@*
25694 Creates a program sublibrary.
25696 @item @command{ACS DELETE LIBRARY}
25698 Deletes a program library and its contents.
25700 @item @command{ACS DELETE SUBLIBRARY}
25702 Deletes a program sublibrary and its contents.
25704 @item @command{ACS DELETE UNIT}
25705 @tab Delete file (*)@*
25706 On OpenVMS systems, deletes one or more compiled units from
25707 the current program library.
25709 @item @command{ACS DIRECTORY}
25710 @tab Directory (*)@*
25711 On OpenVMS systems, lists units contained in the current
25714 @item @command{ACS ENTER FOREIGN}
25716 Allows the import of a foreign body as an Ada library
25717 spec and enters a reference to a pointer.
25719 @item @command{ACS ENTER UNIT}
25721 Enters a reference (pointer) from the current program library to
25722 a unit compiled into another program library.
25724 @item @command{ACS EXIT}
25725 @tab [No equivalent]@*
25726 Exits from the program library manager.
25728 @item @command{ACS EXPORT}
25730 Creates an object file that contains system-specific object code
25731 for one or more units. With GNAT, object files can simply be copied
25732 into the desired directory.
25734 @item @command{ACS EXTRACT SOURCE}
25736 Allows access to the copied source file for each Ada compilation unit
25738 @item @command{ACS HELP}
25739 @tab @command{HELP GNAT}@*
25740 Provides online help.
25742 @item @command{ACS LINK}
25743 @tab @command{GNAT LINK}@*
25744 Links an object file containing Ada units into an executable file.
25746 @item @command{ACS LOAD}
25748 Loads (partially compiles) Ada units into the program library.
25749 Allows loading a program from a collection of files into a library
25750 without knowing the relationship among units.
25752 @item @command{ACS MERGE}
25754 Merges into the current program library, one or more units from
25755 another library where they were modified.
25757 @item @command{ACS RECOMPILE}
25758 @tab @command{GNAT MAKE /ACTIONS=COMPILE}@*
25759 Recompiles from external or copied source files any obsolete
25760 unit in the closure. Also, completes any incomplete generic
25763 @item @command{ACS REENTER}
25764 @tab @command{GNAT MAKE}@*
25765 Reenters current references to units compiled after last entered
25766 with the @command{ACS ENTER UNIT} command.
25768 @item @command{ACS SET LIBRARY}
25769 @tab Set default (*)@*
25770 Defines a program library to be the compilation context as well
25771 as the target library for compiler output and commands in general.
25773 @item @command{ACS SET PRAGMA}
25774 @tab Edit @file{gnat.adc} (*)@*
25775 Redefines specified values of the library characteristics
25776 @code{LONG_ FLOAT}, @code{MEMORY_SIZE}, @code{SYSTEM_NAME},
25777 and @code{Float_Representation}.
25779 @item @command{ACS SET SOURCE}
25780 @tab Define @code{ADA_INCLUDE_PATH} path (*)@*
25781 Defines the source file search list for the @command{ACS COMPILE} command.
25783 @item @command{ACS SHOW LIBRARY}
25784 @tab Directory (*)@*
25785 Lists information about one or more program libraries.
25787 @item @command{ACS SHOW PROGRAM}
25788 @tab [No equivalent]@*
25789 Lists information about the execution closure of one or
25790 more units in the program library.
25792 @item @command{ACS SHOW SOURCE}
25793 @tab Show logical @code{ADA_INCLUDE_PATH}@*
25794 Shows the source file search used when compiling units.
25796 @item @command{ACS SHOW VERSION}
25797 @tab Compile with @option{VERBOSE} option
25798 Displays the version number of the compiler and program library
25801 @item @command{ACS SPAWN}
25802 @tab [No equivalent]@*
25803 Creates a subprocess of the current process (same as @command{DCL SPAWN}
25806 @item @command{ACS VERIFY}
25807 @tab [No equivalent]@*
25808 Performs a series of consistency checks on a program library to
25809 determine whether the library structure and library files are in
25816 @section Input-Output
25819 On OpenVMS Alpha systems, HP Ada uses OpenVMS Record
25820 Management Services (RMS) to perform operations on
25824 HP Ada and GNAT predefine an identical set of input-
25825 output packages. To make the use of the
25826 generic @code{TEXT_IO} operations more convenient, HP Ada
25827 provides predefined library packages that instantiate the
25828 integer and floating-point operations for the predefined
25829 integer and floating-point types as shown in the following table.
25831 @multitable @columnfractions .45 .55
25832 @item @emph{Package Name} @tab Instantiation
25834 @item @code{INTEGER_TEXT_IO}
25835 @tab @code{INTEGER_IO(INTEGER)}
25837 @item @code{SHORT_INTEGER_TEXT_IO}
25838 @tab @code{INTEGER_IO(SHORT_INTEGER)}
25840 @item @code{SHORT_SHORT_INTEGER_TEXT_IO}
25841 @tab @code{INTEGER_IO(SHORT_SHORT_INTEGER)}
25843 @item @code{FLOAT_TEXT_IO}
25844 @tab @code{FLOAT_IO(FLOAT)}
25846 @item @code{LONG_FLOAT_TEXT_IO}
25847 @tab @code{FLOAT_IO(LONG_FLOAT)}
25851 The HP Ada predefined packages and their operations
25852 are implemented using OpenVMS Alpha files and input-output
25853 facilities. HP Ada supports asynchronous input-output on OpenVMS Alpha.
25854 Familiarity with the following is recommended:
25856 @item RMS file organizations and access methods
25858 @item OpenVMS file specifications and directories
25860 @item OpenVMS File Definition Language (FDL)
25864 GNAT provides I/O facilities that are completely
25865 compatible with HP Ada. The distribution includes the
25866 standard HP Ada versions of all I/O packages, operating
25867 in a manner compatible with HP Ada. In particular, the
25868 following packages are by default the HP Ada (Ada 83)
25869 versions of these packages rather than the renamings
25870 suggested in Annex J of the Ada Reference Manual:
25872 @item @code{TEXT_IO}
25874 @item @code{SEQUENTIAL_IO}
25876 @item @code{DIRECT_IO}
25880 The use of the standard child package syntax (for
25881 example, @code{ADA.TEXT_IO}) retrieves the post-Ada 83 versions of these
25883 GNAT provides HP-compatible predefined instantiations
25884 of the @code{TEXT_IO} packages, and also
25885 provides the standard predefined instantiations required
25886 by the @cite{Ada Reference Manual}.
25888 For further information on how GNAT interfaces to the file
25889 system or how I/O is implemented in programs written in
25890 mixed languages, see @ref{Implementation of the Standard I/O,,,
25891 gnat_rm, GNAT Reference Manual}.
25892 This chapter covers the following:
25894 @item Standard I/O packages
25896 @item @code{FORM} strings
25898 @item @code{ADA.DIRECT_IO}
25900 @item @code{ADA.SEQUENTIAL_IO}
25902 @item @code{ADA.TEXT_IO}
25904 @item Stream pointer positioning
25906 @item Reading and writing non-regular files
25908 @item @code{GET_IMMEDIATE}
25910 @item Treating @code{TEXT_IO} files as streams
25917 @node Implementation Limits
25918 @section Implementation Limits
25921 The following table lists implementation limits for HP Ada
25923 @multitable @columnfractions .60 .20 .20
25925 @item @emph{Compilation Parameter}
25930 @item In a subprogram or entry declaration, maximum number of
25931 formal parameters that are of an unconstrained record type
25936 @item Maximum identifier length (number of characters)
25941 @item Maximum number of characters in a source line
25946 @item Maximum collection size (number of bytes)
25951 @item Maximum number of discriminants for a record type
25956 @item Maximum number of formal parameters in an entry or
25957 subprogram declaration
25962 @item Maximum number of dimensions in an array type
25967 @item Maximum number of library units and subunits in a compilation.
25972 @item Maximum number of library units and subunits in an execution.
25977 @item Maximum number of objects declared with the pragma @code{COMMON_OBJECT}
25978 or @code{PSECT_OBJECT}
25983 @item Maximum number of enumeration literals in an enumeration type
25989 @item Maximum number of lines in a source file
25994 @item Maximum number of bits in any object
25999 @item Maximum size of the static portion of a stack frame (approximate)
26004 @node Tools and Utilities
26005 @section Tools and Utilities
26008 The following table lists some of the OpenVMS development tools
26009 available for HP Ada, and the corresponding tools for
26010 use with @value{EDITION} on Alpha and I64 platforms.
26011 Aside from the debugger, all the OpenVMS tools identified are part
26012 of the DECset package.
26015 @c Specify table in TeX since Texinfo does a poor job
26019 \settabs\+Language-Sensitive Editor\quad
26020 &Product with HP Ada\quad
26023 &\it Product with HP Ada
26024 & \it Product with GNAT Pro\cr
26026 \+Code Management System
26030 \+Language-Sensitive Editor
26032 & emacs or HP LSE (Alpha)\cr
26042 & OpenVMS Debug (I64)\cr
26044 \+Source Code Analyzer /
26061 \+Coverage Analyzer
26065 \+Module Management
26067 & Not applicable\cr
26077 @c This is the Texinfo version of the table. It renders poorly in pdf, hence
26078 @c the TeX version above for the printed version
26080 @c @multitable @columnfractions .3 .4 .4
26081 @multitable {Source Code Analyzer /}{Tool with HP Ada}{Tool with GNAT Pro}
26083 @tab @i{Tool with HP Ada}
26084 @tab @i{Tool with @value{EDITION}}
26085 @item Code Management@*System
26088 @item Language-Sensitive@*Editor
26090 @tab emacs or HP LSE (Alpha)
26099 @tab OpenVMS Debug (I64)
26100 @item Source Code Analyzer /@*Cross Referencer
26104 @tab HP Digital Test@*Manager (DTM)
26106 @item Performance and@*Coverage Analyzer
26109 @item Module Management@*System
26111 @tab Not applicable
26118 @c **************************************
26119 @node Platform-Specific Information for the Run-Time Libraries
26120 @appendix Platform-Specific Information for the Run-Time Libraries
26121 @cindex Tasking and threads libraries
26122 @cindex Threads libraries and tasking
26123 @cindex Run-time libraries (platform-specific information)
26126 The GNAT run-time implementation may vary with respect to both the
26127 underlying threads library and the exception handling scheme.
26128 For threads support, one or more of the following are supplied:
26130 @item @b{native threads library}, a binding to the thread package from
26131 the underlying operating system
26133 @item @b{pthreads library} (Sparc Solaris only), a binding to the Solaris
26134 POSIX thread package
26138 For exception handling, either or both of two models are supplied:
26140 @item @b{Zero-Cost Exceptions} (``ZCX''),@footnote{
26141 Most programs should experience a substantial speed improvement by
26142 being compiled with a ZCX run-time.
26143 This is especially true for
26144 tasking applications or applications with many exception handlers.}
26145 @cindex Zero-Cost Exceptions
26146 @cindex ZCX (Zero-Cost Exceptions)
26147 which uses binder-generated tables that
26148 are interrogated at run time to locate a handler
26150 @item @b{setjmp / longjmp} (``SJLJ''),
26151 @cindex setjmp/longjmp Exception Model
26152 @cindex SJLJ (setjmp/longjmp Exception Model)
26153 which uses dynamically-set data to establish
26154 the set of handlers
26158 This appendix summarizes which combinations of threads and exception support
26159 are supplied on various GNAT platforms.
26160 It then shows how to select a particular library either
26161 permanently or temporarily,
26162 explains the properties of (and tradeoffs among) the various threads
26163 libraries, and provides some additional
26164 information about several specific platforms.
26167 * Summary of Run-Time Configurations::
26168 * Specifying a Run-Time Library::
26169 * Choosing the Scheduling Policy::
26170 * Solaris-Specific Considerations::
26171 * Linux-Specific Considerations::
26172 * AIX-Specific Considerations::
26173 * Irix-Specific Considerations::
26174 * RTX-Specific Considerations::
26177 @node Summary of Run-Time Configurations
26178 @section Summary of Run-Time Configurations
26180 @multitable @columnfractions .30 .70
26181 @item @b{alpha-openvms}
26182 @item @code{@ @ }@i{rts-native (default)}
26183 @item @code{@ @ @ @ }Tasking @tab native VMS threads
26184 @item @code{@ @ @ @ }Exceptions @tab ZCX
26186 @item @b{alpha-tru64}
26187 @item @code{@ @ }@i{rts-native (default)}
26188 @item @code{@ @ @ @ }Tasking @tab native TRU64 threads
26189 @item @code{@ @ @ @ }Exceptions @tab ZCX
26191 @item @code{@ @ }@i{rts-sjlj}
26192 @item @code{@ @ @ @ }Tasking @tab native TRU64 threads
26193 @item @code{@ @ @ @ }Exceptions @tab SJLJ
26195 @item @b{ia64-hp_linux}
26196 @item @code{@ @ }@i{rts-native (default)}
26197 @item @code{@ @ @ @ }Tasking @tab pthread library
26198 @item @code{@ @ @ @ }Exceptions @tab ZCX
26200 @item @b{ia64-hpux}
26201 @item @code{@ @ }@i{rts-native (default)}
26202 @item @code{@ @ @ @ }Tasking @tab native HP-UX threads
26203 @item @code{@ @ @ @ }Exceptions @tab SJLJ
26205 @item @b{ia64-openvms}
26206 @item @code{@ @ }@i{rts-native (default)}
26207 @item @code{@ @ @ @ }Tasking @tab native VMS threads
26208 @item @code{@ @ @ @ }Exceptions @tab ZCX
26210 @item @b{ia64-sgi_linux}
26211 @item @code{@ @ }@i{rts-native (default)}
26212 @item @code{@ @ @ @ }Tasking @tab pthread library
26213 @item @code{@ @ @ @ }Exceptions @tab ZCX
26215 @item @b{mips-irix}
26216 @item @code{@ @ }@i{rts-native (default)}
26217 @item @code{@ @ @ @ }Tasking @tab native IRIX threads
26218 @item @code{@ @ @ @ }Exceptions @tab ZCX
26221 @item @code{@ @ }@i{rts-native (default)}
26222 @item @code{@ @ @ @ }Tasking @tab native HP-UX threads
26223 @item @code{@ @ @ @ }Exceptions @tab ZCX
26225 @item @code{@ @ }@i{rts-sjlj}
26226 @item @code{@ @ @ @ }Tasking @tab native HP-UX threads
26227 @item @code{@ @ @ @ }Exceptions @tab SJLJ
26230 @item @code{@ @ }@i{rts-native (default)}
26231 @item @code{@ @ @ @ }Tasking @tab native AIX threads
26232 @item @code{@ @ @ @ }Exceptions @tab SJLJ
26234 @item @b{ppc-darwin}
26235 @item @code{@ @ }@i{rts-native (default)}
26236 @item @code{@ @ @ @ }Tasking @tab native MacOS threads
26237 @item @code{@ @ @ @ }Exceptions @tab ZCX
26239 @item @b{sparc-solaris} @tab
26240 @item @code{@ @ }@i{rts-native (default)}
26241 @item @code{@ @ @ @ }Tasking @tab native Solaris threads library
26242 @item @code{@ @ @ @ }Exceptions @tab ZCX
26244 @item @code{@ @ }@i{rts-pthread}
26245 @item @code{@ @ @ @ }Tasking @tab pthread library
26246 @item @code{@ @ @ @ }Exceptions @tab ZCX
26248 @item @code{@ @ }@i{rts-sjlj}
26249 @item @code{@ @ @ @ }Tasking @tab native Solaris threads library
26250 @item @code{@ @ @ @ }Exceptions @tab SJLJ
26252 @item @b{sparc64-solaris} @tab
26253 @item @code{@ @ }@i{rts-native (default)}
26254 @item @code{@ @ @ @ }Tasking @tab native Solaris threads library
26255 @item @code{@ @ @ @ }Exceptions @tab ZCX
26257 @item @b{x86-linux}
26258 @item @code{@ @ }@i{rts-native (default)}
26259 @item @code{@ @ @ @ }Tasking @tab pthread library
26260 @item @code{@ @ @ @ }Exceptions @tab ZCX
26262 @item @code{@ @ }@i{rts-sjlj}
26263 @item @code{@ @ @ @ }Tasking @tab pthread library
26264 @item @code{@ @ @ @ }Exceptions @tab SJLJ
26267 @item @code{@ @ }@i{rts-native (default)}
26268 @item @code{@ @ @ @ }Tasking @tab native LynxOS threads
26269 @item @code{@ @ @ @ }Exceptions @tab SJLJ
26271 @item @b{x86-solaris}
26272 @item @code{@ @ }@i{rts-native (default)}
26273 @item @code{@ @ @ @ }Tasking @tab native Solaris threads
26274 @item @code{@ @ @ @ }Exceptions @tab SJLJ
26276 @item @b{x86-windows}
26277 @item @code{@ @ }@i{rts-native (default)}
26278 @item @code{@ @ @ @ }Tasking @tab native Win32 threads
26279 @item @code{@ @ @ @ }Exceptions @tab ZCX
26281 @item @code{@ @ }@i{rts-sjlj (default)}
26282 @item @code{@ @ @ @ }Tasking @tab native Win32 threads
26283 @item @code{@ @ @ @ }Exceptions @tab SJLJ
26285 @item @b{x86-windows-rtx}
26286 @item @code{@ @ }@i{rts-rtx-rtss (default)}
26287 @item @code{@ @ @ @ }Tasking @tab RTX real-time subsystem RTSS threads (kernel mode)
26288 @item @code{@ @ @ @ }Exceptions @tab SJLJ
26290 @item @code{@ @ }@i{rts-rtx-w32}
26291 @item @code{@ @ @ @ }Tasking @tab RTX Win32 threads (user mode)
26292 @item @code{@ @ @ @ }Exceptions @tab ZCX
26294 @item @b{x86_64-linux}
26295 @item @code{@ @ }@i{rts-native (default)}
26296 @item @code{@ @ @ @ }Tasking @tab pthread library
26297 @item @code{@ @ @ @ }Exceptions @tab ZCX
26299 @item @code{@ @ }@i{rts-sjlj}
26300 @item @code{@ @ @ @ }Tasking @tab pthread library
26301 @item @code{@ @ @ @ }Exceptions @tab SJLJ
26305 @node Specifying a Run-Time Library
26306 @section Specifying a Run-Time Library
26309 The @file{adainclude} subdirectory containing the sources of the GNAT
26310 run-time library, and the @file{adalib} subdirectory containing the
26311 @file{ALI} files and the static and/or shared GNAT library, are located
26312 in the gcc target-dependent area:
26315 target=$prefix/lib/gcc/gcc-@i{dumpmachine}/gcc-@i{dumpversion}/
26319 As indicated above, on some platforms several run-time libraries are supplied.
26320 These libraries are installed in the target dependent area and
26321 contain a complete source and binary subdirectory. The detailed description
26322 below explains the differences between the different libraries in terms of
26323 their thread support.
26325 The default run-time library (when GNAT is installed) is @emph{rts-native}.
26326 This default run time is selected by the means of soft links.
26327 For example on x86-linux:
26333 +--- adainclude----------+
26335 +--- adalib-----------+ |
26337 +--- rts-native | |
26339 | +--- adainclude <---+
26341 | +--- adalib <----+
26352 If the @i{rts-sjlj} library is to be selected on a permanent basis,
26353 these soft links can be modified with the following commands:
26357 $ rm -f adainclude adalib
26358 $ ln -s rts-sjlj/adainclude adainclude
26359 $ ln -s rts-sjlj/adalib adalib
26363 Alternatively, you can specify @file{rts-sjlj/adainclude} in the file
26364 @file{$target/ada_source_path} and @file{rts-sjlj/adalib} in
26365 @file{$target/ada_object_path}.
26367 Selecting another run-time library temporarily can be
26368 achieved by using the @option{--RTS} switch, e.g., @option{--RTS=sjlj}
26369 @cindex @option{--RTS} option
26371 @node Choosing the Scheduling Policy
26372 @section Choosing the Scheduling Policy
26375 When using a POSIX threads implementation, you have a choice of several
26376 scheduling policies: @code{SCHED_FIFO},
26377 @cindex @code{SCHED_FIFO} scheduling policy
26379 @cindex @code{SCHED_RR} scheduling policy
26380 and @code{SCHED_OTHER}.
26381 @cindex @code{SCHED_OTHER} scheduling policy
26382 Typically, the default is @code{SCHED_OTHER}, while using @code{SCHED_FIFO}
26383 or @code{SCHED_RR} requires special (e.g., root) privileges.
26385 By default, GNAT uses the @code{SCHED_OTHER} policy. To specify
26387 @cindex @code{SCHED_FIFO} scheduling policy
26388 you can use one of the following:
26392 @code{pragma Time_Slice (0.0)}
26393 @cindex pragma Time_Slice
26395 the corresponding binder option @option{-T0}
26396 @cindex @option{-T0} option
26398 @code{pragma Task_Dispatching_Policy (FIFO_Within_Priorities)}
26399 @cindex pragma Task_Dispatching_Policy
26403 To specify @code{SCHED_RR},
26404 @cindex @code{SCHED_RR} scheduling policy
26405 you should use @code{pragma Time_Slice} with a
26406 value greater than @code{0.0}, or else use the corresponding @option{-T}
26409 @node Solaris-Specific Considerations
26410 @section Solaris-Specific Considerations
26411 @cindex Solaris Sparc threads libraries
26414 This section addresses some topics related to the various threads libraries
26418 * Solaris Threads Issues::
26421 @node Solaris Threads Issues
26422 @subsection Solaris Threads Issues
26425 GNAT under Solaris/Sparc 32 bits comes with an alternate tasking run-time
26426 library based on POSIX threads --- @emph{rts-pthread}.
26427 @cindex rts-pthread threads library
26428 This run-time library has the advantage of being mostly shared across all
26429 POSIX-compliant thread implementations, and it also provides under
26430 @w{Solaris 8} the @code{PTHREAD_PRIO_INHERIT}
26431 @cindex @code{PTHREAD_PRIO_INHERIT} policy (under rts-pthread)
26432 and @code{PTHREAD_PRIO_PROTECT}
26433 @cindex @code{PTHREAD_PRIO_PROTECT} policy (under rts-pthread)
26434 semantics that can be selected using the predefined pragma
26435 @code{Locking_Policy}
26436 @cindex pragma Locking_Policy (under rts-pthread)
26438 @code{Inheritance_Locking} and @code{Ceiling_Locking} as the policy.
26439 @cindex @code{Inheritance_Locking} (under rts-pthread)
26440 @cindex @code{Ceiling_Locking} (under rts-pthread)
26442 As explained above, the native run-time library is based on the Solaris thread
26443 library (@code{libthread}) and is the default library.
26445 When the Solaris threads library is used (this is the default), programs
26446 compiled with GNAT can automatically take advantage of
26447 and can thus execute on multiple processors.
26448 The user can alternatively specify a processor on which the program should run
26449 to emulate a single-processor system. The multiprocessor / uniprocessor choice
26451 setting the environment variable @env{GNAT_PROCESSOR}
26452 @cindex @env{GNAT_PROCESSOR} environment variable (on Sparc Solaris)
26453 to one of the following:
26457 Use the default configuration (run the program on all
26458 available processors) - this is the same as having @code{GNAT_PROCESSOR}
26462 Let the run-time implementation choose one processor and run the program on
26465 @item 0 .. Last_Proc
26466 Run the program on the specified processor.
26467 @code{Last_Proc} is equal to @code{_SC_NPROCESSORS_CONF - 1}
26468 (where @code{_SC_NPROCESSORS_CONF} is a system variable).
26471 @node Linux-Specific Considerations
26472 @section Linux-Specific Considerations
26473 @cindex Linux threads libraries
26476 On GNU/Linux without NPTL support (usually system with GNU C Library
26477 older than 2.3), the signal model is not POSIX compliant, which means
26478 that to send a signal to the process, you need to send the signal to all
26479 threads, e.g.@: by using @code{killpg()}.
26481 @node AIX-Specific Considerations
26482 @section AIX-Specific Considerations
26483 @cindex AIX resolver library
26486 On AIX, the resolver library initializes some internal structure on
26487 the first call to @code{get*by*} functions, which are used to implement
26488 @code{GNAT.Sockets.Get_Host_By_Name} and
26489 @code{GNAT.Sockets.Get_Host_By_Address}.
26490 If such initialization occurs within an Ada task, and the stack size for
26491 the task is the default size, a stack overflow may occur.
26493 To avoid this overflow, the user should either ensure that the first call
26494 to @code{GNAT.Sockets.Get_Host_By_Name} or
26495 @code{GNAT.Sockets.Get_Host_By_Addrss}
26496 occurs in the environment task, or use @code{pragma Storage_Size} to
26497 specify a sufficiently large size for the stack of the task that contains
26500 @node Irix-Specific Considerations
26501 @section Irix-Specific Considerations
26502 @cindex Irix libraries
26505 The GCC support libraries coming with the Irix compiler have moved to
26506 their canonical place with respect to the general Irix ABI related
26507 conventions. Running applications built with the default shared GNAT
26508 run-time now requires the LD_LIBRARY_PATH environment variable to
26509 include this location. A possible way to achieve this is to issue the
26510 following command line on a bash prompt:
26514 $ LD_LIBRARY_PATH=$LD_LIBRARY_PATH:`dirname \`gcc --print-file-name=libgcc_s.so\``
26518 @node RTX-Specific Considerations
26519 @section RTX-Specific Considerations
26520 @cindex RTX libraries
26523 The Real-time Extension (RTX) to Windows is based on the Windows Win32
26524 API. Applications can be built to work in two different modes:
26528 Windows executables that run in Ring 3 to utilize memory protection
26529 (@emph{rts-rtx-w32}).
26532 Real-time subsystem (RTSS) executables that run in Ring 0, where
26533 performance can be optimized with RTSS applications taking precedent
26534 over all Windows applications (@emph{rts-rtx-rtss}).
26538 @c *******************************
26539 @node Example of Binder Output File
26540 @appendix Example of Binder Output File
26543 This Appendix displays the source code for @command{gnatbind}'s output
26544 file generated for a simple ``Hello World'' program.
26545 Comments have been added for clarification purposes.
26547 @smallexample @c adanocomment
26551 -- The package is called Ada_Main unless this name is actually used
26552 -- as a unit name in the partition, in which case some other unique
26556 package ada_main is
26558 Elab_Final_Code : Integer;
26559 pragma Import (C, Elab_Final_Code, "__gnat_inside_elab_final_code");
26561 -- The main program saves the parameters (argument count,
26562 -- argument values, environment pointer) in global variables
26563 -- for later access by other units including
26564 -- Ada.Command_Line.
26566 gnat_argc : Integer;
26567 gnat_argv : System.Address;
26568 gnat_envp : System.Address;
26570 -- The actual variables are stored in a library routine. This
26571 -- is useful for some shared library situations, where there
26572 -- are problems if variables are not in the library.
26574 pragma Import (C, gnat_argc);
26575 pragma Import (C, gnat_argv);
26576 pragma Import (C, gnat_envp);
26578 -- The exit status is similarly an external location
26580 gnat_exit_status : Integer;
26581 pragma Import (C, gnat_exit_status);
26583 GNAT_Version : constant String :=
26584 "GNAT Version: 6.0.0w (20061115)";
26585 pragma Export (C, GNAT_Version, "__gnat_version");
26587 -- This is the generated adafinal routine that performs
26588 -- finalization at the end of execution. In the case where
26589 -- Ada is the main program, this main program makes a call
26590 -- to adafinal at program termination.
26592 procedure adafinal;
26593 pragma Export (C, adafinal, "adafinal");
26595 -- This is the generated adainit routine that performs
26596 -- initialization at the start of execution. In the case
26597 -- where Ada is the main program, this main program makes
26598 -- a call to adainit at program startup.
26601 pragma Export (C, adainit, "adainit");
26603 -- This routine is called at the start of execution. It is
26604 -- a dummy routine that is used by the debugger to breakpoint
26605 -- at the start of execution.
26607 procedure Break_Start;
26608 pragma Import (C, Break_Start, "__gnat_break_start");
26610 -- This is the actual generated main program (it would be
26611 -- suppressed if the no main program switch were used). As
26612 -- required by standard system conventions, this program has
26613 -- the external name main.
26617 argv : System.Address;
26618 envp : System.Address)
26620 pragma Export (C, main, "main");
26622 -- The following set of constants give the version
26623 -- identification values for every unit in the bound
26624 -- partition. This identification is computed from all
26625 -- dependent semantic units, and corresponds to the
26626 -- string that would be returned by use of the
26627 -- Body_Version or Version attributes.
26629 type Version_32 is mod 2 ** 32;
26630 u00001 : constant Version_32 := 16#7880BEB3#;
26631 u00002 : constant Version_32 := 16#0D24CBD0#;
26632 u00003 : constant Version_32 := 16#3283DBEB#;
26633 u00004 : constant Version_32 := 16#2359F9ED#;
26634 u00005 : constant Version_32 := 16#664FB847#;
26635 u00006 : constant Version_32 := 16#68E803DF#;
26636 u00007 : constant Version_32 := 16#5572E604#;
26637 u00008 : constant Version_32 := 16#46B173D8#;
26638 u00009 : constant Version_32 := 16#156A40CF#;
26639 u00010 : constant Version_32 := 16#033DABE0#;
26640 u00011 : constant Version_32 := 16#6AB38FEA#;
26641 u00012 : constant Version_32 := 16#22B6217D#;
26642 u00013 : constant Version_32 := 16#68A22947#;
26643 u00014 : constant Version_32 := 16#18CC4A56#;
26644 u00015 : constant Version_32 := 16#08258E1B#;
26645 u00016 : constant Version_32 := 16#367D5222#;
26646 u00017 : constant Version_32 := 16#20C9ECA4#;
26647 u00018 : constant Version_32 := 16#50D32CB6#;
26648 u00019 : constant Version_32 := 16#39A8BB77#;
26649 u00020 : constant Version_32 := 16#5CF8FA2B#;
26650 u00021 : constant Version_32 := 16#2F1EB794#;
26651 u00022 : constant Version_32 := 16#31AB6444#;
26652 u00023 : constant Version_32 := 16#1574B6E9#;
26653 u00024 : constant Version_32 := 16#5109C189#;
26654 u00025 : constant Version_32 := 16#56D770CD#;
26655 u00026 : constant Version_32 := 16#02F9DE3D#;
26656 u00027 : constant Version_32 := 16#08AB6B2C#;
26657 u00028 : constant Version_32 := 16#3FA37670#;
26658 u00029 : constant Version_32 := 16#476457A0#;
26659 u00030 : constant Version_32 := 16#731E1B6E#;
26660 u00031 : constant Version_32 := 16#23C2E789#;
26661 u00032 : constant Version_32 := 16#0F1BD6A1#;
26662 u00033 : constant Version_32 := 16#7C25DE96#;
26663 u00034 : constant Version_32 := 16#39ADFFA2#;
26664 u00035 : constant Version_32 := 16#571DE3E7#;
26665 u00036 : constant Version_32 := 16#5EB646AB#;
26666 u00037 : constant Version_32 := 16#4249379B#;
26667 u00038 : constant Version_32 := 16#0357E00A#;
26668 u00039 : constant Version_32 := 16#3784FB72#;
26669 u00040 : constant Version_32 := 16#2E723019#;
26670 u00041 : constant Version_32 := 16#623358EA#;
26671 u00042 : constant Version_32 := 16#107F9465#;
26672 u00043 : constant Version_32 := 16#6843F68A#;
26673 u00044 : constant Version_32 := 16#63305874#;
26674 u00045 : constant Version_32 := 16#31E56CE1#;
26675 u00046 : constant Version_32 := 16#02917970#;
26676 u00047 : constant Version_32 := 16#6CCBA70E#;
26677 u00048 : constant Version_32 := 16#41CD4204#;
26678 u00049 : constant Version_32 := 16#572E3F58#;
26679 u00050 : constant Version_32 := 16#20729FF5#;
26680 u00051 : constant Version_32 := 16#1D4F93E8#;
26681 u00052 : constant Version_32 := 16#30B2EC3D#;
26682 u00053 : constant Version_32 := 16#34054F96#;
26683 u00054 : constant Version_32 := 16#5A199860#;
26684 u00055 : constant Version_32 := 16#0E7F912B#;
26685 u00056 : constant Version_32 := 16#5760634A#;
26686 u00057 : constant Version_32 := 16#5D851835#;
26688 -- The following Export pragmas export the version numbers
26689 -- with symbolic names ending in B (for body) or S
26690 -- (for spec) so that they can be located in a link. The
26691 -- information provided here is sufficient to track down
26692 -- the exact versions of units used in a given build.
26694 pragma Export (C, u00001, "helloB");
26695 pragma Export (C, u00002, "system__standard_libraryB");
26696 pragma Export (C, u00003, "system__standard_libraryS");
26697 pragma Export (C, u00004, "adaS");
26698 pragma Export (C, u00005, "ada__text_ioB");
26699 pragma Export (C, u00006, "ada__text_ioS");
26700 pragma Export (C, u00007, "ada__exceptionsB");
26701 pragma Export (C, u00008, "ada__exceptionsS");
26702 pragma Export (C, u00009, "gnatS");
26703 pragma Export (C, u00010, "gnat__heap_sort_aB");
26704 pragma Export (C, u00011, "gnat__heap_sort_aS");
26705 pragma Export (C, u00012, "systemS");
26706 pragma Export (C, u00013, "system__exception_tableB");
26707 pragma Export (C, u00014, "system__exception_tableS");
26708 pragma Export (C, u00015, "gnat__htableB");
26709 pragma Export (C, u00016, "gnat__htableS");
26710 pragma Export (C, u00017, "system__exceptionsS");
26711 pragma Export (C, u00018, "system__machine_state_operationsB");
26712 pragma Export (C, u00019, "system__machine_state_operationsS");
26713 pragma Export (C, u00020, "system__machine_codeS");
26714 pragma Export (C, u00021, "system__storage_elementsB");
26715 pragma Export (C, u00022, "system__storage_elementsS");
26716 pragma Export (C, u00023, "system__secondary_stackB");
26717 pragma Export (C, u00024, "system__secondary_stackS");
26718 pragma Export (C, u00025, "system__parametersB");
26719 pragma Export (C, u00026, "system__parametersS");
26720 pragma Export (C, u00027, "system__soft_linksB");
26721 pragma Export (C, u00028, "system__soft_linksS");
26722 pragma Export (C, u00029, "system__stack_checkingB");
26723 pragma Export (C, u00030, "system__stack_checkingS");
26724 pragma Export (C, u00031, "system__tracebackB");
26725 pragma Export (C, u00032, "system__tracebackS");
26726 pragma Export (C, u00033, "ada__streamsS");
26727 pragma Export (C, u00034, "ada__tagsB");
26728 pragma Export (C, u00035, "ada__tagsS");
26729 pragma Export (C, u00036, "system__string_opsB");
26730 pragma Export (C, u00037, "system__string_opsS");
26731 pragma Export (C, u00038, "interfacesS");
26732 pragma Export (C, u00039, "interfaces__c_streamsB");
26733 pragma Export (C, u00040, "interfaces__c_streamsS");
26734 pragma Export (C, u00041, "system__file_ioB");
26735 pragma Export (C, u00042, "system__file_ioS");
26736 pragma Export (C, u00043, "ada__finalizationB");
26737 pragma Export (C, u00044, "ada__finalizationS");
26738 pragma Export (C, u00045, "system__finalization_rootB");
26739 pragma Export (C, u00046, "system__finalization_rootS");
26740 pragma Export (C, u00047, "system__finalization_implementationB");
26741 pragma Export (C, u00048, "system__finalization_implementationS");
26742 pragma Export (C, u00049, "system__string_ops_concat_3B");
26743 pragma Export (C, u00050, "system__string_ops_concat_3S");
26744 pragma Export (C, u00051, "system__stream_attributesB");
26745 pragma Export (C, u00052, "system__stream_attributesS");
26746 pragma Export (C, u00053, "ada__io_exceptionsS");
26747 pragma Export (C, u00054, "system__unsigned_typesS");
26748 pragma Export (C, u00055, "system__file_control_blockS");
26749 pragma Export (C, u00056, "ada__finalization__list_controllerB");
26750 pragma Export (C, u00057, "ada__finalization__list_controllerS");
26752 -- BEGIN ELABORATION ORDER
26755 -- gnat.heap_sort_a (spec)
26756 -- gnat.heap_sort_a (body)
26757 -- gnat.htable (spec)
26758 -- gnat.htable (body)
26759 -- interfaces (spec)
26761 -- system.machine_code (spec)
26762 -- system.parameters (spec)
26763 -- system.parameters (body)
26764 -- interfaces.c_streams (spec)
26765 -- interfaces.c_streams (body)
26766 -- system.standard_library (spec)
26767 -- ada.exceptions (spec)
26768 -- system.exception_table (spec)
26769 -- system.exception_table (body)
26770 -- ada.io_exceptions (spec)
26771 -- system.exceptions (spec)
26772 -- system.storage_elements (spec)
26773 -- system.storage_elements (body)
26774 -- system.machine_state_operations (spec)
26775 -- system.machine_state_operations (body)
26776 -- system.secondary_stack (spec)
26777 -- system.stack_checking (spec)
26778 -- system.soft_links (spec)
26779 -- system.soft_links (body)
26780 -- system.stack_checking (body)
26781 -- system.secondary_stack (body)
26782 -- system.standard_library (body)
26783 -- system.string_ops (spec)
26784 -- system.string_ops (body)
26787 -- ada.streams (spec)
26788 -- system.finalization_root (spec)
26789 -- system.finalization_root (body)
26790 -- system.string_ops_concat_3 (spec)
26791 -- system.string_ops_concat_3 (body)
26792 -- system.traceback (spec)
26793 -- system.traceback (body)
26794 -- ada.exceptions (body)
26795 -- system.unsigned_types (spec)
26796 -- system.stream_attributes (spec)
26797 -- system.stream_attributes (body)
26798 -- system.finalization_implementation (spec)
26799 -- system.finalization_implementation (body)
26800 -- ada.finalization (spec)
26801 -- ada.finalization (body)
26802 -- ada.finalization.list_controller (spec)
26803 -- ada.finalization.list_controller (body)
26804 -- system.file_control_block (spec)
26805 -- system.file_io (spec)
26806 -- system.file_io (body)
26807 -- ada.text_io (spec)
26808 -- ada.text_io (body)
26810 -- END ELABORATION ORDER
26814 -- The following source file name pragmas allow the generated file
26815 -- names to be unique for different main programs. They are needed
26816 -- since the package name will always be Ada_Main.
26818 pragma Source_File_Name (ada_main, Spec_File_Name => "b~hello.ads");
26819 pragma Source_File_Name (ada_main, Body_File_Name => "b~hello.adb");
26821 -- Generated package body for Ada_Main starts here
26823 package body ada_main is
26825 -- The actual finalization is performed by calling the
26826 -- library routine in System.Standard_Library.Adafinal
26828 procedure Do_Finalize;
26829 pragma Import (C, Do_Finalize, "system__standard_library__adafinal");
26836 procedure adainit is
26838 -- These booleans are set to True once the associated unit has
26839 -- been elaborated. It is also used to avoid elaborating the
26840 -- same unit twice.
26843 pragma Import (Ada, E040, "interfaces__c_streams_E");
26846 pragma Import (Ada, E008, "ada__exceptions_E");
26849 pragma Import (Ada, E014, "system__exception_table_E");
26852 pragma Import (Ada, E053, "ada__io_exceptions_E");
26855 pragma Import (Ada, E017, "system__exceptions_E");
26858 pragma Import (Ada, E024, "system__secondary_stack_E");
26861 pragma Import (Ada, E030, "system__stack_checking_E");
26864 pragma Import (Ada, E028, "system__soft_links_E");
26867 pragma Import (Ada, E035, "ada__tags_E");
26870 pragma Import (Ada, E033, "ada__streams_E");
26873 pragma Import (Ada, E046, "system__finalization_root_E");
26876 pragma Import (Ada, E048, "system__finalization_implementation_E");
26879 pragma Import (Ada, E044, "ada__finalization_E");
26882 pragma Import (Ada, E057, "ada__finalization__list_controller_E");
26885 pragma Import (Ada, E055, "system__file_control_block_E");
26888 pragma Import (Ada, E042, "system__file_io_E");
26891 pragma Import (Ada, E006, "ada__text_io_E");
26893 -- Set_Globals is a library routine that stores away the
26894 -- value of the indicated set of global values in global
26895 -- variables within the library.
26897 procedure Set_Globals
26898 (Main_Priority : Integer;
26899 Time_Slice_Value : Integer;
26900 WC_Encoding : Character;
26901 Locking_Policy : Character;
26902 Queuing_Policy : Character;
26903 Task_Dispatching_Policy : Character;
26904 Adafinal : System.Address;
26905 Unreserve_All_Interrupts : Integer;
26906 Exception_Tracebacks : Integer);
26907 @findex __gnat_set_globals
26908 pragma Import (C, Set_Globals, "__gnat_set_globals");
26910 -- SDP_Table_Build is a library routine used to build the
26911 -- exception tables. See unit Ada.Exceptions in files
26912 -- a-except.ads/adb for full details of how zero cost
26913 -- exception handling works. This procedure, the call to
26914 -- it, and the two following tables are all omitted if the
26915 -- build is in longjmp/setjmp exception mode.
26917 @findex SDP_Table_Build
26918 @findex Zero Cost Exceptions
26919 procedure SDP_Table_Build
26920 (SDP_Addresses : System.Address;
26921 SDP_Count : Natural;
26922 Elab_Addresses : System.Address;
26923 Elab_Addr_Count : Natural);
26924 pragma Import (C, SDP_Table_Build, "__gnat_SDP_Table_Build");
26926 -- Table of Unit_Exception_Table addresses. Used for zero
26927 -- cost exception handling to build the top level table.
26929 ST : aliased constant array (1 .. 23) of System.Address := (
26931 Ada.Text_Io'UET_Address,
26932 Ada.Exceptions'UET_Address,
26933 Gnat.Heap_Sort_A'UET_Address,
26934 System.Exception_Table'UET_Address,
26935 System.Machine_State_Operations'UET_Address,
26936 System.Secondary_Stack'UET_Address,
26937 System.Parameters'UET_Address,
26938 System.Soft_Links'UET_Address,
26939 System.Stack_Checking'UET_Address,
26940 System.Traceback'UET_Address,
26941 Ada.Streams'UET_Address,
26942 Ada.Tags'UET_Address,
26943 System.String_Ops'UET_Address,
26944 Interfaces.C_Streams'UET_Address,
26945 System.File_Io'UET_Address,
26946 Ada.Finalization'UET_Address,
26947 System.Finalization_Root'UET_Address,
26948 System.Finalization_Implementation'UET_Address,
26949 System.String_Ops_Concat_3'UET_Address,
26950 System.Stream_Attributes'UET_Address,
26951 System.File_Control_Block'UET_Address,
26952 Ada.Finalization.List_Controller'UET_Address);
26954 -- Table of addresses of elaboration routines. Used for
26955 -- zero cost exception handling to make sure these
26956 -- addresses are included in the top level procedure
26959 EA : aliased constant array (1 .. 23) of System.Address := (
26960 adainit'Code_Address,
26961 Do_Finalize'Code_Address,
26962 Ada.Exceptions'Elab_Spec'Address,
26963 System.Exceptions'Elab_Spec'Address,
26964 Interfaces.C_Streams'Elab_Spec'Address,
26965 System.Exception_Table'Elab_Body'Address,
26966 Ada.Io_Exceptions'Elab_Spec'Address,
26967 System.Stack_Checking'Elab_Spec'Address,
26968 System.Soft_Links'Elab_Body'Address,
26969 System.Secondary_Stack'Elab_Body'Address,
26970 Ada.Tags'Elab_Spec'Address,
26971 Ada.Tags'Elab_Body'Address,
26972 Ada.Streams'Elab_Spec'Address,
26973 System.Finalization_Root'Elab_Spec'Address,
26974 Ada.Exceptions'Elab_Body'Address,
26975 System.Finalization_Implementation'Elab_Spec'Address,
26976 System.Finalization_Implementation'Elab_Body'Address,
26977 Ada.Finalization'Elab_Spec'Address,
26978 Ada.Finalization.List_Controller'Elab_Spec'Address,
26979 System.File_Control_Block'Elab_Spec'Address,
26980 System.File_Io'Elab_Body'Address,
26981 Ada.Text_Io'Elab_Spec'Address,
26982 Ada.Text_Io'Elab_Body'Address);
26984 -- Start of processing for adainit
26988 -- Call SDP_Table_Build to build the top level procedure
26989 -- table for zero cost exception handling (omitted in
26990 -- longjmp/setjmp mode).
26992 SDP_Table_Build (ST'Address, 23, EA'Address, 23);
26994 -- Call Set_Globals to record various information for
26995 -- this partition. The values are derived by the binder
26996 -- from information stored in the ali files by the compiler.
26998 @findex __gnat_set_globals
27000 (Main_Priority => -1,
27001 -- Priority of main program, -1 if no pragma Priority used
27003 Time_Slice_Value => -1,
27004 -- Time slice from Time_Slice pragma, -1 if none used
27006 WC_Encoding => 'b',
27007 -- Wide_Character encoding used, default is brackets
27009 Locking_Policy => ' ',
27010 -- Locking_Policy used, default of space means not
27011 -- specified, otherwise it is the first character of
27012 -- the policy name.
27014 Queuing_Policy => ' ',
27015 -- Queuing_Policy used, default of space means not
27016 -- specified, otherwise it is the first character of
27017 -- the policy name.
27019 Task_Dispatching_Policy => ' ',
27020 -- Task_Dispatching_Policy used, default of space means
27021 -- not specified, otherwise first character of the
27024 Adafinal => System.Null_Address,
27025 -- Address of Adafinal routine, not used anymore
27027 Unreserve_All_Interrupts => 0,
27028 -- Set true if pragma Unreserve_All_Interrupts was used
27030 Exception_Tracebacks => 0);
27031 -- Indicates if exception tracebacks are enabled
27033 Elab_Final_Code := 1;
27035 -- Now we have the elaboration calls for all units in the partition.
27036 -- The Elab_Spec and Elab_Body attributes generate references to the
27037 -- implicit elaboration procedures generated by the compiler for
27038 -- each unit that requires elaboration.
27041 Interfaces.C_Streams'Elab_Spec;
27045 Ada.Exceptions'Elab_Spec;
27048 System.Exception_Table'Elab_Body;
27052 Ada.Io_Exceptions'Elab_Spec;
27056 System.Exceptions'Elab_Spec;
27060 System.Stack_Checking'Elab_Spec;
27063 System.Soft_Links'Elab_Body;
27068 System.Secondary_Stack'Elab_Body;
27072 Ada.Tags'Elab_Spec;
27075 Ada.Tags'Elab_Body;
27079 Ada.Streams'Elab_Spec;
27083 System.Finalization_Root'Elab_Spec;
27087 Ada.Exceptions'Elab_Body;
27091 System.Finalization_Implementation'Elab_Spec;
27094 System.Finalization_Implementation'Elab_Body;
27098 Ada.Finalization'Elab_Spec;
27102 Ada.Finalization.List_Controller'Elab_Spec;
27106 System.File_Control_Block'Elab_Spec;
27110 System.File_Io'Elab_Body;
27114 Ada.Text_Io'Elab_Spec;
27117 Ada.Text_Io'Elab_Body;
27121 Elab_Final_Code := 0;
27129 procedure adafinal is
27138 -- main is actually a function, as in the ANSI C standard,
27139 -- defined to return the exit status. The three parameters
27140 -- are the argument count, argument values and environment
27143 @findex Main Program
27146 argv : System.Address;
27147 envp : System.Address)
27150 -- The initialize routine performs low level system
27151 -- initialization using a standard library routine which
27152 -- sets up signal handling and performs any other
27153 -- required setup. The routine can be found in file
27156 @findex __gnat_initialize
27157 procedure initialize;
27158 pragma Import (C, initialize, "__gnat_initialize");
27160 -- The finalize routine performs low level system
27161 -- finalization using a standard library routine. The
27162 -- routine is found in file a-final.c and in the standard
27163 -- distribution is a dummy routine that does nothing, so
27164 -- really this is a hook for special user finalization.
27166 @findex __gnat_finalize
27167 procedure finalize;
27168 pragma Import (C, finalize, "__gnat_finalize");
27170 -- We get to the main program of the partition by using
27171 -- pragma Import because if we try to with the unit and
27172 -- call it Ada style, then not only do we waste time
27173 -- recompiling it, but also, we don't really know the right
27174 -- switches (e.g.@: identifier character set) to be used
27177 procedure Ada_Main_Program;
27178 pragma Import (Ada, Ada_Main_Program, "_ada_hello");
27180 -- Start of processing for main
27183 -- Save global variables
27189 -- Call low level system initialization
27193 -- Call our generated Ada initialization routine
27197 -- This is the point at which we want the debugger to get
27202 -- Now we call the main program of the partition
27206 -- Perform Ada finalization
27210 -- Perform low level system finalization
27214 -- Return the proper exit status
27215 return (gnat_exit_status);
27218 -- This section is entirely comments, so it has no effect on the
27219 -- compilation of the Ada_Main package. It provides the list of
27220 -- object files and linker options, as well as some standard
27221 -- libraries needed for the link. The gnatlink utility parses
27222 -- this b~hello.adb file to read these comment lines to generate
27223 -- the appropriate command line arguments for the call to the
27224 -- system linker. The BEGIN/END lines are used for sentinels for
27225 -- this parsing operation.
27227 -- The exact file names will of course depend on the environment,
27228 -- host/target and location of files on the host system.
27230 @findex Object file list
27231 -- BEGIN Object file/option list
27234 -- -L/usr/local/gnat/lib/gcc-lib/i686-pc-linux-gnu/2.8.1/adalib/
27235 -- /usr/local/gnat/lib/gcc-lib/i686-pc-linux-gnu/2.8.1/adalib/libgnat.a
27236 -- END Object file/option list
27242 The Ada code in the above example is exactly what is generated by the
27243 binder. We have added comments to more clearly indicate the function
27244 of each part of the generated @code{Ada_Main} package.
27246 The code is standard Ada in all respects, and can be processed by any
27247 tools that handle Ada. In particular, it is possible to use the debugger
27248 in Ada mode to debug the generated @code{Ada_Main} package. For example,
27249 suppose that for reasons that you do not understand, your program is crashing
27250 during elaboration of the body of @code{Ada.Text_IO}. To locate this bug,
27251 you can place a breakpoint on the call:
27253 @smallexample @c ada
27254 Ada.Text_Io'Elab_Body;
27258 and trace the elaboration routine for this package to find out where
27259 the problem might be (more usually of course you would be debugging
27260 elaboration code in your own application).
27262 @node Elaboration Order Handling in GNAT
27263 @appendix Elaboration Order Handling in GNAT
27264 @cindex Order of elaboration
27265 @cindex Elaboration control
27268 * Elaboration Code::
27269 * Checking the Elaboration Order::
27270 * Controlling the Elaboration Order::
27271 * Controlling Elaboration in GNAT - Internal Calls::
27272 * Controlling Elaboration in GNAT - External Calls::
27273 * Default Behavior in GNAT - Ensuring Safety::
27274 * Treatment of Pragma Elaborate::
27275 * Elaboration Issues for Library Tasks::
27276 * Mixing Elaboration Models::
27277 * What to Do If the Default Elaboration Behavior Fails::
27278 * Elaboration for Access-to-Subprogram Values::
27279 * Summary of Procedures for Elaboration Control::
27280 * Other Elaboration Order Considerations::
27284 This chapter describes the handling of elaboration code in Ada and
27285 in GNAT, and discusses how the order of elaboration of program units can
27286 be controlled in GNAT, either automatically or with explicit programming
27289 @node Elaboration Code
27290 @section Elaboration Code
27293 Ada provides rather general mechanisms for executing code at elaboration
27294 time, that is to say before the main program starts executing. Such code arises
27298 @item Initializers for variables.
27299 Variables declared at the library level, in package specs or bodies, can
27300 require initialization that is performed at elaboration time, as in:
27301 @smallexample @c ada
27303 Sqrt_Half : Float := Sqrt (0.5);
27307 @item Package initialization code
27308 Code in a @code{BEGIN-END} section at the outer level of a package body is
27309 executed as part of the package body elaboration code.
27311 @item Library level task allocators
27312 Tasks that are declared using task allocators at the library level
27313 start executing immediately and hence can execute at elaboration time.
27317 Subprogram calls are possible in any of these contexts, which means that
27318 any arbitrary part of the program may be executed as part of the elaboration
27319 code. It is even possible to write a program which does all its work at
27320 elaboration time, with a null main program, although stylistically this
27321 would usually be considered an inappropriate way to structure
27324 An important concern arises in the context of elaboration code:
27325 we have to be sure that it is executed in an appropriate order. What we
27326 have is a series of elaboration code sections, potentially one section
27327 for each unit in the program. It is important that these execute
27328 in the correct order. Correctness here means that, taking the above
27329 example of the declaration of @code{Sqrt_Half},
27330 if some other piece of
27331 elaboration code references @code{Sqrt_Half},
27332 then it must run after the
27333 section of elaboration code that contains the declaration of
27336 There would never be any order of elaboration problem if we made a rule
27337 that whenever you @code{with} a unit, you must elaborate both the spec and body
27338 of that unit before elaborating the unit doing the @code{with}'ing:
27340 @smallexample @c ada
27344 package Unit_2 is @dots{}
27350 would require that both the body and spec of @code{Unit_1} be elaborated
27351 before the spec of @code{Unit_2}. However, a rule like that would be far too
27352 restrictive. In particular, it would make it impossible to have routines
27353 in separate packages that were mutually recursive.
27355 You might think that a clever enough compiler could look at the actual
27356 elaboration code and determine an appropriate correct order of elaboration,
27357 but in the general case, this is not possible. Consider the following
27360 In the body of @code{Unit_1}, we have a procedure @code{Func_1}
27362 the variable @code{Sqrt_1}, which is declared in the elaboration code
27363 of the body of @code{Unit_1}:
27365 @smallexample @c ada
27367 Sqrt_1 : Float := Sqrt (0.1);
27372 The elaboration code of the body of @code{Unit_1} also contains:
27374 @smallexample @c ada
27377 if expression_1 = 1 then
27378 Q := Unit_2.Func_2;
27385 @code{Unit_2} is exactly parallel,
27386 it has a procedure @code{Func_2} that references
27387 the variable @code{Sqrt_2}, which is declared in the elaboration code of
27388 the body @code{Unit_2}:
27390 @smallexample @c ada
27392 Sqrt_2 : Float := Sqrt (0.1);
27397 The elaboration code of the body of @code{Unit_2} also contains:
27399 @smallexample @c ada
27402 if expression_2 = 2 then
27403 Q := Unit_1.Func_1;
27410 Now the question is, which of the following orders of elaboration is
27435 If you carefully analyze the flow here, you will see that you cannot tell
27436 at compile time the answer to this question.
27437 If @code{expression_1} is not equal to 1,
27438 and @code{expression_2} is not equal to 2,
27439 then either order is acceptable, because neither of the function calls is
27440 executed. If both tests evaluate to true, then neither order is acceptable
27441 and in fact there is no correct order.
27443 If one of the two expressions is true, and the other is false, then one
27444 of the above orders is correct, and the other is incorrect. For example,
27445 if @code{expression_1} /= 1 and @code{expression_2} = 2,
27446 then the call to @code{Func_1}
27447 will occur, but not the call to @code{Func_2.}
27448 This means that it is essential
27449 to elaborate the body of @code{Unit_1} before
27450 the body of @code{Unit_2}, so the first
27451 order of elaboration is correct and the second is wrong.
27453 By making @code{expression_1} and @code{expression_2}
27454 depend on input data, or perhaps
27455 the time of day, we can make it impossible for the compiler or binder
27456 to figure out which of these expressions will be true, and hence it
27457 is impossible to guarantee a safe order of elaboration at run time.
27459 @node Checking the Elaboration Order
27460 @section Checking the Elaboration Order
27463 In some languages that involve the same kind of elaboration problems,
27464 e.g.@: Java and C++, the programmer is expected to worry about these
27465 ordering problems himself, and it is common to
27466 write a program in which an incorrect elaboration order gives
27467 surprising results, because it references variables before they
27469 Ada is designed to be a safe language, and a programmer-beware approach is
27470 clearly not sufficient. Consequently, the language provides three lines
27474 @item Standard rules
27475 Some standard rules restrict the possible choice of elaboration
27476 order. In particular, if you @code{with} a unit, then its spec is always
27477 elaborated before the unit doing the @code{with}. Similarly, a parent
27478 spec is always elaborated before the child spec, and finally
27479 a spec is always elaborated before its corresponding body.
27481 @item Dynamic elaboration checks
27482 @cindex Elaboration checks
27483 @cindex Checks, elaboration
27484 Dynamic checks are made at run time, so that if some entity is accessed
27485 before it is elaborated (typically by means of a subprogram call)
27486 then the exception (@code{Program_Error}) is raised.
27488 @item Elaboration control
27489 Facilities are provided for the programmer to specify the desired order
27493 Let's look at these facilities in more detail. First, the rules for
27494 dynamic checking. One possible rule would be simply to say that the
27495 exception is raised if you access a variable which has not yet been
27496 elaborated. The trouble with this approach is that it could require
27497 expensive checks on every variable reference. Instead Ada has two
27498 rules which are a little more restrictive, but easier to check, and
27502 @item Restrictions on calls
27503 A subprogram can only be called at elaboration time if its body
27504 has been elaborated. The rules for elaboration given above guarantee
27505 that the spec of the subprogram has been elaborated before the
27506 call, but not the body. If this rule is violated, then the
27507 exception @code{Program_Error} is raised.
27509 @item Restrictions on instantiations
27510 A generic unit can only be instantiated if the body of the generic
27511 unit has been elaborated. Again, the rules for elaboration given above
27512 guarantee that the spec of the generic unit has been elaborated
27513 before the instantiation, but not the body. If this rule is
27514 violated, then the exception @code{Program_Error} is raised.
27518 The idea is that if the body has been elaborated, then any variables
27519 it references must have been elaborated; by checking for the body being
27520 elaborated we guarantee that none of its references causes any
27521 trouble. As we noted above, this is a little too restrictive, because a
27522 subprogram that has no non-local references in its body may in fact be safe
27523 to call. However, it really would be unsafe to rely on this, because
27524 it would mean that the caller was aware of details of the implementation
27525 in the body. This goes against the basic tenets of Ada.
27527 A plausible implementation can be described as follows.
27528 A Boolean variable is associated with each subprogram
27529 and each generic unit. This variable is initialized to False, and is set to
27530 True at the point body is elaborated. Every call or instantiation checks the
27531 variable, and raises @code{Program_Error} if the variable is False.
27533 Note that one might think that it would be good enough to have one Boolean
27534 variable for each package, but that would not deal with cases of trying
27535 to call a body in the same package as the call
27536 that has not been elaborated yet.
27537 Of course a compiler may be able to do enough analysis to optimize away
27538 some of the Boolean variables as unnecessary, and @code{GNAT} indeed
27539 does such optimizations, but still the easiest conceptual model is to
27540 think of there being one variable per subprogram.
27542 @node Controlling the Elaboration Order
27543 @section Controlling the Elaboration Order
27546 In the previous section we discussed the rules in Ada which ensure
27547 that @code{Program_Error} is raised if an incorrect elaboration order is
27548 chosen. This prevents erroneous executions, but we need mechanisms to
27549 specify a correct execution and avoid the exception altogether.
27550 To achieve this, Ada provides a number of features for controlling
27551 the order of elaboration. We discuss these features in this section.
27553 First, there are several ways of indicating to the compiler that a given
27554 unit has no elaboration problems:
27557 @item packages that do not require a body
27558 A library package that does not require a body does not permit
27559 a body (this rule was introduced in Ada 95).
27560 Thus if we have a such a package, as in:
27562 @smallexample @c ada
27565 package Definitions is
27567 type m is new integer;
27569 type a is array (1 .. 10) of m;
27570 type b is array (1 .. 20) of m;
27578 A package that @code{with}'s @code{Definitions} may safely instantiate
27579 @code{Definitions.Subp} because the compiler can determine that there
27580 definitely is no package body to worry about in this case
27583 @cindex pragma Pure
27585 Places sufficient restrictions on a unit to guarantee that
27586 no call to any subprogram in the unit can result in an
27587 elaboration problem. This means that the compiler does not need
27588 to worry about the point of elaboration of such units, and in
27589 particular, does not need to check any calls to any subprograms
27592 @item pragma Preelaborate
27593 @findex Preelaborate
27594 @cindex pragma Preelaborate
27595 This pragma places slightly less stringent restrictions on a unit than
27597 but these restrictions are still sufficient to ensure that there
27598 are no elaboration problems with any calls to the unit.
27600 @item pragma Elaborate_Body
27601 @findex Elaborate_Body
27602 @cindex pragma Elaborate_Body
27603 This pragma requires that the body of a unit be elaborated immediately
27604 after its spec. Suppose a unit @code{A} has such a pragma,
27605 and unit @code{B} does
27606 a @code{with} of unit @code{A}. Recall that the standard rules require
27607 the spec of unit @code{A}
27608 to be elaborated before the @code{with}'ing unit; given the pragma in
27609 @code{A}, we also know that the body of @code{A}
27610 will be elaborated before @code{B}, so
27611 that calls to @code{A} are safe and do not need a check.
27616 unlike pragma @code{Pure} and pragma @code{Preelaborate},
27618 @code{Elaborate_Body} does not guarantee that the program is
27619 free of elaboration problems, because it may not be possible
27620 to satisfy the requested elaboration order.
27621 Let's go back to the example with @code{Unit_1} and @code{Unit_2}.
27623 marks @code{Unit_1} as @code{Elaborate_Body},
27624 and not @code{Unit_2,} then the order of
27625 elaboration will be:
27637 Now that means that the call to @code{Func_1} in @code{Unit_2}
27638 need not be checked,
27639 it must be safe. But the call to @code{Func_2} in
27640 @code{Unit_1} may still fail if
27641 @code{Expression_1} is equal to 1,
27642 and the programmer must still take
27643 responsibility for this not being the case.
27645 If all units carry a pragma @code{Elaborate_Body}, then all problems are
27646 eliminated, except for calls entirely within a body, which are
27647 in any case fully under programmer control. However, using the pragma
27648 everywhere is not always possible.
27649 In particular, for our @code{Unit_1}/@code{Unit_2} example, if
27650 we marked both of them as having pragma @code{Elaborate_Body}, then
27651 clearly there would be no possible elaboration order.
27653 The above pragmas allow a server to guarantee safe use by clients, and
27654 clearly this is the preferable approach. Consequently a good rule
27655 is to mark units as @code{Pure} or @code{Preelaborate} if possible,
27656 and if this is not possible,
27657 mark them as @code{Elaborate_Body} if possible.
27658 As we have seen, there are situations where neither of these
27659 three pragmas can be used.
27660 So we also provide methods for clients to control the
27661 order of elaboration of the servers on which they depend:
27664 @item pragma Elaborate (unit)
27666 @cindex pragma Elaborate
27667 This pragma is placed in the context clause, after a @code{with} clause,
27668 and it requires that the body of the named unit be elaborated before
27669 the unit in which the pragma occurs. The idea is to use this pragma
27670 if the current unit calls at elaboration time, directly or indirectly,
27671 some subprogram in the named unit.
27673 @item pragma Elaborate_All (unit)
27674 @findex Elaborate_All
27675 @cindex pragma Elaborate_All
27676 This is a stronger version of the Elaborate pragma. Consider the
27680 Unit A @code{with}'s unit B and calls B.Func in elab code
27681 Unit B @code{with}'s unit C, and B.Func calls C.Func
27685 Now if we put a pragma @code{Elaborate (B)}
27686 in unit @code{A}, this ensures that the
27687 body of @code{B} is elaborated before the call, but not the
27688 body of @code{C}, so
27689 the call to @code{C.Func} could still cause @code{Program_Error} to
27692 The effect of a pragma @code{Elaborate_All} is stronger, it requires
27693 not only that the body of the named unit be elaborated before the
27694 unit doing the @code{with}, but also the bodies of all units that the
27695 named unit uses, following @code{with} links transitively. For example,
27696 if we put a pragma @code{Elaborate_All (B)} in unit @code{A},
27698 not only that the body of @code{B} be elaborated before @code{A},
27700 body of @code{C}, because @code{B} @code{with}'s @code{C}.
27704 We are now in a position to give a usage rule in Ada for avoiding
27705 elaboration problems, at least if dynamic dispatching and access to
27706 subprogram values are not used. We will handle these cases separately
27709 The rule is simple. If a unit has elaboration code that can directly or
27710 indirectly make a call to a subprogram in a @code{with}'ed unit, or instantiate
27711 a generic package in a @code{with}'ed unit,
27712 then if the @code{with}'ed unit does not have
27713 pragma @code{Pure} or @code{Preelaborate}, then the client should have
27714 a pragma @code{Elaborate_All}
27715 for the @code{with}'ed unit. By following this rule a client is
27716 assured that calls can be made without risk of an exception.
27718 For generic subprogram instantiations, the rule can be relaxed to
27719 require only a pragma @code{Elaborate} since elaborating the body
27720 of a subprogram cannot cause any transitive elaboration (we are
27721 not calling the subprogram in this case, just elaborating its
27724 If this rule is not followed, then a program may be in one of four
27728 @item No order exists
27729 No order of elaboration exists which follows the rules, taking into
27730 account any @code{Elaborate}, @code{Elaborate_All},
27731 or @code{Elaborate_Body} pragmas. In
27732 this case, an Ada compiler must diagnose the situation at bind
27733 time, and refuse to build an executable program.
27735 @item One or more orders exist, all incorrect
27736 One or more acceptable elaboration orders exist, and all of them
27737 generate an elaboration order problem. In this case, the binder
27738 can build an executable program, but @code{Program_Error} will be raised
27739 when the program is run.
27741 @item Several orders exist, some right, some incorrect
27742 One or more acceptable elaboration orders exists, and some of them
27743 work, and some do not. The programmer has not controlled
27744 the order of elaboration, so the binder may or may not pick one of
27745 the correct orders, and the program may or may not raise an
27746 exception when it is run. This is the worst case, because it means
27747 that the program may fail when moved to another compiler, or even
27748 another version of the same compiler.
27750 @item One or more orders exists, all correct
27751 One ore more acceptable elaboration orders exist, and all of them
27752 work. In this case the program runs successfully. This state of
27753 affairs can be guaranteed by following the rule we gave above, but
27754 may be true even if the rule is not followed.
27758 Note that one additional advantage of following our rules on the use
27759 of @code{Elaborate} and @code{Elaborate_All}
27760 is that the program continues to stay in the ideal (all orders OK) state
27761 even if maintenance
27762 changes some bodies of some units. Conversely, if a program that does
27763 not follow this rule happens to be safe at some point, this state of affairs
27764 may deteriorate silently as a result of maintenance changes.
27766 You may have noticed that the above discussion did not mention
27767 the use of @code{Elaborate_Body}. This was a deliberate omission. If you
27768 @code{with} an @code{Elaborate_Body} unit, it still may be the case that
27769 code in the body makes calls to some other unit, so it is still necessary
27770 to use @code{Elaborate_All} on such units.
27772 @node Controlling Elaboration in GNAT - Internal Calls
27773 @section Controlling Elaboration in GNAT - Internal Calls
27776 In the case of internal calls, i.e., calls within a single package, the
27777 programmer has full control over the order of elaboration, and it is up
27778 to the programmer to elaborate declarations in an appropriate order. For
27781 @smallexample @c ada
27784 function One return Float;
27788 function One return Float is
27797 will obviously raise @code{Program_Error} at run time, because function
27798 One will be called before its body is elaborated. In this case GNAT will
27799 generate a warning that the call will raise @code{Program_Error}:
27805 2. function One return Float;
27807 4. Q : Float := One;
27809 >>> warning: cannot call "One" before body is elaborated
27810 >>> warning: Program_Error will be raised at run time
27813 6. function One return Float is
27826 Note that in this particular case, it is likely that the call is safe, because
27827 the function @code{One} does not access any global variables.
27828 Nevertheless in Ada, we do not want the validity of the check to depend on
27829 the contents of the body (think about the separate compilation case), so this
27830 is still wrong, as we discussed in the previous sections.
27832 The error is easily corrected by rearranging the declarations so that the
27833 body of @code{One} appears before the declaration containing the call
27834 (note that in Ada 95 and Ada 2005,
27835 declarations can appear in any order, so there is no restriction that
27836 would prevent this reordering, and if we write:
27838 @smallexample @c ada
27841 function One return Float;
27843 function One return Float is
27854 then all is well, no warning is generated, and no
27855 @code{Program_Error} exception
27857 Things are more complicated when a chain of subprograms is executed:
27859 @smallexample @c ada
27862 function A return Integer;
27863 function B return Integer;
27864 function C return Integer;
27866 function B return Integer is begin return A; end;
27867 function C return Integer is begin return B; end;
27871 function A return Integer is begin return 1; end;
27877 Now the call to @code{C}
27878 at elaboration time in the declaration of @code{X} is correct, because
27879 the body of @code{C} is already elaborated,
27880 and the call to @code{B} within the body of
27881 @code{C} is correct, but the call
27882 to @code{A} within the body of @code{B} is incorrect, because the body
27883 of @code{A} has not been elaborated, so @code{Program_Error}
27884 will be raised on the call to @code{A}.
27885 In this case GNAT will generate a
27886 warning that @code{Program_Error} may be
27887 raised at the point of the call. Let's look at the warning:
27893 2. function A return Integer;
27894 3. function B return Integer;
27895 4. function C return Integer;
27897 6. function B return Integer is begin return A; end;
27899 >>> warning: call to "A" before body is elaborated may
27900 raise Program_Error
27901 >>> warning: "B" called at line 7
27902 >>> warning: "C" called at line 9
27904 7. function C return Integer is begin return B; end;
27906 9. X : Integer := C;
27908 11. function A return Integer is begin return 1; end;
27918 Note that the message here says ``may raise'', instead of the direct case,
27919 where the message says ``will be raised''. That's because whether
27921 actually called depends in general on run-time flow of control.
27922 For example, if the body of @code{B} said
27924 @smallexample @c ada
27927 function B return Integer is
27929 if some-condition-depending-on-input-data then
27940 then we could not know until run time whether the incorrect call to A would
27941 actually occur, so @code{Program_Error} might
27942 or might not be raised. It is possible for a compiler to
27943 do a better job of analyzing bodies, to
27944 determine whether or not @code{Program_Error}
27945 might be raised, but it certainly
27946 couldn't do a perfect job (that would require solving the halting problem
27947 and is provably impossible), and because this is a warning anyway, it does
27948 not seem worth the effort to do the analysis. Cases in which it
27949 would be relevant are rare.
27951 In practice, warnings of either of the forms given
27952 above will usually correspond to
27953 real errors, and should be examined carefully and eliminated.
27954 In the rare case where a warning is bogus, it can be suppressed by any of
27955 the following methods:
27959 Compile with the @option{-gnatws} switch set
27962 Suppress @code{Elaboration_Check} for the called subprogram
27965 Use pragma @code{Warnings_Off} to turn warnings off for the call
27969 For the internal elaboration check case,
27970 GNAT by default generates the
27971 necessary run-time checks to ensure
27972 that @code{Program_Error} is raised if any
27973 call fails an elaboration check. Of course this can only happen if a
27974 warning has been issued as described above. The use of pragma
27975 @code{Suppress (Elaboration_Check)} may (but is not guaranteed to) suppress
27976 some of these checks, meaning that it may be possible (but is not
27977 guaranteed) for a program to be able to call a subprogram whose body
27978 is not yet elaborated, without raising a @code{Program_Error} exception.
27980 @node Controlling Elaboration in GNAT - External Calls
27981 @section Controlling Elaboration in GNAT - External Calls
27984 The previous section discussed the case in which the execution of a
27985 particular thread of elaboration code occurred entirely within a
27986 single unit. This is the easy case to handle, because a programmer
27987 has direct and total control over the order of elaboration, and
27988 furthermore, checks need only be generated in cases which are rare
27989 and which the compiler can easily detect.
27990 The situation is more complex when separate compilation is taken into account.
27991 Consider the following:
27993 @smallexample @c ada
27997 function Sqrt (Arg : Float) return Float;
28000 package body Math is
28001 function Sqrt (Arg : Float) return Float is
28010 X : Float := Math.Sqrt (0.5);
28023 where @code{Main} is the main program. When this program is executed, the
28024 elaboration code must first be executed, and one of the jobs of the
28025 binder is to determine the order in which the units of a program are
28026 to be elaborated. In this case we have four units: the spec and body
28028 the spec of @code{Stuff} and the body of @code{Main}).
28029 In what order should the four separate sections of elaboration code
28032 There are some restrictions in the order of elaboration that the binder
28033 can choose. In particular, if unit U has a @code{with}
28034 for a package @code{X}, then you
28035 are assured that the spec of @code{X}
28036 is elaborated before U , but you are
28037 not assured that the body of @code{X}
28038 is elaborated before U.
28039 This means that in the above case, the binder is allowed to choose the
28050 but that's not good, because now the call to @code{Math.Sqrt}
28051 that happens during
28052 the elaboration of the @code{Stuff}
28053 spec happens before the body of @code{Math.Sqrt} is
28054 elaborated, and hence causes @code{Program_Error} exception to be raised.
28055 At first glance, one might say that the binder is misbehaving, because
28056 obviously you want to elaborate the body of something you @code{with}
28058 that is not a general rule that can be followed in all cases. Consider
28060 @smallexample @c ada
28063 package X is @dots{}
28065 package Y is @dots{}
28068 package body Y is @dots{}
28071 package body X is @dots{}
28077 This is a common arrangement, and, apart from the order of elaboration
28078 problems that might arise in connection with elaboration code, this works fine.
28079 A rule that says that you must first elaborate the body of anything you
28080 @code{with} cannot work in this case:
28081 the body of @code{X} @code{with}'s @code{Y},
28082 which means you would have to
28083 elaborate the body of @code{Y} first, but that @code{with}'s @code{X},
28085 you have to elaborate the body of @code{X} first, but @dots{} and we have a
28086 loop that cannot be broken.
28088 It is true that the binder can in many cases guess an order of elaboration
28089 that is unlikely to cause a @code{Program_Error}
28090 exception to be raised, and it tries to do so (in the
28091 above example of @code{Math/Stuff/Spec}, the GNAT binder will
28093 elaborate the body of @code{Math} right after its spec, so all will be well).
28095 However, a program that blindly relies on the binder to be helpful can
28096 get into trouble, as we discussed in the previous sections, so
28098 provides a number of facilities for assisting the programmer in
28099 developing programs that are robust with respect to elaboration order.
28101 @node Default Behavior in GNAT - Ensuring Safety
28102 @section Default Behavior in GNAT - Ensuring Safety
28105 The default behavior in GNAT ensures elaboration safety. In its
28106 default mode GNAT implements the
28107 rule we previously described as the right approach. Let's restate it:
28111 @emph{If a unit has elaboration code that can directly or indirectly make a
28112 call to a subprogram in a @code{with}'ed unit, or instantiate a generic
28113 package in a @code{with}'ed unit, then if the @code{with}'ed unit
28114 does not have pragma @code{Pure} or
28115 @code{Preelaborate}, then the client should have an
28116 @code{Elaborate_All} pragma for the @code{with}'ed unit.}
28118 @emph{In the case of instantiating a generic subprogram, it is always
28119 sufficient to have only an @code{Elaborate} pragma for the
28120 @code{with}'ed unit.}
28124 By following this rule a client is assured that calls and instantiations
28125 can be made without risk of an exception.
28127 In this mode GNAT traces all calls that are potentially made from
28128 elaboration code, and puts in any missing implicit @code{Elaborate}
28129 and @code{Elaborate_All} pragmas.
28130 The advantage of this approach is that no elaboration problems
28131 are possible if the binder can find an elaboration order that is
28132 consistent with these implicit @code{Elaborate} and
28133 @code{Elaborate_All} pragmas. The
28134 disadvantage of this approach is that no such order may exist.
28136 If the binder does not generate any diagnostics, then it means that it has
28137 found an elaboration order that is guaranteed to be safe. However, the binder
28138 may still be relying on implicitly generated @code{Elaborate} and
28139 @code{Elaborate_All} pragmas so portability to other compilers than GNAT is not
28142 If it is important to guarantee portability, then the compilations should
28145 (warn on elaboration problems) switch. This will cause warning messages
28146 to be generated indicating the missing @code{Elaborate} and
28147 @code{Elaborate_All} pragmas.
28148 Consider the following source program:
28150 @smallexample @c ada
28155 m : integer := k.r;
28162 where it is clear that there
28163 should be a pragma @code{Elaborate_All}
28164 for unit @code{k}. An implicit pragma will be generated, and it is
28165 likely that the binder will be able to honor it. However, if you want
28166 to port this program to some other Ada compiler than GNAT.
28167 it is safer to include the pragma explicitly in the source. If this
28168 unit is compiled with the
28170 switch, then the compiler outputs a warning:
28177 3. m : integer := k.r;
28179 >>> warning: call to "r" may raise Program_Error
28180 >>> warning: missing pragma Elaborate_All for "k"
28188 and these warnings can be used as a guide for supplying manually
28189 the missing pragmas. It is usually a bad idea to use this warning
28190 option during development. That's because it will warn you when
28191 you need to put in a pragma, but cannot warn you when it is time
28192 to take it out. So the use of pragma @code{Elaborate_All} may lead to
28193 unnecessary dependencies and even false circularities.
28195 This default mode is more restrictive than the Ada Reference
28196 Manual, and it is possible to construct programs which will compile
28197 using the dynamic model described there, but will run into a
28198 circularity using the safer static model we have described.
28200 Of course any Ada compiler must be able to operate in a mode
28201 consistent with the requirements of the Ada Reference Manual,
28202 and in particular must have the capability of implementing the
28203 standard dynamic model of elaboration with run-time checks.
28205 In GNAT, this standard mode can be achieved either by the use of
28206 the @option{-gnatE} switch on the compiler (@command{gcc} or
28207 @command{gnatmake}) command, or by the use of the configuration pragma:
28209 @smallexample @c ada
28210 pragma Elaboration_Checks (RM);
28214 Either approach will cause the unit affected to be compiled using the
28215 standard dynamic run-time elaboration checks described in the Ada
28216 Reference Manual. The static model is generally preferable, since it
28217 is clearly safer to rely on compile and link time checks rather than
28218 run-time checks. However, in the case of legacy code, it may be
28219 difficult to meet the requirements of the static model. This
28220 issue is further discussed in
28221 @ref{What to Do If the Default Elaboration Behavior Fails}.
28223 Note that the static model provides a strict subset of the allowed
28224 behavior and programs of the Ada Reference Manual, so if you do
28225 adhere to the static model and no circularities exist,
28226 then you are assured that your program will
28227 work using the dynamic model, providing that you remove any
28228 pragma Elaborate statements from the source.
28230 @node Treatment of Pragma Elaborate
28231 @section Treatment of Pragma Elaborate
28232 @cindex Pragma Elaborate
28235 The use of @code{pragma Elaborate}
28236 should generally be avoided in Ada 95 and Ada 2005 programs,
28237 since there is no guarantee that transitive calls
28238 will be properly handled. Indeed at one point, this pragma was placed
28239 in Annex J (Obsolescent Features), on the grounds that it is never useful.
28241 Now that's a bit restrictive. In practice, the case in which
28242 @code{pragma Elaborate} is useful is when the caller knows that there
28243 are no transitive calls, or that the called unit contains all necessary
28244 transitive @code{pragma Elaborate} statements, and legacy code often
28245 contains such uses.
28247 Strictly speaking the static mode in GNAT should ignore such pragmas,
28248 since there is no assurance at compile time that the necessary safety
28249 conditions are met. In practice, this would cause GNAT to be incompatible
28250 with correctly written Ada 83 code that had all necessary
28251 @code{pragma Elaborate} statements in place. Consequently, we made the
28252 decision that GNAT in its default mode will believe that if it encounters
28253 a @code{pragma Elaborate} then the programmer knows what they are doing,
28254 and it will trust that no elaboration errors can occur.
28256 The result of this decision is two-fold. First to be safe using the
28257 static mode, you should remove all @code{pragma Elaborate} statements.
28258 Second, when fixing circularities in existing code, you can selectively
28259 use @code{pragma Elaborate} statements to convince the static mode of
28260 GNAT that it need not generate an implicit @code{pragma Elaborate_All}
28263 When using the static mode with @option{-gnatwl}, any use of
28264 @code{pragma Elaborate} will generate a warning about possible
28267 @node Elaboration Issues for Library Tasks
28268 @section Elaboration Issues for Library Tasks
28269 @cindex Library tasks, elaboration issues
28270 @cindex Elaboration of library tasks
28273 In this section we examine special elaboration issues that arise for
28274 programs that declare library level tasks.
28276 Generally the model of execution of an Ada program is that all units are
28277 elaborated, and then execution of the program starts. However, the
28278 declaration of library tasks definitely does not fit this model. The
28279 reason for this is that library tasks start as soon as they are declared
28280 (more precisely, as soon as the statement part of the enclosing package
28281 body is reached), that is to say before elaboration
28282 of the program is complete. This means that if such a task calls a
28283 subprogram, or an entry in another task, the callee may or may not be
28284 elaborated yet, and in the standard
28285 Reference Manual model of dynamic elaboration checks, you can even
28286 get timing dependent Program_Error exceptions, since there can be
28287 a race between the elaboration code and the task code.
28289 The static model of elaboration in GNAT seeks to avoid all such
28290 dynamic behavior, by being conservative, and the conservative
28291 approach in this particular case is to assume that all the code
28292 in a task body is potentially executed at elaboration time if
28293 a task is declared at the library level.
28295 This can definitely result in unexpected circularities. Consider
28296 the following example
28298 @smallexample @c ada
28304 type My_Int is new Integer;
28306 function Ident (M : My_Int) return My_Int;
28310 package body Decls is
28311 task body Lib_Task is
28317 function Ident (M : My_Int) return My_Int is
28325 procedure Put_Val (Arg : Decls.My_Int);
28329 package body Utils is
28330 procedure Put_Val (Arg : Decls.My_Int) is
28332 Text_IO.Put_Line (Decls.My_Int'Image (Decls.Ident (Arg)));
28339 Decls.Lib_Task.Start;
28344 If the above example is compiled in the default static elaboration
28345 mode, then a circularity occurs. The circularity comes from the call
28346 @code{Utils.Put_Val} in the task body of @code{Decls.Lib_Task}. Since
28347 this call occurs in elaboration code, we need an implicit pragma
28348 @code{Elaborate_All} for @code{Utils}. This means that not only must
28349 the spec and body of @code{Utils} be elaborated before the body
28350 of @code{Decls}, but also the spec and body of any unit that is
28351 @code{with'ed} by the body of @code{Utils} must also be elaborated before
28352 the body of @code{Decls}. This is the transitive implication of
28353 pragma @code{Elaborate_All} and it makes sense, because in general
28354 the body of @code{Put_Val} might have a call to something in a
28355 @code{with'ed} unit.
28357 In this case, the body of Utils (actually its spec) @code{with's}
28358 @code{Decls}. Unfortunately this means that the body of @code{Decls}
28359 must be elaborated before itself, in case there is a call from the
28360 body of @code{Utils}.
28362 Here is the exact chain of events we are worrying about:
28366 In the body of @code{Decls} a call is made from within the body of a library
28367 task to a subprogram in the package @code{Utils}. Since this call may
28368 occur at elaboration time (given that the task is activated at elaboration
28369 time), we have to assume the worst, i.e., that the
28370 call does happen at elaboration time.
28373 This means that the body and spec of @code{Util} must be elaborated before
28374 the body of @code{Decls} so that this call does not cause an access before
28378 Within the body of @code{Util}, specifically within the body of
28379 @code{Util.Put_Val} there may be calls to any unit @code{with}'ed
28383 One such @code{with}'ed package is package @code{Decls}, so there
28384 might be a call to a subprogram in @code{Decls} in @code{Put_Val}.
28385 In fact there is such a call in this example, but we would have to
28386 assume that there was such a call even if it were not there, since
28387 we are not supposed to write the body of @code{Decls} knowing what
28388 is in the body of @code{Utils}; certainly in the case of the
28389 static elaboration model, the compiler does not know what is in
28390 other bodies and must assume the worst.
28393 This means that the spec and body of @code{Decls} must also be
28394 elaborated before we elaborate the unit containing the call, but
28395 that unit is @code{Decls}! This means that the body of @code{Decls}
28396 must be elaborated before itself, and that's a circularity.
28400 Indeed, if you add an explicit pragma @code{Elaborate_All} for @code{Utils} in
28401 the body of @code{Decls} you will get a true Ada Reference Manual
28402 circularity that makes the program illegal.
28404 In practice, we have found that problems with the static model of
28405 elaboration in existing code often arise from library tasks, so
28406 we must address this particular situation.
28408 Note that if we compile and run the program above, using the dynamic model of
28409 elaboration (that is to say use the @option{-gnatE} switch),
28410 then it compiles, binds,
28411 links, and runs, printing the expected result of 2. Therefore in some sense
28412 the circularity here is only apparent, and we need to capture
28413 the properties of this program that distinguish it from other library-level
28414 tasks that have real elaboration problems.
28416 We have four possible answers to this question:
28421 Use the dynamic model of elaboration.
28423 If we use the @option{-gnatE} switch, then as noted above, the program works.
28424 Why is this? If we examine the task body, it is apparent that the task cannot
28426 @code{accept} statement until after elaboration has been completed, because
28427 the corresponding entry call comes from the main program, not earlier.
28428 This is why the dynamic model works here. But that's really giving
28429 up on a precise analysis, and we prefer to take this approach only if we cannot
28431 problem in any other manner. So let us examine two ways to reorganize
28432 the program to avoid the potential elaboration problem.
28435 Split library tasks into separate packages.
28437 Write separate packages, so that library tasks are isolated from
28438 other declarations as much as possible. Let us look at a variation on
28441 @smallexample @c ada
28449 package body Decls1 is
28450 task body Lib_Task is
28458 type My_Int is new Integer;
28459 function Ident (M : My_Int) return My_Int;
28463 package body Decls2 is
28464 function Ident (M : My_Int) return My_Int is
28472 procedure Put_Val (Arg : Decls2.My_Int);
28476 package body Utils is
28477 procedure Put_Val (Arg : Decls2.My_Int) is
28479 Text_IO.Put_Line (Decls2.My_Int'Image (Decls2.Ident (Arg)));
28486 Decls1.Lib_Task.Start;
28491 All we have done is to split @code{Decls} into two packages, one
28492 containing the library task, and one containing everything else. Now
28493 there is no cycle, and the program compiles, binds, links and executes
28494 using the default static model of elaboration.
28497 Declare separate task types.
28499 A significant part of the problem arises because of the use of the
28500 single task declaration form. This means that the elaboration of
28501 the task type, and the elaboration of the task itself (i.e.@: the
28502 creation of the task) happen at the same time. A good rule
28503 of style in Ada is to always create explicit task types. By
28504 following the additional step of placing task objects in separate
28505 packages from the task type declaration, many elaboration problems
28506 are avoided. Here is another modified example of the example program:
28508 @smallexample @c ada
28510 task type Lib_Task_Type is
28514 type My_Int is new Integer;
28516 function Ident (M : My_Int) return My_Int;
28520 package body Decls is
28521 task body Lib_Task_Type is
28527 function Ident (M : My_Int) return My_Int is
28535 procedure Put_Val (Arg : Decls.My_Int);
28539 package body Utils is
28540 procedure Put_Val (Arg : Decls.My_Int) is
28542 Text_IO.Put_Line (Decls.My_Int'Image (Decls.Ident (Arg)));
28548 Lib_Task : Decls.Lib_Task_Type;
28554 Declst.Lib_Task.Start;
28559 What we have done here is to replace the @code{task} declaration in
28560 package @code{Decls} with a @code{task type} declaration. Then we
28561 introduce a separate package @code{Declst} to contain the actual
28562 task object. This separates the elaboration issues for
28563 the @code{task type}
28564 declaration, which causes no trouble, from the elaboration issues
28565 of the task object, which is also unproblematic, since it is now independent
28566 of the elaboration of @code{Utils}.
28567 This separation of concerns also corresponds to
28568 a generally sound engineering principle of separating declarations
28569 from instances. This version of the program also compiles, binds, links,
28570 and executes, generating the expected output.
28573 Use No_Entry_Calls_In_Elaboration_Code restriction.
28574 @cindex No_Entry_Calls_In_Elaboration_Code
28576 The previous two approaches described how a program can be restructured
28577 to avoid the special problems caused by library task bodies. in practice,
28578 however, such restructuring may be difficult to apply to existing legacy code,
28579 so we must consider solutions that do not require massive rewriting.
28581 Let us consider more carefully why our original sample program works
28582 under the dynamic model of elaboration. The reason is that the code
28583 in the task body blocks immediately on the @code{accept}
28584 statement. Now of course there is nothing to prohibit elaboration
28585 code from making entry calls (for example from another library level task),
28586 so we cannot tell in isolation that
28587 the task will not execute the accept statement during elaboration.
28589 However, in practice it is very unusual to see elaboration code
28590 make any entry calls, and the pattern of tasks starting
28591 at elaboration time and then immediately blocking on @code{accept} or
28592 @code{select} statements is very common. What this means is that
28593 the compiler is being too pessimistic when it analyzes the
28594 whole package body as though it might be executed at elaboration
28597 If we know that the elaboration code contains no entry calls, (a very safe
28598 assumption most of the time, that could almost be made the default
28599 behavior), then we can compile all units of the program under control
28600 of the following configuration pragma:
28603 pragma Restrictions (No_Entry_Calls_In_Elaboration_Code);
28607 This pragma can be placed in the @file{gnat.adc} file in the usual
28608 manner. If we take our original unmodified program and compile it
28609 in the presence of a @file{gnat.adc} containing the above pragma,
28610 then once again, we can compile, bind, link, and execute, obtaining
28611 the expected result. In the presence of this pragma, the compiler does
28612 not trace calls in a task body, that appear after the first @code{accept}
28613 or @code{select} statement, and therefore does not report a potential
28614 circularity in the original program.
28616 The compiler will check to the extent it can that the above
28617 restriction is not violated, but it is not always possible to do a
28618 complete check at compile time, so it is important to use this
28619 pragma only if the stated restriction is in fact met, that is to say
28620 no task receives an entry call before elaboration of all units is completed.
28624 @node Mixing Elaboration Models
28625 @section Mixing Elaboration Models
28627 So far, we have assumed that the entire program is either compiled
28628 using the dynamic model or static model, ensuring consistency. It
28629 is possible to mix the two models, but rules have to be followed
28630 if this mixing is done to ensure that elaboration checks are not
28633 The basic rule is that @emph{a unit compiled with the static model cannot
28634 be @code{with'ed} by a unit compiled with the dynamic model}. The
28635 reason for this is that in the static model, a unit assumes that
28636 its clients guarantee to use (the equivalent of) pragma
28637 @code{Elaborate_All} so that no elaboration checks are required
28638 in inner subprograms, and this assumption is violated if the
28639 client is compiled with dynamic checks.
28641 The precise rule is as follows. A unit that is compiled with dynamic
28642 checks can only @code{with} a unit that meets at least one of the
28643 following criteria:
28648 The @code{with'ed} unit is itself compiled with dynamic elaboration
28649 checks (that is with the @option{-gnatE} switch.
28652 The @code{with'ed} unit is an internal GNAT implementation unit from
28653 the System, Interfaces, Ada, or GNAT hierarchies.
28656 The @code{with'ed} unit has pragma Preelaborate or pragma Pure.
28659 The @code{with'ing} unit (that is the client) has an explicit pragma
28660 @code{Elaborate_All} for the @code{with'ed} unit.
28665 If this rule is violated, that is if a unit with dynamic elaboration
28666 checks @code{with's} a unit that does not meet one of the above four
28667 criteria, then the binder (@code{gnatbind}) will issue a warning
28668 similar to that in the following example:
28671 warning: "x.ads" has dynamic elaboration checks and with's
28672 warning: "y.ads" which has static elaboration checks
28676 These warnings indicate that the rule has been violated, and that as a result
28677 elaboration checks may be missed in the resulting executable file.
28678 This warning may be suppressed using the @option{-ws} binder switch
28679 in the usual manner.
28681 One useful application of this mixing rule is in the case of a subsystem
28682 which does not itself @code{with} units from the remainder of the
28683 application. In this case, the entire subsystem can be compiled with
28684 dynamic checks to resolve a circularity in the subsystem, while
28685 allowing the main application that uses this subsystem to be compiled
28686 using the more reliable default static model.
28688 @node What to Do If the Default Elaboration Behavior Fails
28689 @section What to Do If the Default Elaboration Behavior Fails
28692 If the binder cannot find an acceptable order, it outputs detailed
28693 diagnostics. For example:
28699 error: elaboration circularity detected
28700 info: "proc (body)" must be elaborated before "pack (body)"
28701 info: reason: Elaborate_All probably needed in unit "pack (body)"
28702 info: recompile "pack (body)" with -gnatwl
28703 info: for full details
28704 info: "proc (body)"
28705 info: is needed by its spec:
28706 info: "proc (spec)"
28707 info: which is withed by:
28708 info: "pack (body)"
28709 info: "pack (body)" must be elaborated before "proc (body)"
28710 info: reason: pragma Elaborate in unit "proc (body)"
28716 In this case we have a cycle that the binder cannot break. On the one
28717 hand, there is an explicit pragma Elaborate in @code{proc} for
28718 @code{pack}. This means that the body of @code{pack} must be elaborated
28719 before the body of @code{proc}. On the other hand, there is elaboration
28720 code in @code{pack} that calls a subprogram in @code{proc}. This means
28721 that for maximum safety, there should really be a pragma
28722 Elaborate_All in @code{pack} for @code{proc} which would require that
28723 the body of @code{proc} be elaborated before the body of
28724 @code{pack}. Clearly both requirements cannot be satisfied.
28725 Faced with a circularity of this kind, you have three different options.
28728 @item Fix the program
28729 The most desirable option from the point of view of long-term maintenance
28730 is to rearrange the program so that the elaboration problems are avoided.
28731 One useful technique is to place the elaboration code into separate
28732 child packages. Another is to move some of the initialization code to
28733 explicitly called subprograms, where the program controls the order
28734 of initialization explicitly. Although this is the most desirable option,
28735 it may be impractical and involve too much modification, especially in
28736 the case of complex legacy code.
28738 @item Perform dynamic checks
28739 If the compilations are done using the
28741 (dynamic elaboration check) switch, then GNAT behaves in a quite different
28742 manner. Dynamic checks are generated for all calls that could possibly result
28743 in raising an exception. With this switch, the compiler does not generate
28744 implicit @code{Elaborate} or @code{Elaborate_All} pragmas. The behavior then is
28745 exactly as specified in the @cite{Ada Reference Manual}.
28746 The binder will generate
28747 an executable program that may or may not raise @code{Program_Error}, and then
28748 it is the programmer's job to ensure that it does not raise an exception. Note
28749 that it is important to compile all units with the switch, it cannot be used
28752 @item Suppress checks
28753 The drawback of dynamic checks is that they generate a
28754 significant overhead at run time, both in space and time. If you
28755 are absolutely sure that your program cannot raise any elaboration
28756 exceptions, and you still want to use the dynamic elaboration model,
28757 then you can use the configuration pragma
28758 @code{Suppress (Elaboration_Check)} to suppress all such checks. For
28759 example this pragma could be placed in the @file{gnat.adc} file.
28761 @item Suppress checks selectively
28762 When you know that certain calls or instantiations in elaboration code cannot
28763 possibly lead to an elaboration error, and the binder nevertheless complains
28764 about implicit @code{Elaborate} and @code{Elaborate_All} pragmas that lead to
28765 elaboration circularities, it is possible to remove those warnings locally and
28766 obtain a program that will bind. Clearly this can be unsafe, and it is the
28767 responsibility of the programmer to make sure that the resulting program has no
28768 elaboration anomalies. The pragma @code{Suppress (Elaboration_Check)} can be
28769 used with different granularity to suppress warnings and break elaboration
28774 Place the pragma that names the called subprogram in the declarative part
28775 that contains the call.
28778 Place the pragma in the declarative part, without naming an entity. This
28779 disables warnings on all calls in the corresponding declarative region.
28782 Place the pragma in the package spec that declares the called subprogram,
28783 and name the subprogram. This disables warnings on all elaboration calls to
28787 Place the pragma in the package spec that declares the called subprogram,
28788 without naming any entity. This disables warnings on all elaboration calls to
28789 all subprograms declared in this spec.
28791 @item Use Pragma Elaborate
28792 As previously described in section @xref{Treatment of Pragma Elaborate},
28793 GNAT in static mode assumes that a @code{pragma} Elaborate indicates correctly
28794 that no elaboration checks are required on calls to the designated unit.
28795 There may be cases in which the caller knows that no transitive calls
28796 can occur, so that a @code{pragma Elaborate} will be sufficient in a
28797 case where @code{pragma Elaborate_All} would cause a circularity.
28801 These five cases are listed in order of decreasing safety, and therefore
28802 require increasing programmer care in their application. Consider the
28805 @smallexample @c adanocomment
28807 function F1 return Integer;
28812 function F2 return Integer;
28813 function Pure (x : integer) return integer;
28814 -- pragma Suppress (Elaboration_Check, On => Pure); -- (3)
28815 -- pragma Suppress (Elaboration_Check); -- (4)
28819 package body Pack1 is
28820 function F1 return Integer is
28824 Val : integer := Pack2.Pure (11); -- Elab. call (1)
28827 -- pragma Suppress(Elaboration_Check, Pack2.F2); -- (1)
28828 -- pragma Suppress(Elaboration_Check); -- (2)
28830 X1 := Pack2.F2 + 1; -- Elab. call (2)
28835 package body Pack2 is
28836 function F2 return Integer is
28840 function Pure (x : integer) return integer is
28842 return x ** 3 - 3 * x;
28846 with Pack1, Ada.Text_IO;
28849 Ada.Text_IO.Put_Line(Pack1.X1'Img); -- 101
28852 In the absence of any pragmas, an attempt to bind this program produces
28853 the following diagnostics:
28859 error: elaboration circularity detected
28860 info: "pack1 (body)" must be elaborated before "pack1 (body)"
28861 info: reason: Elaborate_All probably needed in unit "pack1 (body)"
28862 info: recompile "pack1 (body)" with -gnatwl for full details
28863 info: "pack1 (body)"
28864 info: must be elaborated along with its spec:
28865 info: "pack1 (spec)"
28866 info: which is withed by:
28867 info: "pack2 (body)"
28868 info: which must be elaborated along with its spec:
28869 info: "pack2 (spec)"
28870 info: which is withed by:
28871 info: "pack1 (body)"
28874 The sources of the circularity are the two calls to @code{Pack2.Pure} and
28875 @code{Pack2.F2} in the body of @code{Pack1}. We can see that the call to
28876 F2 is safe, even though F2 calls F1, because the call appears after the
28877 elaboration of the body of F1. Therefore the pragma (1) is safe, and will
28878 remove the warning on the call. It is also possible to use pragma (2)
28879 because there are no other potentially unsafe calls in the block.
28882 The call to @code{Pure} is safe because this function does not depend on the
28883 state of @code{Pack2}. Therefore any call to this function is safe, and it
28884 is correct to place pragma (3) in the corresponding package spec.
28887 Finally, we could place pragma (4) in the spec of @code{Pack2} to disable
28888 warnings on all calls to functions declared therein. Note that this is not
28889 necessarily safe, and requires more detailed examination of the subprogram
28890 bodies involved. In particular, a call to @code{F2} requires that @code{F1}
28891 be already elaborated.
28895 It is hard to generalize on which of these four approaches should be
28896 taken. Obviously if it is possible to fix the program so that the default
28897 treatment works, this is preferable, but this may not always be practical.
28898 It is certainly simple enough to use
28900 but the danger in this case is that, even if the GNAT binder
28901 finds a correct elaboration order, it may not always do so,
28902 and certainly a binder from another Ada compiler might not. A
28903 combination of testing and analysis (for which the warnings generated
28906 switch can be useful) must be used to ensure that the program is free
28907 of errors. One switch that is useful in this testing is the
28908 @option{^-p (pessimistic elaboration order)^/PESSIMISTIC_ELABORATION_ORDER^}
28911 Normally the binder tries to find an order that has the best chance
28912 of avoiding elaboration problems. However, if this switch is used, the binder
28913 plays a devil's advocate role, and tries to choose the order that
28914 has the best chance of failing. If your program works even with this
28915 switch, then it has a better chance of being error free, but this is still
28918 For an example of this approach in action, consider the C-tests (executable
28919 tests) from the ACVC suite. If these are compiled and run with the default
28920 treatment, then all but one of them succeed without generating any error
28921 diagnostics from the binder. However, there is one test that fails, and
28922 this is not surprising, because the whole point of this test is to ensure
28923 that the compiler can handle cases where it is impossible to determine
28924 a correct order statically, and it checks that an exception is indeed
28925 raised at run time.
28927 This one test must be compiled and run using the
28929 switch, and then it passes. Alternatively, the entire suite can
28930 be run using this switch. It is never wrong to run with the dynamic
28931 elaboration switch if your code is correct, and we assume that the
28932 C-tests are indeed correct (it is less efficient, but efficiency is
28933 not a factor in running the ACVC tests.)
28935 @node Elaboration for Access-to-Subprogram Values
28936 @section Elaboration for Access-to-Subprogram Values
28937 @cindex Access-to-subprogram
28940 Access-to-subprogram types (introduced in Ada 95) complicate
28941 the handling of elaboration. The trouble is that it becomes
28942 impossible to tell at compile time which procedure
28943 is being called. This means that it is not possible for the binder
28944 to analyze the elaboration requirements in this case.
28946 If at the point at which the access value is created
28947 (i.e., the evaluation of @code{P'Access} for a subprogram @code{P}),
28948 the body of the subprogram is
28949 known to have been elaborated, then the access value is safe, and its use
28950 does not require a check. This may be achieved by appropriate arrangement
28951 of the order of declarations if the subprogram is in the current unit,
28952 or, if the subprogram is in another unit, by using pragma
28953 @code{Pure}, @code{Preelaborate}, or @code{Elaborate_Body}
28954 on the referenced unit.
28956 If the referenced body is not known to have been elaborated at the point
28957 the access value is created, then any use of the access value must do a
28958 dynamic check, and this dynamic check will fail and raise a
28959 @code{Program_Error} exception if the body has not been elaborated yet.
28960 GNAT will generate the necessary checks, and in addition, if the
28962 switch is set, will generate warnings that such checks are required.
28964 The use of dynamic dispatching for tagged types similarly generates
28965 a requirement for dynamic checks, and premature calls to any primitive
28966 operation of a tagged type before the body of the operation has been
28967 elaborated, will result in the raising of @code{Program_Error}.
28969 @node Summary of Procedures for Elaboration Control
28970 @section Summary of Procedures for Elaboration Control
28971 @cindex Elaboration control
28974 First, compile your program with the default options, using none of
28975 the special elaboration control switches. If the binder successfully
28976 binds your program, then you can be confident that, apart from issues
28977 raised by the use of access-to-subprogram types and dynamic dispatching,
28978 the program is free of elaboration errors. If it is important that the
28979 program be portable, then use the
28981 switch to generate warnings about missing @code{Elaborate} or
28982 @code{Elaborate_All} pragmas, and supply the missing pragmas.
28984 If the program fails to bind using the default static elaboration
28985 handling, then you can fix the program to eliminate the binder
28986 message, or recompile the entire program with the
28987 @option{-gnatE} switch to generate dynamic elaboration checks,
28988 and, if you are sure there really are no elaboration problems,
28989 use a global pragma @code{Suppress (Elaboration_Check)}.
28991 @node Other Elaboration Order Considerations
28992 @section Other Elaboration Order Considerations
28994 This section has been entirely concerned with the issue of finding a valid
28995 elaboration order, as defined by the Ada Reference Manual. In a case
28996 where several elaboration orders are valid, the task is to find one
28997 of the possible valid elaboration orders (and the static model in GNAT
28998 will ensure that this is achieved).
29000 The purpose of the elaboration rules in the Ada Reference Manual is to
29001 make sure that no entity is accessed before it has been elaborated. For
29002 a subprogram, this means that the spec and body must have been elaborated
29003 before the subprogram is called. For an object, this means that the object
29004 must have been elaborated before its value is read or written. A violation
29005 of either of these two requirements is an access before elaboration order,
29006 and this section has been all about avoiding such errors.
29008 In the case where more than one order of elaboration is possible, in the
29009 sense that access before elaboration errors are avoided, then any one of
29010 the orders is ``correct'' in the sense that it meets the requirements of
29011 the Ada Reference Manual, and no such error occurs.
29013 However, it may be the case for a given program, that there are
29014 constraints on the order of elaboration that come not from consideration
29015 of avoiding elaboration errors, but rather from extra-lingual logic
29016 requirements. Consider this example:
29018 @smallexample @c ada
29019 with Init_Constants;
29020 package Constants is
29025 package Init_Constants is
29026 procedure P; -- require a body
29027 end Init_Constants;
29030 package body Init_Constants is
29031 procedure P is begin null; end;
29035 end Init_Constants;
29039 Z : Integer := Constants.X + Constants.Y;
29043 with Text_IO; use Text_IO;
29046 Put_Line (Calc.Z'Img);
29051 In this example, there is more than one valid order of elaboration. For
29052 example both the following are correct orders:
29055 Init_Constants spec
29058 Init_Constants body
29063 Init_Constants spec
29064 Init_Constants body
29071 There is no language rule to prefer one or the other, both are correct
29072 from an order of elaboration point of view. But the programmatic effects
29073 of the two orders are very different. In the first, the elaboration routine
29074 of @code{Calc} initializes @code{Z} to zero, and then the main program
29075 runs with this value of zero. But in the second order, the elaboration
29076 routine of @code{Calc} runs after the body of Init_Constants has set
29077 @code{X} and @code{Y} and thus @code{Z} is set to 7 before @code{Main}
29080 One could perhaps by applying pretty clever non-artificial intelligence
29081 to the situation guess that it is more likely that the second order of
29082 elaboration is the one desired, but there is no formal linguistic reason
29083 to prefer one over the other. In fact in this particular case, GNAT will
29084 prefer the second order, because of the rule that bodies are elaborated
29085 as soon as possible, but it's just luck that this is what was wanted
29086 (if indeed the second order was preferred).
29088 If the program cares about the order of elaboration routines in a case like
29089 this, it is important to specify the order required. In this particular
29090 case, that could have been achieved by adding to the spec of Calc:
29092 @smallexample @c ada
29093 pragma Elaborate_All (Constants);
29097 which requires that the body (if any) and spec of @code{Constants},
29098 as well as the body and spec of any unit @code{with}'ed by
29099 @code{Constants} be elaborated before @code{Calc} is elaborated.
29101 Clearly no automatic method can always guess which alternative you require,
29102 and if you are working with legacy code that had constraints of this kind
29103 which were not properly specified by adding @code{Elaborate} or
29104 @code{Elaborate_All} pragmas, then indeed it is possible that two different
29105 compilers can choose different orders.
29107 However, GNAT does attempt to diagnose the common situation where there
29108 are uninitialized variables in the visible part of a package spec, and the
29109 corresponding package body has an elaboration block that directly or
29110 indirectly initialized one or more of these variables. This is the situation
29111 in which a pragma Elaborate_Body is usually desirable, and GNAT will generate
29112 a warning that suggests this addition if it detects this situation.
29114 The @code{gnatbind}
29115 @option{^-p^/PESSIMISTIC_ELABORATION^} switch may be useful in smoking
29116 out problems. This switch causes bodies to be elaborated as late as possible
29117 instead of as early as possible. In the example above, it would have forced
29118 the choice of the first elaboration order. If you get different results
29119 when using this switch, and particularly if one set of results is right,
29120 and one is wrong as far as you are concerned, it shows that you have some
29121 missing @code{Elaborate} pragmas. For the example above, we have the
29125 gnatmake -f -q main
29128 gnatmake -f -q main -bargs -p
29134 It is of course quite unlikely that both these results are correct, so
29135 it is up to you in a case like this to investigate the source of the
29136 difference, by looking at the two elaboration orders that are chosen,
29137 and figuring out which is correct, and then adding the necessary
29138 @code{Elaborate} or @code{Elaborate_All} pragmas to ensure the desired order.
29142 @c *******************************
29143 @node Conditional Compilation
29144 @appendix Conditional Compilation
29145 @c *******************************
29146 @cindex Conditional compilation
29149 It is often necessary to arrange for a single source program
29150 to serve multiple purposes, where it is compiled in different
29151 ways to achieve these different goals. Some examples of the
29152 need for this feature are
29155 @item Adapting a program to a different hardware environment
29156 @item Adapting a program to a different target architecture
29157 @item Turning debugging features on and off
29158 @item Arranging for a program to compile with different compilers
29162 In C, or C++, the typical approach would be to use the preprocessor
29163 that is defined as part of the language. The Ada language does not
29164 contain such a feature. This is not an oversight, but rather a very
29165 deliberate design decision, based on the experience that overuse of
29166 the preprocessing features in C and C++ can result in programs that
29167 are extremely difficult to maintain. For example, if we have ten
29168 switches that can be on or off, this means that there are a thousand
29169 separate programs, any one of which might not even be syntactically
29170 correct, and even if syntactically correct, the resulting program
29171 might not work correctly. Testing all combinations can quickly become
29174 Nevertheless, the need to tailor programs certainly exists, and in
29175 this Appendix we will discuss how this can
29176 be achieved using Ada in general, and GNAT in particular.
29179 * Use of Boolean Constants::
29180 * Debugging - A Special Case::
29181 * Conditionalizing Declarations::
29182 * Use of Alternative Implementations::
29186 @node Use of Boolean Constants
29187 @section Use of Boolean Constants
29190 In the case where the difference is simply which code
29191 sequence is executed, the cleanest solution is to use Boolean
29192 constants to control which code is executed.
29194 @smallexample @c ada
29196 FP_Initialize_Required : constant Boolean := True;
29198 if FP_Initialize_Required then
29205 Not only will the code inside the @code{if} statement not be executed if
29206 the constant Boolean is @code{False}, but it will also be completely
29207 deleted from the program.
29208 However, the code is only deleted after the @code{if} statement
29209 has been checked for syntactic and semantic correctness.
29210 (In contrast, with preprocessors the code is deleted before the
29211 compiler ever gets to see it, so it is not checked until the switch
29213 @cindex Preprocessors (contrasted with conditional compilation)
29215 Typically the Boolean constants will be in a separate package,
29218 @smallexample @c ada
29221 FP_Initialize_Required : constant Boolean := True;
29222 Reset_Available : constant Boolean := False;
29229 The @code{Config} package exists in multiple forms for the various targets,
29230 with an appropriate script selecting the version of @code{Config} needed.
29231 Then any other unit requiring conditional compilation can do a @code{with}
29232 of @code{Config} to make the constants visible.
29235 @node Debugging - A Special Case
29236 @section Debugging - A Special Case
29239 A common use of conditional code is to execute statements (for example
29240 dynamic checks, or output of intermediate results) under control of a
29241 debug switch, so that the debugging behavior can be turned on and off.
29242 This can be done using a Boolean constant to control whether the code
29245 @smallexample @c ada
29248 Put_Line ("got to the first stage!");
29256 @smallexample @c ada
29258 if Debugging and then Temperature > 999.0 then
29259 raise Temperature_Crazy;
29265 Since this is a common case, there are special features to deal with
29266 this in a convenient manner. For the case of tests, Ada 2005 has added
29267 a pragma @code{Assert} that can be used for such tests. This pragma is modeled
29268 @cindex pragma @code{Assert}
29269 on the @code{Assert} pragma that has always been available in GNAT, so this
29270 feature may be used with GNAT even if you are not using Ada 2005 features.
29271 The use of pragma @code{Assert} is described in
29272 @ref{Pragma Assert,,, gnat_rm, GNAT Reference Manual}, but as an
29273 example, the last test could be written:
29275 @smallexample @c ada
29276 pragma Assert (Temperature <= 999.0, "Temperature Crazy");
29282 @smallexample @c ada
29283 pragma Assert (Temperature <= 999.0);
29287 In both cases, if assertions are active and the temperature is excessive,
29288 the exception @code{Assert_Failure} will be raised, with the given string in
29289 the first case or a string indicating the location of the pragma in the second
29290 case used as the exception message.
29292 You can turn assertions on and off by using the @code{Assertion_Policy}
29294 @cindex pragma @code{Assertion_Policy}
29295 This is an Ada 2005 pragma which is implemented in all modes by
29296 GNAT, but only in the latest versions of GNAT which include Ada 2005
29297 capability. Alternatively, you can use the @option{-gnata} switch
29298 @cindex @option{-gnata} switch
29299 to enable assertions from the command line (this is recognized by all versions
29302 For the example above with the @code{Put_Line}, the GNAT-specific pragma
29303 @code{Debug} can be used:
29304 @cindex pragma @code{Debug}
29306 @smallexample @c ada
29307 pragma Debug (Put_Line ("got to the first stage!"));
29311 If debug pragmas are enabled, the argument, which must be of the form of
29312 a procedure call, is executed (in this case, @code{Put_Line} will be called).
29313 Only one call can be present, but of course a special debugging procedure
29314 containing any code you like can be included in the program and then
29315 called in a pragma @code{Debug} argument as needed.
29317 One advantage of pragma @code{Debug} over the @code{if Debugging then}
29318 construct is that pragma @code{Debug} can appear in declarative contexts,
29319 such as at the very beginning of a procedure, before local declarations have
29322 Debug pragmas are enabled using either the @option{-gnata} switch that also
29323 controls assertions, or with a separate Debug_Policy pragma.
29324 @cindex pragma @code{Debug_Policy}
29325 The latter pragma is new in the Ada 2005 versions of GNAT (but it can be used
29326 in Ada 95 and Ada 83 programs as well), and is analogous to
29327 pragma @code{Assertion_Policy} to control assertions.
29329 @code{Assertion_Policy} and @code{Debug_Policy} are configuration pragmas,
29330 and thus they can appear in @file{gnat.adc} if you are not using a
29331 project file, or in the file designated to contain configuration pragmas
29333 They then apply to all subsequent compilations. In practice the use of
29334 the @option{-gnata} switch is often the most convenient method of controlling
29335 the status of these pragmas.
29337 Note that a pragma is not a statement, so in contexts where a statement
29338 sequence is required, you can't just write a pragma on its own. You have
29339 to add a @code{null} statement.
29341 @smallexample @c ada
29344 @dots{} -- some statements
29346 pragma Assert (Num_Cases < 10);
29353 @node Conditionalizing Declarations
29354 @section Conditionalizing Declarations
29357 In some cases, it may be necessary to conditionalize declarations to meet
29358 different requirements. For example we might want a bit string whose length
29359 is set to meet some hardware message requirement.
29361 In some cases, it may be possible to do this using declare blocks controlled
29362 by conditional constants:
29364 @smallexample @c ada
29366 if Small_Machine then
29368 X : Bit_String (1 .. 10);
29374 X : Large_Bit_String (1 .. 1000);
29383 Note that in this approach, both declarations are analyzed by the
29384 compiler so this can only be used where both declarations are legal,
29385 even though one of them will not be used.
29387 Another approach is to define integer constants, e.g.@: @code{Bits_Per_Word}, or
29388 Boolean constants, e.g.@: @code{Little_Endian}, and then write declarations
29389 that are parameterized by these constants. For example
29391 @smallexample @c ada
29394 Field1 at 0 range Boolean'Pos (Little_Endian) * 10 .. Bits_Per_Word;
29400 If @code{Bits_Per_Word} is set to 32, this generates either
29402 @smallexample @c ada
29405 Field1 at 0 range 0 .. 32;
29411 for the big endian case, or
29413 @smallexample @c ada
29416 Field1 at 0 range 10 .. 32;
29422 for the little endian case. Since a powerful subset of Ada expression
29423 notation is usable for creating static constants, clever use of this
29424 feature can often solve quite difficult problems in conditionalizing
29425 compilation (note incidentally that in Ada 95, the little endian
29426 constant was introduced as @code{System.Default_Bit_Order}, so you do not
29427 need to define this one yourself).
29430 @node Use of Alternative Implementations
29431 @section Use of Alternative Implementations
29434 In some cases, none of the approaches described above are adequate. This
29435 can occur for example if the set of declarations required is radically
29436 different for two different configurations.
29438 In this situation, the official Ada way of dealing with conditionalizing
29439 such code is to write separate units for the different cases. As long as
29440 this does not result in excessive duplication of code, this can be done
29441 without creating maintenance problems. The approach is to share common
29442 code as far as possible, and then isolate the code and declarations
29443 that are different. Subunits are often a convenient method for breaking
29444 out a piece of a unit that is to be conditionalized, with separate files
29445 for different versions of the subunit for different targets, where the
29446 build script selects the right one to give to the compiler.
29447 @cindex Subunits (and conditional compilation)
29449 As an example, consider a situation where a new feature in Ada 2005
29450 allows something to be done in a really nice way. But your code must be able
29451 to compile with an Ada 95 compiler. Conceptually you want to say:
29453 @smallexample @c ada
29456 @dots{} neat Ada 2005 code
29458 @dots{} not quite as neat Ada 95 code
29464 where @code{Ada_2005} is a Boolean constant.
29466 But this won't work when @code{Ada_2005} is set to @code{False},
29467 since the @code{then} clause will be illegal for an Ada 95 compiler.
29468 (Recall that although such unreachable code would eventually be deleted
29469 by the compiler, it still needs to be legal. If it uses features
29470 introduced in Ada 2005, it will be illegal in Ada 95.)
29472 So instead we write
29474 @smallexample @c ada
29475 procedure Insert is separate;
29479 Then we have two files for the subunit @code{Insert}, with the two sets of
29481 If the package containing this is called @code{File_Queries}, then we might
29485 @item @file{file_queries-insert-2005.adb}
29486 @item @file{file_queries-insert-95.adb}
29490 and the build script renames the appropriate file to
29493 file_queries-insert.adb
29497 and then carries out the compilation.
29499 This can also be done with project files' naming schemes. For example:
29501 @smallexample @c project
29502 For Body ("File_Queries.Insert") use "file_queries-insert-2005.ada";
29506 Note also that with project files it is desirable to use a different extension
29507 than @file{ads} / @file{adb} for alternative versions. Otherwise a naming
29508 conflict may arise through another commonly used feature: to declare as part
29509 of the project a set of directories containing all the sources obeying the
29510 default naming scheme.
29512 The use of alternative units is certainly feasible in all situations,
29513 and for example the Ada part of the GNAT run-time is conditionalized
29514 based on the target architecture using this approach. As a specific example,
29515 consider the implementation of the AST feature in VMS. There is one
29523 which is the same for all architectures, and three bodies:
29527 used for all non-VMS operating systems
29528 @item s-asthan-vms-alpha.adb
29529 used for VMS on the Alpha
29530 @item s-asthan-vms-ia64.adb
29531 used for VMS on the ia64
29535 The dummy version @file{s-asthan.adb} simply raises exceptions noting that
29536 this operating system feature is not available, and the two remaining
29537 versions interface with the corresponding versions of VMS to provide
29538 VMS-compatible AST handling. The GNAT build script knows the architecture
29539 and operating system, and automatically selects the right version,
29540 renaming it if necessary to @file{s-asthan.adb} before the run-time build.
29542 Another style for arranging alternative implementations is through Ada's
29543 access-to-subprogram facility.
29544 In case some functionality is to be conditionally included,
29545 you can declare an access-to-procedure variable @code{Ref} that is initialized
29546 to designate a ``do nothing'' procedure, and then invoke @code{Ref.all}
29548 In some library package, set @code{Ref} to @code{Proc'Access} for some
29549 procedure @code{Proc} that performs the relevant processing.
29550 The initialization only occurs if the library package is included in the
29552 The same idea can also be implemented using tagged types and dispatching
29556 @node Preprocessing
29557 @section Preprocessing
29558 @cindex Preprocessing
29561 Although it is quite possible to conditionalize code without the use of
29562 C-style preprocessing, as described earlier in this section, it is
29563 nevertheless convenient in some cases to use the C approach. Moreover,
29564 older Ada compilers have often provided some preprocessing capability,
29565 so legacy code may depend on this approach, even though it is not
29568 To accommodate such use, GNAT provides a preprocessor (modeled to a large
29569 extent on the various preprocessors that have been used
29570 with legacy code on other compilers, to enable easier transition).
29572 The preprocessor may be used in two separate modes. It can be used quite
29573 separately from the compiler, to generate a separate output source file
29574 that is then fed to the compiler as a separate step. This is the
29575 @code{gnatprep} utility, whose use is fully described in
29576 @ref{Preprocessing Using gnatprep}.
29577 @cindex @code{gnatprep}
29579 The preprocessing language allows such constructs as
29583 #if DEBUG or PRIORITY > 4 then
29584 bunch of declarations
29586 completely different bunch of declarations
29592 The values of the symbols @code{DEBUG} and @code{PRIORITY} can be
29593 defined either on the command line or in a separate file.
29595 The other way of running the preprocessor is even closer to the C style and
29596 often more convenient. In this approach the preprocessing is integrated into
29597 the compilation process. The compiler is fed the preprocessor input which
29598 includes @code{#if} lines etc, and then the compiler carries out the
29599 preprocessing internally and processes the resulting output.
29600 For more details on this approach, see @ref{Integrated Preprocessing}.
29603 @c *******************************
29604 @node Inline Assembler
29605 @appendix Inline Assembler
29606 @c *******************************
29609 If you need to write low-level software that interacts directly
29610 with the hardware, Ada provides two ways to incorporate assembly
29611 language code into your program. First, you can import and invoke
29612 external routines written in assembly language, an Ada feature fully
29613 supported by GNAT@. However, for small sections of code it may be simpler
29614 or more efficient to include assembly language statements directly
29615 in your Ada source program, using the facilities of the implementation-defined
29616 package @code{System.Machine_Code}, which incorporates the gcc
29617 Inline Assembler. The Inline Assembler approach offers a number of advantages,
29618 including the following:
29621 @item No need to use non-Ada tools
29622 @item Consistent interface over different targets
29623 @item Automatic usage of the proper calling conventions
29624 @item Access to Ada constants and variables
29625 @item Definition of intrinsic routines
29626 @item Possibility of inlining a subprogram comprising assembler code
29627 @item Code optimizer can take Inline Assembler code into account
29630 This chapter presents a series of examples to show you how to use
29631 the Inline Assembler. Although it focuses on the Intel x86,
29632 the general approach applies also to other processors.
29633 It is assumed that you are familiar with Ada
29634 and with assembly language programming.
29637 * Basic Assembler Syntax::
29638 * A Simple Example of Inline Assembler::
29639 * Output Variables in Inline Assembler::
29640 * Input Variables in Inline Assembler::
29641 * Inlining Inline Assembler Code::
29642 * Other Asm Functionality::
29645 @c ---------------------------------------------------------------------------
29646 @node Basic Assembler Syntax
29647 @section Basic Assembler Syntax
29650 The assembler used by GNAT and gcc is based not on the Intel assembly
29651 language, but rather on a language that descends from the AT&T Unix
29652 assembler @emph{as} (and which is often referred to as ``AT&T syntax'').
29653 The following table summarizes the main features of @emph{as} syntax
29654 and points out the differences from the Intel conventions.
29655 See the gcc @emph{as} and @emph{gas} (an @emph{as} macro
29656 pre-processor) documentation for further information.
29659 @item Register names
29660 gcc / @emph{as}: Prefix with ``%''; for example @code{%eax}
29662 Intel: No extra punctuation; for example @code{eax}
29664 @item Immediate operand
29665 gcc / @emph{as}: Prefix with ``$''; for example @code{$4}
29667 Intel: No extra punctuation; for example @code{4}
29670 gcc / @emph{as}: Prefix with ``$''; for example @code{$loc}
29672 Intel: No extra punctuation; for example @code{loc}
29674 @item Memory contents
29675 gcc / @emph{as}: No extra punctuation; for example @code{loc}
29677 Intel: Square brackets; for example @code{[loc]}
29679 @item Register contents
29680 gcc / @emph{as}: Parentheses; for example @code{(%eax)}
29682 Intel: Square brackets; for example @code{[eax]}
29684 @item Hexadecimal numbers
29685 gcc / @emph{as}: Leading ``0x'' (C language syntax); for example @code{0xA0}
29687 Intel: Trailing ``h''; for example @code{A0h}
29690 gcc / @emph{as}: Explicit in op code; for example @code{movw} to move
29693 Intel: Implicit, deduced by assembler; for example @code{mov}
29695 @item Instruction repetition
29696 gcc / @emph{as}: Split into two lines; for example
29702 Intel: Keep on one line; for example @code{rep stosl}
29704 @item Order of operands
29705 gcc / @emph{as}: Source first; for example @code{movw $4, %eax}
29707 Intel: Destination first; for example @code{mov eax, 4}
29710 @c ---------------------------------------------------------------------------
29711 @node A Simple Example of Inline Assembler
29712 @section A Simple Example of Inline Assembler
29715 The following example will generate a single assembly language statement,
29716 @code{nop}, which does nothing. Despite its lack of run-time effect,
29717 the example will be useful in illustrating the basics of
29718 the Inline Assembler facility.
29720 @smallexample @c ada
29722 with System.Machine_Code; use System.Machine_Code;
29723 procedure Nothing is
29730 @code{Asm} is a procedure declared in package @code{System.Machine_Code};
29731 here it takes one parameter, a @emph{template string} that must be a static
29732 expression and that will form the generated instruction.
29733 @code{Asm} may be regarded as a compile-time procedure that parses
29734 the template string and additional parameters (none here),
29735 from which it generates a sequence of assembly language instructions.
29737 The examples in this chapter will illustrate several of the forms
29738 for invoking @code{Asm}; a complete specification of the syntax
29739 is found in @ref{Machine Code Insertions,,, gnat_rm, GNAT Reference
29742 Under the standard GNAT conventions, the @code{Nothing} procedure
29743 should be in a file named @file{nothing.adb}.
29744 You can build the executable in the usual way:
29748 However, the interesting aspect of this example is not its run-time behavior
29749 but rather the generated assembly code.
29750 To see this output, invoke the compiler as follows:
29752 gcc -c -S -fomit-frame-pointer -gnatp @file{nothing.adb}
29754 where the options are:
29758 compile only (no bind or link)
29760 generate assembler listing
29761 @item -fomit-frame-pointer
29762 do not set up separate stack frames
29764 do not add runtime checks
29767 This gives a human-readable assembler version of the code. The resulting
29768 file will have the same name as the Ada source file, but with a @code{.s}
29769 extension. In our example, the file @file{nothing.s} has the following
29774 .file "nothing.adb"
29776 ___gnu_compiled_ada:
29779 .globl __ada_nothing
29791 The assembly code you included is clearly indicated by
29792 the compiler, between the @code{#APP} and @code{#NO_APP}
29793 delimiters. The character before the 'APP' and 'NOAPP'
29794 can differ on different targets. For example, GNU/Linux uses '#APP' while
29795 on NT you will see '/APP'.
29797 If you make a mistake in your assembler code (such as using the
29798 wrong size modifier, or using a wrong operand for the instruction) GNAT
29799 will report this error in a temporary file, which will be deleted when
29800 the compilation is finished. Generating an assembler file will help
29801 in such cases, since you can assemble this file separately using the
29802 @emph{as} assembler that comes with gcc.
29804 Assembling the file using the command
29807 as @file{nothing.s}
29810 will give you error messages whose lines correspond to the assembler
29811 input file, so you can easily find and correct any mistakes you made.
29812 If there are no errors, @emph{as} will generate an object file
29813 @file{nothing.out}.
29815 @c ---------------------------------------------------------------------------
29816 @node Output Variables in Inline Assembler
29817 @section Output Variables in Inline Assembler
29820 The examples in this section, showing how to access the processor flags,
29821 illustrate how to specify the destination operands for assembly language
29824 @smallexample @c ada
29826 with Interfaces; use Interfaces;
29827 with Ada.Text_IO; use Ada.Text_IO;
29828 with System.Machine_Code; use System.Machine_Code;
29829 procedure Get_Flags is
29830 Flags : Unsigned_32;
29833 Asm ("pushfl" & LF & HT & -- push flags on stack
29834 "popl %%eax" & LF & HT & -- load eax with flags
29835 "movl %%eax, %0", -- store flags in variable
29836 Outputs => Unsigned_32'Asm_Output ("=g", Flags));
29837 Put_Line ("Flags register:" & Flags'Img);
29842 In order to have a nicely aligned assembly listing, we have separated
29843 multiple assembler statements in the Asm template string with linefeed
29844 (ASCII.LF) and horizontal tab (ASCII.HT) characters.
29845 The resulting section of the assembly output file is:
29852 movl %eax, -40(%ebp)
29857 It would have been legal to write the Asm invocation as:
29860 Asm ("pushfl popl %%eax movl %%eax, %0")
29863 but in the generated assembler file, this would come out as:
29867 pushfl popl %eax movl %eax, -40(%ebp)
29871 which is not so convenient for the human reader.
29873 We use Ada comments
29874 at the end of each line to explain what the assembler instructions
29875 actually do. This is a useful convention.
29877 When writing Inline Assembler instructions, you need to precede each register
29878 and variable name with a percent sign. Since the assembler already requires
29879 a percent sign at the beginning of a register name, you need two consecutive
29880 percent signs for such names in the Asm template string, thus @code{%%eax}.
29881 In the generated assembly code, one of the percent signs will be stripped off.
29883 Names such as @code{%0}, @code{%1}, @code{%2}, etc., denote input or output
29884 variables: operands you later define using @code{Input} or @code{Output}
29885 parameters to @code{Asm}.
29886 An output variable is illustrated in
29887 the third statement in the Asm template string:
29891 The intent is to store the contents of the eax register in a variable that can
29892 be accessed in Ada. Simply writing @code{movl %%eax, Flags} would not
29893 necessarily work, since the compiler might optimize by using a register
29894 to hold Flags, and the expansion of the @code{movl} instruction would not be
29895 aware of this optimization. The solution is not to store the result directly
29896 but rather to advise the compiler to choose the correct operand form;
29897 that is the purpose of the @code{%0} output variable.
29899 Information about the output variable is supplied in the @code{Outputs}
29900 parameter to @code{Asm}:
29902 Outputs => Unsigned_32'Asm_Output ("=g", Flags));
29905 The output is defined by the @code{Asm_Output} attribute of the target type;
29906 the general format is
29908 Type'Asm_Output (constraint_string, variable_name)
29911 The constraint string directs the compiler how
29912 to store/access the associated variable. In the example
29914 Unsigned_32'Asm_Output ("=m", Flags);
29916 the @code{"m"} (memory) constraint tells the compiler that the variable
29917 @code{Flags} should be stored in a memory variable, thus preventing
29918 the optimizer from keeping it in a register. In contrast,
29920 Unsigned_32'Asm_Output ("=r", Flags);
29922 uses the @code{"r"} (register) constraint, telling the compiler to
29923 store the variable in a register.
29925 If the constraint is preceded by the equal character (@strong{=}), it tells
29926 the compiler that the variable will be used to store data into it.
29928 In the @code{Get_Flags} example, we used the @code{"g"} (global) constraint,
29929 allowing the optimizer to choose whatever it deems best.
29931 There are a fairly large number of constraints, but the ones that are
29932 most useful (for the Intel x86 processor) are the following:
29938 global (i.e.@: can be stored anywhere)
29956 use one of eax, ebx, ecx or edx
29958 use one of eax, ebx, ecx, edx, esi or edi
29961 The full set of constraints is described in the gcc and @emph{as}
29962 documentation; note that it is possible to combine certain constraints
29963 in one constraint string.
29965 You specify the association of an output variable with an assembler operand
29966 through the @code{%}@emph{n} notation, where @emph{n} is a non-negative
29968 @smallexample @c ada
29970 Asm ("pushfl" & LF & HT & -- push flags on stack
29971 "popl %%eax" & LF & HT & -- load eax with flags
29972 "movl %%eax, %0", -- store flags in variable
29973 Outputs => Unsigned_32'Asm_Output ("=g", Flags));
29977 @code{%0} will be replaced in the expanded code by the appropriate operand,
29979 the compiler decided for the @code{Flags} variable.
29981 In general, you may have any number of output variables:
29984 Count the operands starting at 0; thus @code{%0}, @code{%1}, etc.
29986 Specify the @code{Outputs} parameter as a parenthesized comma-separated list
29987 of @code{Asm_Output} attributes
29991 @smallexample @c ada
29993 Asm ("movl %%eax, %0" & LF & HT &
29994 "movl %%ebx, %1" & LF & HT &
29996 Outputs => (Unsigned_32'Asm_Output ("=g", Var_A), -- %0 = Var_A
29997 Unsigned_32'Asm_Output ("=g", Var_B), -- %1 = Var_B
29998 Unsigned_32'Asm_Output ("=g", Var_C))); -- %2 = Var_C
30002 where @code{Var_A}, @code{Var_B}, and @code{Var_C} are variables
30003 in the Ada program.
30005 As a variation on the @code{Get_Flags} example, we can use the constraints
30006 string to direct the compiler to store the eax register into the @code{Flags}
30007 variable, instead of including the store instruction explicitly in the
30008 @code{Asm} template string:
30010 @smallexample @c ada
30012 with Interfaces; use Interfaces;
30013 with Ada.Text_IO; use Ada.Text_IO;
30014 with System.Machine_Code; use System.Machine_Code;
30015 procedure Get_Flags_2 is
30016 Flags : Unsigned_32;
30019 Asm ("pushfl" & LF & HT & -- push flags on stack
30020 "popl %%eax", -- save flags in eax
30021 Outputs => Unsigned_32'Asm_Output ("=a", Flags));
30022 Put_Line ("Flags register:" & Flags'Img);
30028 The @code{"a"} constraint tells the compiler that the @code{Flags}
30029 variable will come from the eax register. Here is the resulting code:
30037 movl %eax,-40(%ebp)
30042 The compiler generated the store of eax into Flags after
30043 expanding the assembler code.
30045 Actually, there was no need to pop the flags into the eax register;
30046 more simply, we could just pop the flags directly into the program variable:
30048 @smallexample @c ada
30050 with Interfaces; use Interfaces;
30051 with Ada.Text_IO; use Ada.Text_IO;
30052 with System.Machine_Code; use System.Machine_Code;
30053 procedure Get_Flags_3 is
30054 Flags : Unsigned_32;
30057 Asm ("pushfl" & LF & HT & -- push flags on stack
30058 "pop %0", -- save flags in Flags
30059 Outputs => Unsigned_32'Asm_Output ("=g", Flags));
30060 Put_Line ("Flags register:" & Flags'Img);
30065 @c ---------------------------------------------------------------------------
30066 @node Input Variables in Inline Assembler
30067 @section Input Variables in Inline Assembler
30070 The example in this section illustrates how to specify the source operands
30071 for assembly language statements.
30072 The program simply increments its input value by 1:
30074 @smallexample @c ada
30076 with Interfaces; use Interfaces;
30077 with Ada.Text_IO; use Ada.Text_IO;
30078 with System.Machine_Code; use System.Machine_Code;
30079 procedure Increment is
30081 function Incr (Value : Unsigned_32) return Unsigned_32 is
30082 Result : Unsigned_32;
30085 Inputs => Unsigned_32'Asm_Input ("a", Value),
30086 Outputs => Unsigned_32'Asm_Output ("=a", Result));
30090 Value : Unsigned_32;
30094 Put_Line ("Value before is" & Value'Img);
30095 Value := Incr (Value);
30096 Put_Line ("Value after is" & Value'Img);
30101 The @code{Outputs} parameter to @code{Asm} specifies
30102 that the result will be in the eax register and that it is to be stored
30103 in the @code{Result} variable.
30105 The @code{Inputs} parameter looks much like the @code{Outputs} parameter,
30106 but with an @code{Asm_Input} attribute.
30107 The @code{"="} constraint, indicating an output value, is not present.
30109 You can have multiple input variables, in the same way that you can have more
30110 than one output variable.
30112 The parameter count (%0, %1) etc, now starts at the first input
30113 statement, and continues with the output statements.
30114 When both parameters use the same variable, the
30115 compiler will treat them as the same %n operand, which is the case here.
30117 Just as the @code{Outputs} parameter causes the register to be stored into the
30118 target variable after execution of the assembler statements, so does the
30119 @code{Inputs} parameter cause its variable to be loaded into the register
30120 before execution of the assembler statements.
30122 Thus the effect of the @code{Asm} invocation is:
30124 @item load the 32-bit value of @code{Value} into eax
30125 @item execute the @code{incl %eax} instruction
30126 @item store the contents of eax into the @code{Result} variable
30129 The resulting assembler file (with @option{-O2} optimization) contains:
30132 _increment__incr.1:
30145 @c ---------------------------------------------------------------------------
30146 @node Inlining Inline Assembler Code
30147 @section Inlining Inline Assembler Code
30150 For a short subprogram such as the @code{Incr} function in the previous
30151 section, the overhead of the call and return (creating / deleting the stack
30152 frame) can be significant, compared to the amount of code in the subprogram
30153 body. A solution is to apply Ada's @code{Inline} pragma to the subprogram,
30154 which directs the compiler to expand invocations of the subprogram at the
30155 point(s) of call, instead of setting up a stack frame for out-of-line calls.
30156 Here is the resulting program:
30158 @smallexample @c ada
30160 with Interfaces; use Interfaces;
30161 with Ada.Text_IO; use Ada.Text_IO;
30162 with System.Machine_Code; use System.Machine_Code;
30163 procedure Increment_2 is
30165 function Incr (Value : Unsigned_32) return Unsigned_32 is
30166 Result : Unsigned_32;
30169 Inputs => Unsigned_32'Asm_Input ("a", Value),
30170 Outputs => Unsigned_32'Asm_Output ("=a", Result));
30173 pragma Inline (Increment);
30175 Value : Unsigned_32;
30179 Put_Line ("Value before is" & Value'Img);
30180 Value := Increment (Value);
30181 Put_Line ("Value after is" & Value'Img);
30186 Compile the program with both optimization (@option{-O2}) and inlining
30187 (@option{-gnatn}) enabled.
30189 The @code{Incr} function is still compiled as usual, but at the
30190 point in @code{Increment} where our function used to be called:
30195 call _increment__incr.1
30200 the code for the function body directly appears:
30213 thus saving the overhead of stack frame setup and an out-of-line call.
30215 @c ---------------------------------------------------------------------------
30216 @node Other Asm Functionality
30217 @section Other @code{Asm} Functionality
30220 This section describes two important parameters to the @code{Asm}
30221 procedure: @code{Clobber}, which identifies register usage;
30222 and @code{Volatile}, which inhibits unwanted optimizations.
30225 * The Clobber Parameter::
30226 * The Volatile Parameter::
30229 @c ---------------------------------------------------------------------------
30230 @node The Clobber Parameter
30231 @subsection The @code{Clobber} Parameter
30234 One of the dangers of intermixing assembly language and a compiled language
30235 such as Ada is that the compiler needs to be aware of which registers are
30236 being used by the assembly code. In some cases, such as the earlier examples,
30237 the constraint string is sufficient to indicate register usage (e.g.,
30239 the eax register). But more generally, the compiler needs an explicit
30240 identification of the registers that are used by the Inline Assembly
30243 Using a register that the compiler doesn't know about
30244 could be a side effect of an instruction (like @code{mull}
30245 storing its result in both eax and edx).
30246 It can also arise from explicit register usage in your
30247 assembly code; for example:
30250 Asm ("movl %0, %%ebx" & LF & HT &
30252 Inputs => Unsigned_32'Asm_Input ("g", Var_In),
30253 Outputs => Unsigned_32'Asm_Output ("=g", Var_Out));
30257 where the compiler (since it does not analyze the @code{Asm} template string)
30258 does not know you are using the ebx register.
30260 In such cases you need to supply the @code{Clobber} parameter to @code{Asm},
30261 to identify the registers that will be used by your assembly code:
30265 Asm ("movl %0, %%ebx" & LF & HT &
30267 Inputs => Unsigned_32'Asm_Input ("g", Var_In),
30268 Outputs => Unsigned_32'Asm_Output ("=g", Var_Out),
30273 The Clobber parameter is a static string expression specifying the
30274 register(s) you are using. Note that register names are @emph{not} prefixed
30275 by a percent sign. Also, if more than one register is used then their names
30276 are separated by commas; e.g., @code{"eax, ebx"}
30278 The @code{Clobber} parameter has several additional uses:
30280 @item Use ``register'' name @code{cc} to indicate that flags might have changed
30281 @item Use ``register'' name @code{memory} if you changed a memory location
30284 @c ---------------------------------------------------------------------------
30285 @node The Volatile Parameter
30286 @subsection The @code{Volatile} Parameter
30287 @cindex Volatile parameter
30290 Compiler optimizations in the presence of Inline Assembler may sometimes have
30291 unwanted effects. For example, when an @code{Asm} invocation with an input
30292 variable is inside a loop, the compiler might move the loading of the input
30293 variable outside the loop, regarding it as a one-time initialization.
30295 If this effect is not desired, you can disable such optimizations by setting
30296 the @code{Volatile} parameter to @code{True}; for example:
30298 @smallexample @c ada
30300 Asm ("movl %0, %%ebx" & LF & HT &
30302 Inputs => Unsigned_32'Asm_Input ("g", Var_In),
30303 Outputs => Unsigned_32'Asm_Output ("=g", Var_Out),
30309 By default, @code{Volatile} is set to @code{False} unless there is no
30310 @code{Outputs} parameter.
30312 Although setting @code{Volatile} to @code{True} prevents unwanted
30313 optimizations, it will also disable other optimizations that might be
30314 important for efficiency. In general, you should set @code{Volatile}
30315 to @code{True} only if the compiler's optimizations have created
30317 @c END OF INLINE ASSEMBLER CHAPTER
30318 @c ===============================
30320 @c ***********************************
30321 @c * Compatibility and Porting Guide *
30322 @c ***********************************
30323 @node Compatibility and Porting Guide
30324 @appendix Compatibility and Porting Guide
30327 This chapter describes the compatibility issues that may arise between
30328 GNAT and other Ada compilation systems (including those for Ada 83),
30329 and shows how GNAT can expedite porting
30330 applications developed in other Ada environments.
30333 * Compatibility with Ada 83::
30334 * Compatibility between Ada 95 and Ada 2005::
30335 * Implementation-dependent characteristics::
30336 * Compatibility with Other Ada Systems::
30337 * Representation Clauses::
30339 @c Brief section is only in non-VMS version
30340 @c Full chapter is in VMS version
30341 * Compatibility with HP Ada 83::
30344 * Transitioning to 64-Bit GNAT for OpenVMS::
30348 @node Compatibility with Ada 83
30349 @section Compatibility with Ada 83
30350 @cindex Compatibility (between Ada 83 and Ada 95 / Ada 2005)
30353 Ada 95 and Ada 2005 are highly upwards compatible with Ada 83. In
30354 particular, the design intention was that the difficulties associated
30355 with moving from Ada 83 to Ada 95 or Ada 2005 should be no greater than those
30356 that occur when moving from one Ada 83 system to another.
30358 However, there are a number of points at which there are minor
30359 incompatibilities. The @cite{Ada 95 Annotated Reference Manual} contains
30360 full details of these issues,
30361 and should be consulted for a complete treatment.
30363 following subsections treat the most likely issues to be encountered.
30366 * Legal Ada 83 programs that are illegal in Ada 95::
30367 * More deterministic semantics::
30368 * Changed semantics::
30369 * Other language compatibility issues::
30372 @node Legal Ada 83 programs that are illegal in Ada 95
30373 @subsection Legal Ada 83 programs that are illegal in Ada 95
30375 Some legal Ada 83 programs are illegal (i.e., they will fail to compile) in
30376 Ada 95 and thus also in Ada 2005:
30379 @item Character literals
30380 Some uses of character literals are ambiguous. Since Ada 95 has introduced
30381 @code{Wide_Character} as a new predefined character type, some uses of
30382 character literals that were legal in Ada 83 are illegal in Ada 95.
30384 @smallexample @c ada
30385 for Char in 'A' .. 'Z' loop @dots{} end loop;
30389 The problem is that @code{'A'} and @code{'Z'} could be from either
30390 @code{Character} or @code{Wide_Character}. The simplest correction
30391 is to make the type explicit; e.g.:
30392 @smallexample @c ada
30393 for Char in Character range 'A' .. 'Z' loop @dots{} end loop;
30396 @item New reserved words
30397 The identifiers @code{abstract}, @code{aliased}, @code{protected},
30398 @code{requeue}, @code{tagged}, and @code{until} are reserved in Ada 95.
30399 Existing Ada 83 code using any of these identifiers must be edited to
30400 use some alternative name.
30402 @item Freezing rules
30403 The rules in Ada 95 are slightly different with regard to the point at
30404 which entities are frozen, and representation pragmas and clauses are
30405 not permitted past the freeze point. This shows up most typically in
30406 the form of an error message complaining that a representation item
30407 appears too late, and the appropriate corrective action is to move
30408 the item nearer to the declaration of the entity to which it refers.
30410 A particular case is that representation pragmas
30413 extended HP Ada 83 compatibility pragmas such as @code{Export_Procedure})
30415 cannot be applied to a subprogram body. If necessary, a separate subprogram
30416 declaration must be introduced to which the pragma can be applied.
30418 @item Optional bodies for library packages
30419 In Ada 83, a package that did not require a package body was nevertheless
30420 allowed to have one. This lead to certain surprises in compiling large
30421 systems (situations in which the body could be unexpectedly ignored by the
30422 binder). In Ada 95, if a package does not require a body then it is not
30423 permitted to have a body. To fix this problem, simply remove a redundant
30424 body if it is empty, or, if it is non-empty, introduce a dummy declaration
30425 into the spec that makes the body required. One approach is to add a private
30426 part to the package declaration (if necessary), and define a parameterless
30427 procedure called @code{Requires_Body}, which must then be given a dummy
30428 procedure body in the package body, which then becomes required.
30429 Another approach (assuming that this does not introduce elaboration
30430 circularities) is to add an @code{Elaborate_Body} pragma to the package spec,
30431 since one effect of this pragma is to require the presence of a package body.
30433 @item @code{Numeric_Error} is now the same as @code{Constraint_Error}
30434 In Ada 95, the exception @code{Numeric_Error} is a renaming of
30435 @code{Constraint_Error}.
30436 This means that it is illegal to have separate exception handlers for
30437 the two exceptions. The fix is simply to remove the handler for the
30438 @code{Numeric_Error} case (since even in Ada 83, a compiler was free to raise
30439 @code{Constraint_Error} in place of @code{Numeric_Error} in all cases).
30441 @item Indefinite subtypes in generics
30442 In Ada 83, it was permissible to pass an indefinite type (e.g.@: @code{String})
30443 as the actual for a generic formal private type, but then the instantiation
30444 would be illegal if there were any instances of declarations of variables
30445 of this type in the generic body. In Ada 95, to avoid this clear violation
30446 of the methodological principle known as the ``contract model'',
30447 the generic declaration explicitly indicates whether
30448 or not such instantiations are permitted. If a generic formal parameter
30449 has explicit unknown discriminants, indicated by using @code{(<>)} after the
30450 type name, then it can be instantiated with indefinite types, but no
30451 stand-alone variables can be declared of this type. Any attempt to declare
30452 such a variable will result in an illegality at the time the generic is
30453 declared. If the @code{(<>)} notation is not used, then it is illegal
30454 to instantiate the generic with an indefinite type.
30455 This is the potential incompatibility issue when porting Ada 83 code to Ada 95.
30456 It will show up as a compile time error, and
30457 the fix is usually simply to add the @code{(<>)} to the generic declaration.
30460 @node More deterministic semantics
30461 @subsection More deterministic semantics
30465 Conversions from real types to integer types round away from 0. In Ada 83
30466 the conversion Integer(2.5) could deliver either 2 or 3 as its value. This
30467 implementation freedom was intended to support unbiased rounding in
30468 statistical applications, but in practice it interfered with portability.
30469 In Ada 95 the conversion semantics are unambiguous, and rounding away from 0
30470 is required. Numeric code may be affected by this change in semantics.
30471 Note, though, that this issue is no worse than already existed in Ada 83
30472 when porting code from one vendor to another.
30475 The Real-Time Annex introduces a set of policies that define the behavior of
30476 features that were implementation dependent in Ada 83, such as the order in
30477 which open select branches are executed.
30480 @node Changed semantics
30481 @subsection Changed semantics
30484 The worst kind of incompatibility is one where a program that is legal in
30485 Ada 83 is also legal in Ada 95 but can have an effect in Ada 95 that was not
30486 possible in Ada 83. Fortunately this is extremely rare, but the one
30487 situation that you should be alert to is the change in the predefined type
30488 @code{Character} from 7-bit ASCII to 8-bit Latin-1.
30491 @item Range of type @code{Character}
30492 The range of @code{Standard.Character} is now the full 256 characters
30493 of Latin-1, whereas in most Ada 83 implementations it was restricted
30494 to 128 characters. Although some of the effects of
30495 this change will be manifest in compile-time rejection of legal
30496 Ada 83 programs it is possible for a working Ada 83 program to have
30497 a different effect in Ada 95, one that was not permitted in Ada 83.
30498 As an example, the expression
30499 @code{Character'Pos(Character'Last)} returned @code{127} in Ada 83 and now
30500 delivers @code{255} as its value.
30501 In general, you should look at the logic of any
30502 character-processing Ada 83 program and see whether it needs to be adapted
30503 to work correctly with Latin-1. Note that the predefined Ada 95 API has a
30504 character handling package that may be relevant if code needs to be adapted
30505 to account for the additional Latin-1 elements.
30506 The desirable fix is to
30507 modify the program to accommodate the full character set, but in some cases
30508 it may be convenient to define a subtype or derived type of Character that
30509 covers only the restricted range.
30513 @node Other language compatibility issues
30514 @subsection Other language compatibility issues
30517 @item @option{-gnat83} switch
30518 All implementations of GNAT provide a switch that causes GNAT to operate
30519 in Ada 83 mode. In this mode, some but not all compatibility problems
30520 of the type described above are handled automatically. For example, the
30521 new reserved words introduced in Ada 95 and Ada 2005 are treated simply
30522 as identifiers as in Ada 83.
30524 in practice, it is usually advisable to make the necessary modifications
30525 to the program to remove the need for using this switch.
30526 See @ref{Compiling Different Versions of Ada}.
30528 @item Support for removed Ada 83 pragmas and attributes
30529 A number of pragmas and attributes from Ada 83 were removed from Ada 95,
30530 generally because they were replaced by other mechanisms. Ada 95 and Ada 2005
30531 compilers are allowed, but not required, to implement these missing
30532 elements. In contrast with some other compilers, GNAT implements all
30533 such pragmas and attributes, eliminating this compatibility concern. These
30534 include @code{pragma Interface} and the floating point type attributes
30535 (@code{Emax}, @code{Mantissa}, etc.), among other items.
30539 @node Compatibility between Ada 95 and Ada 2005
30540 @section Compatibility between Ada 95 and Ada 2005
30541 @cindex Compatibility between Ada 95 and Ada 2005
30544 Although Ada 2005 was designed to be upwards compatible with Ada 95, there are
30545 a number of incompatibilities. Several are enumerated below;
30546 for a complete description please see the
30547 Annotated Ada 2005 Reference Manual, or section 9.1.1 in
30548 @cite{Rationale for Ada 2005}.
30551 @item New reserved words.
30552 The words @code{interface}, @code{overriding} and @code{synchronized} are
30553 reserved in Ada 2005.
30554 A pre-Ada 2005 program that uses any of these as an identifier will be
30557 @item New declarations in predefined packages.
30558 A number of packages in the predefined environment contain new declarations:
30559 @code{Ada.Exceptions}, @code{Ada.Real_Time}, @code{Ada.Strings},
30560 @code{Ada.Strings.Fixed}, @code{Ada.Strings.Bounded},
30561 @code{Ada.Strings.Unbounded}, @code{Ada.Strings.Wide_Fixed},
30562 @code{Ada.Strings.Wide_Bounded}, @code{Ada.Strings.Wide_Unbounded},
30563 @code{Ada.Tags}, @code{Ada.Text_IO}, and @code{Interfaces.C}.
30564 If an Ada 95 program does a @code{with} and @code{use} of any of these
30565 packages, the new declarations may cause name clashes.
30567 @item Access parameters.
30568 A nondispatching subprogram with an access parameter cannot be renamed
30569 as a dispatching operation. This was permitted in Ada 95.
30571 @item Access types, discriminants, and constraints.
30572 Rule changes in this area have led to some incompatibilities; for example,
30573 constrained subtypes of some access types are not permitted in Ada 2005.
30575 @item Aggregates for limited types.
30576 The allowance of aggregates for limited types in Ada 2005 raises the
30577 possibility of ambiguities in legal Ada 95 programs, since additional types
30578 now need to be considered in expression resolution.
30580 @item Fixed-point multiplication and division.
30581 Certain expressions involving ``*'' or ``/'' for a fixed-point type, which
30582 were legal in Ada 95 and invoked the predefined versions of these operations,
30584 The ambiguity may be resolved either by applying a type conversion to the
30585 expression, or by explicitly invoking the operation from package
30588 @item Return-by-reference types.
30589 The Ada 95 return-by-reference mechanism has been removed. Instead, the user
30590 can declare a function returning a value from an anonymous access type.
30594 @node Implementation-dependent characteristics
30595 @section Implementation-dependent characteristics
30597 Although the Ada language defines the semantics of each construct as
30598 precisely as practical, in some situations (for example for reasons of
30599 efficiency, or where the effect is heavily dependent on the host or target
30600 platform) the implementation is allowed some freedom. In porting Ada 83
30601 code to GNAT, you need to be aware of whether / how the existing code
30602 exercised such implementation dependencies. Such characteristics fall into
30603 several categories, and GNAT offers specific support in assisting the
30604 transition from certain Ada 83 compilers.
30607 * Implementation-defined pragmas::
30608 * Implementation-defined attributes::
30610 * Elaboration order::
30611 * Target-specific aspects::
30614 @node Implementation-defined pragmas
30615 @subsection Implementation-defined pragmas
30618 Ada compilers are allowed to supplement the language-defined pragmas, and
30619 these are a potential source of non-portability. All GNAT-defined pragmas
30620 are described in @ref{Implementation Defined Pragmas,,, gnat_rm, GNAT
30621 Reference Manual}, and these include several that are specifically
30622 intended to correspond to other vendors' Ada 83 pragmas.
30623 For migrating from VADS, the pragma @code{Use_VADS_Size} may be useful.
30624 For compatibility with HP Ada 83, GNAT supplies the pragmas
30625 @code{Extend_System}, @code{Ident}, @code{Inline_Generic},
30626 @code{Interface_Name}, @code{Passive}, @code{Suppress_All},
30627 and @code{Volatile}.
30628 Other relevant pragmas include @code{External} and @code{Link_With}.
30629 Some vendor-specific
30630 Ada 83 pragmas (@code{Share_Generic}, @code{Subtitle}, and @code{Title}) are
30632 avoiding compiler rejection of units that contain such pragmas; they are not
30633 relevant in a GNAT context and hence are not otherwise implemented.
30635 @node Implementation-defined attributes
30636 @subsection Implementation-defined attributes
30638 Analogous to pragmas, the set of attributes may be extended by an
30639 implementation. All GNAT-defined attributes are described in
30640 @ref{Implementation Defined Attributes,,, gnat_rm, GNAT Reference
30641 Manual}, and these include several that are specifically intended
30642 to correspond to other vendors' Ada 83 attributes. For migrating from VADS,
30643 the attribute @code{VADS_Size} may be useful. For compatibility with HP
30644 Ada 83, GNAT supplies the attributes @code{Bit}, @code{Machine_Size} and
30648 @subsection Libraries
30650 Vendors may supply libraries to supplement the standard Ada API. If Ada 83
30651 code uses vendor-specific libraries then there are several ways to manage
30652 this in Ada 95 or Ada 2005:
30655 If the source code for the libraries (specs and bodies) are
30656 available, then the libraries can be migrated in the same way as the
30659 If the source code for the specs but not the bodies are
30660 available, then you can reimplement the bodies.
30662 Some features introduced by Ada 95 obviate the need for library support. For
30663 example most Ada 83 vendors supplied a package for unsigned integers. The
30664 Ada 95 modular type feature is the preferred way to handle this need, so
30665 instead of migrating or reimplementing the unsigned integer package it may
30666 be preferable to retrofit the application using modular types.
30669 @node Elaboration order
30670 @subsection Elaboration order
30672 The implementation can choose any elaboration order consistent with the unit
30673 dependency relationship. This freedom means that some orders can result in
30674 Program_Error being raised due to an ``Access Before Elaboration'': an attempt
30675 to invoke a subprogram its body has been elaborated, or to instantiate a
30676 generic before the generic body has been elaborated. By default GNAT
30677 attempts to choose a safe order (one that will not encounter access before
30678 elaboration problems) by implicitly inserting @code{Elaborate} or
30679 @code{Elaborate_All} pragmas where
30680 needed. However, this can lead to the creation of elaboration circularities
30681 and a resulting rejection of the program by gnatbind. This issue is
30682 thoroughly described in @ref{Elaboration Order Handling in GNAT}.
30683 In brief, there are several
30684 ways to deal with this situation:
30688 Modify the program to eliminate the circularities, e.g.@: by moving
30689 elaboration-time code into explicitly-invoked procedures
30691 Constrain the elaboration order by including explicit @code{Elaborate_Body} or
30692 @code{Elaborate} pragmas, and then inhibit the generation of implicit
30693 @code{Elaborate_All}
30694 pragmas either globally (as an effect of the @option{-gnatE} switch) or locally
30695 (by selectively suppressing elaboration checks via pragma
30696 @code{Suppress(Elaboration_Check)} when it is safe to do so).
30699 @node Target-specific aspects
30700 @subsection Target-specific aspects
30702 Low-level applications need to deal with machine addresses, data
30703 representations, interfacing with assembler code, and similar issues. If
30704 such an Ada 83 application is being ported to different target hardware (for
30705 example where the byte endianness has changed) then you will need to
30706 carefully examine the program logic; the porting effort will heavily depend
30707 on the robustness of the original design. Moreover, Ada 95 (and thus
30708 Ada 2005) are sometimes
30709 incompatible with typical Ada 83 compiler practices regarding implicit
30710 packing, the meaning of the Size attribute, and the size of access values.
30711 GNAT's approach to these issues is described in @ref{Representation Clauses}.
30713 @node Compatibility with Other Ada Systems
30714 @section Compatibility with Other Ada Systems
30717 If programs avoid the use of implementation dependent and
30718 implementation defined features, as documented in the @cite{Ada
30719 Reference Manual}, there should be a high degree of portability between
30720 GNAT and other Ada systems. The following are specific items which
30721 have proved troublesome in moving Ada 95 programs from GNAT to other Ada 95
30722 compilers, but do not affect porting code to GNAT@.
30723 (As of @value{NOW}, GNAT is the only compiler available for Ada 2005;
30724 the following issues may or may not arise for Ada 2005 programs
30725 when other compilers appear.)
30728 @item Ada 83 Pragmas and Attributes
30729 Ada 95 compilers are allowed, but not required, to implement the missing
30730 Ada 83 pragmas and attributes that are no longer defined in Ada 95.
30731 GNAT implements all such pragmas and attributes, eliminating this as
30732 a compatibility concern, but some other Ada 95 compilers reject these
30733 pragmas and attributes.
30735 @item Specialized Needs Annexes
30736 GNAT implements the full set of special needs annexes. At the
30737 current time, it is the only Ada 95 compiler to do so. This means that
30738 programs making use of these features may not be portable to other Ada
30739 95 compilation systems.
30741 @item Representation Clauses
30742 Some other Ada 95 compilers implement only the minimal set of
30743 representation clauses required by the Ada 95 reference manual. GNAT goes
30744 far beyond this minimal set, as described in the next section.
30747 @node Representation Clauses
30748 @section Representation Clauses
30751 The Ada 83 reference manual was quite vague in describing both the minimal
30752 required implementation of representation clauses, and also their precise
30753 effects. Ada 95 (and thus also Ada 2005) are much more explicit, but the
30754 minimal set of capabilities required is still quite limited.
30756 GNAT implements the full required set of capabilities in
30757 Ada 95 and Ada 2005, but also goes much further, and in particular
30758 an effort has been made to be compatible with existing Ada 83 usage to the
30759 greatest extent possible.
30761 A few cases exist in which Ada 83 compiler behavior is incompatible with
30762 the requirements in Ada 95 (and thus also Ada 2005). These are instances of
30763 intentional or accidental dependence on specific implementation dependent
30764 characteristics of these Ada 83 compilers. The following is a list of
30765 the cases most likely to arise in existing Ada 83 code.
30768 @item Implicit Packing
30769 Some Ada 83 compilers allowed a Size specification to cause implicit
30770 packing of an array or record. This could cause expensive implicit
30771 conversions for change of representation in the presence of derived
30772 types, and the Ada design intends to avoid this possibility.
30773 Subsequent AI's were issued to make it clear that such implicit
30774 change of representation in response to a Size clause is inadvisable,
30775 and this recommendation is represented explicitly in the Ada 95 (and Ada 2005)
30776 Reference Manuals as implementation advice that is followed by GNAT@.
30777 The problem will show up as an error
30778 message rejecting the size clause. The fix is simply to provide
30779 the explicit pragma @code{Pack}, or for more fine tuned control, provide
30780 a Component_Size clause.
30782 @item Meaning of Size Attribute
30783 The Size attribute in Ada 95 (and Ada 2005) for discrete types is defined as
30784 the minimal number of bits required to hold values of the type. For example,
30785 on a 32-bit machine, the size of @code{Natural} will typically be 31 and not
30786 32 (since no sign bit is required). Some Ada 83 compilers gave 31, and
30787 some 32 in this situation. This problem will usually show up as a compile
30788 time error, but not always. It is a good idea to check all uses of the
30789 'Size attribute when porting Ada 83 code. The GNAT specific attribute
30790 Object_Size can provide a useful way of duplicating the behavior of
30791 some Ada 83 compiler systems.
30793 @item Size of Access Types
30794 A common assumption in Ada 83 code is that an access type is in fact a pointer,
30795 and that therefore it will be the same size as a System.Address value. This
30796 assumption is true for GNAT in most cases with one exception. For the case of
30797 a pointer to an unconstrained array type (where the bounds may vary from one
30798 value of the access type to another), the default is to use a ``fat pointer'',
30799 which is represented as two separate pointers, one to the bounds, and one to
30800 the array. This representation has a number of advantages, including improved
30801 efficiency. However, it may cause some difficulties in porting existing Ada 83
30802 code which makes the assumption that, for example, pointers fit in 32 bits on
30803 a machine with 32-bit addressing.
30805 To get around this problem, GNAT also permits the use of ``thin pointers'' for
30806 access types in this case (where the designated type is an unconstrained array
30807 type). These thin pointers are indeed the same size as a System.Address value.
30808 To specify a thin pointer, use a size clause for the type, for example:
30810 @smallexample @c ada
30811 type X is access all String;
30812 for X'Size use Standard'Address_Size;
30816 which will cause the type X to be represented using a single pointer.
30817 When using this representation, the bounds are right behind the array.
30818 This representation is slightly less efficient, and does not allow quite
30819 such flexibility in the use of foreign pointers or in using the
30820 Unrestricted_Access attribute to create pointers to non-aliased objects.
30821 But for any standard portable use of the access type it will work in
30822 a functionally correct manner and allow porting of existing code.
30823 Note that another way of forcing a thin pointer representation
30824 is to use a component size clause for the element size in an array,
30825 or a record representation clause for an access field in a record.
30829 @c This brief section is only in the non-VMS version
30830 @c The complete chapter on HP Ada is in the VMS version
30831 @node Compatibility with HP Ada 83
30832 @section Compatibility with HP Ada 83
30835 The VMS version of GNAT fully implements all the pragmas and attributes
30836 provided by HP Ada 83, as well as providing the standard HP Ada 83
30837 libraries, including Starlet. In addition, data layouts and parameter
30838 passing conventions are highly compatible. This means that porting
30839 existing HP Ada 83 code to GNAT in VMS systems should be easier than
30840 most other porting efforts. The following are some of the most
30841 significant differences between GNAT and HP Ada 83.
30844 @item Default floating-point representation
30845 In GNAT, the default floating-point format is IEEE, whereas in HP Ada 83,
30846 it is VMS format. GNAT does implement the necessary pragmas
30847 (Long_Float, Float_Representation) for changing this default.
30850 The package System in GNAT exactly corresponds to the definition in the
30851 Ada 95 reference manual, which means that it excludes many of the
30852 HP Ada 83 extensions. However, a separate package Aux_DEC is provided
30853 that contains the additional definitions, and a special pragma,
30854 Extend_System allows this package to be treated transparently as an
30855 extension of package System.
30858 The definitions provided by Aux_DEC are exactly compatible with those
30859 in the HP Ada 83 version of System, with one exception.
30860 HP Ada provides the following declarations:
30862 @smallexample @c ada
30863 TO_ADDRESS (INTEGER)
30864 TO_ADDRESS (UNSIGNED_LONGWORD)
30865 TO_ADDRESS (@i{universal_integer})
30869 The version of TO_ADDRESS taking a @i{universal integer} argument is in fact
30870 an extension to Ada 83 not strictly compatible with the reference manual.
30871 In GNAT, we are constrained to be exactly compatible with the standard,
30872 and this means we cannot provide this capability. In HP Ada 83, the
30873 point of this definition is to deal with a call like:
30875 @smallexample @c ada
30876 TO_ADDRESS (16#12777#);
30880 Normally, according to the Ada 83 standard, one would expect this to be
30881 ambiguous, since it matches both the INTEGER and UNSIGNED_LONGWORD forms
30882 of TO_ADDRESS@. However, in HP Ada 83, there is no ambiguity, since the
30883 definition using @i{universal_integer} takes precedence.
30885 In GNAT, since the version with @i{universal_integer} cannot be supplied, it
30886 is not possible to be 100% compatible. Since there are many programs using
30887 numeric constants for the argument to TO_ADDRESS, the decision in GNAT was
30888 to change the name of the function in the UNSIGNED_LONGWORD case, so the
30889 declarations provided in the GNAT version of AUX_Dec are:
30891 @smallexample @c ada
30892 function To_Address (X : Integer) return Address;
30893 pragma Pure_Function (To_Address);
30895 function To_Address_Long (X : Unsigned_Longword)
30897 pragma Pure_Function (To_Address_Long);
30901 This means that programs using TO_ADDRESS for UNSIGNED_LONGWORD must
30902 change the name to TO_ADDRESS_LONG@.
30904 @item Task_Id values
30905 The Task_Id values assigned will be different in the two systems, and GNAT
30906 does not provide a specified value for the Task_Id of the environment task,
30907 which in GNAT is treated like any other declared task.
30911 For full details on these and other less significant compatibility issues,
30912 see appendix E of the HP publication entitled @cite{HP Ada, Technical
30913 Overview and Comparison on HP Platforms}.
30915 For GNAT running on other than VMS systems, all the HP Ada 83 pragmas and
30916 attributes are recognized, although only a subset of them can sensibly
30917 be implemented. The description of pragmas in @ref{Implementation
30918 Defined Pragmas,,, gnat_rm, GNAT Reference Manual}
30919 indicates whether or not they are applicable to non-VMS systems.
30923 @node Transitioning to 64-Bit GNAT for OpenVMS
30924 @section Transitioning to 64-Bit @value{EDITION} for OpenVMS
30927 This section is meant to assist users of pre-2006 @value{EDITION}
30928 for Alpha OpenVMS who are transitioning to 64-bit @value{EDITION},
30929 the version of the GNAT technology supplied in 2006 and later for
30930 OpenVMS on both Alpha and I64.
30933 * Introduction to transitioning::
30934 * Migration of 32 bit code::
30935 * Taking advantage of 64 bit addressing::
30936 * Technical details::
30939 @node Introduction to transitioning
30940 @subsection Introduction
30943 64-bit @value{EDITION} for Open VMS has been designed to meet
30948 Providing a full conforming implementation of Ada 95 and Ada 2005
30951 Allowing maximum backward compatibility, thus easing migration of existing
30955 Supplying a path for exploiting the full 64-bit address range
30959 Ada's strong typing semantics has made it
30960 impractical to have different 32-bit and 64-bit modes. As soon as
30961 one object could possibly be outside the 32-bit address space, this
30962 would make it necessary for the @code{System.Address} type to be 64 bits.
30963 In particular, this would cause inconsistencies if 32-bit code is
30964 called from 64-bit code that raises an exception.
30966 This issue has been resolved by always using 64-bit addressing
30967 at the system level, but allowing for automatic conversions between
30968 32-bit and 64-bit addresses where required. Thus users who
30969 do not currently require 64-bit addressing capabilities, can
30970 recompile their code with only minimal changes (and indeed
30971 if the code is written in portable Ada, with no assumptions about
30972 the size of the @code{Address} type, then no changes at all are necessary).
30974 this approach provides a simple, gradual upgrade path to future
30975 use of larger memories than available for 32-bit systems.
30976 Also, newly written applications or libraries will by default
30977 be fully compatible with future systems exploiting 64-bit
30978 addressing capabilities.
30980 @ref{Migration of 32 bit code}, will focus on porting applications
30981 that do not require more than 2 GB of
30982 addressable memory. This code will be referred to as
30983 @emph{32-bit code}.
30984 For applications intending to exploit the full 64-bit address space,
30985 @ref{Taking advantage of 64 bit addressing},
30986 will consider further changes that may be required.
30987 Such code will be referred to below as @emph{64-bit code}.
30989 @node Migration of 32 bit code
30990 @subsection Migration of 32-bit code
30995 * Unchecked conversions::
30996 * Predefined constants::
30997 * Interfacing with C::
30998 * Experience with source compatibility::
31001 @node Address types
31002 @subsubsection Address types
31005 To solve the problem of mixing 64-bit and 32-bit addressing,
31006 while maintaining maximum backward compatibility, the following
31007 approach has been taken:
31011 @code{System.Address} always has a size of 64 bits
31014 @code{System.Short_Address} is a 32-bit subtype of @code{System.Address}
31018 Since @code{System.Short_Address} is a subtype of @code{System.Address},
31019 a @code{Short_Address}
31020 may be used where an @code{Address} is required, and vice versa, without
31021 needing explicit type conversions.
31022 By virtue of the Open VMS parameter passing conventions,
31024 and exported subprograms that have 32-bit address parameters are
31025 compatible with those that have 64-bit address parameters.
31026 (See @ref{Making code 64 bit clean} for details.)
31028 The areas that may need attention are those where record types have
31029 been defined that contain components of the type @code{System.Address}, and
31030 where objects of this type are passed to code expecting a record layout with
31033 Different compilers on different platforms cannot be
31034 expected to represent the same type in the same way,
31035 since alignment constraints
31036 and other system-dependent properties affect the compiler's decision.
31037 For that reason, Ada code
31038 generally uses representation clauses to specify the expected
31039 layout where required.
31041 If such a representation clause uses 32 bits for a component having
31042 the type @code{System.Address}, 64-bit @value{EDITION} for OpenVMS
31043 will detect that error and produce a specific diagnostic message.
31044 The developer should then determine whether the representation
31045 should be 64 bits or not and make either of two changes:
31046 change the size to 64 bits and leave the type as @code{System.Address}, or
31047 leave the size as 32 bits and change the type to @code{System.Short_Address}.
31048 Since @code{Short_Address} is a subtype of @code{Address}, no changes are
31049 required in any code setting or accessing the field; the compiler will
31050 automatically perform any needed conversions between address
31054 @subsubsection Access types
31057 By default, objects designated by access values are always
31058 allocated in the 32-bit
31059 address space. Thus legacy code will never contain
31060 any objects that are not addressable with 32-bit addresses, and
31061 the compiler will never raise exceptions as result of mixing
31062 32-bit and 64-bit addresses.
31064 However, the access values themselves are represented in 64 bits, for optimum
31065 performance and future compatibility with 64-bit code. As was
31066 the case with @code{System.Address}, the compiler will give an error message
31067 if an object or record component has a representation clause that
31068 requires the access value to fit in 32 bits. In such a situation,
31069 an explicit size clause for the access type, specifying 32 bits,
31070 will have the desired effect.
31072 General access types (declared with @code{access all}) can never be
31073 32 bits, as values of such types must be able to refer to any object
31074 of the designated type,
31075 including objects residing outside the 32-bit address range.
31076 Existing Ada 83 code will not contain such type definitions,
31077 however, since general access types were introduced in Ada 95.
31079 @node Unchecked conversions
31080 @subsubsection Unchecked conversions
31083 In the case of an @code{Unchecked_Conversion} where the source type is a
31084 64-bit access type or the type @code{System.Address}, and the target
31085 type is a 32-bit type, the compiler will generate a warning.
31086 Even though the generated code will still perform the required
31087 conversions, it is highly recommended in these cases to use
31088 respectively a 32-bit access type or @code{System.Short_Address}
31089 as the source type.
31091 @node Predefined constants
31092 @subsubsection Predefined constants
31095 The following table shows the correspondence between pre-2006 versions of
31096 @value{EDITION} on Alpha OpenVMS (``Old'') and 64-bit @value{EDITION}
31099 @multitable {@code{System.Short_Memory_Size}} {2**32} {2**64}
31100 @item @b{Constant} @tab @b{Old} @tab @b{New}
31101 @item @code{System.Word_Size} @tab 32 @tab 64
31102 @item @code{System.Memory_Size} @tab 2**32 @tab 2**64
31103 @item @code{System.Short_Memory_Size} @tab 2**32 @tab 2**32
31104 @item @code{System.Address_Size} @tab 32 @tab 64
31108 If you need to refer to the specific
31109 memory size of a 32-bit implementation, instead of the
31110 actual memory size, use @code{System.Short_Memory_Size}
31111 rather than @code{System.Memory_Size}.
31112 Similarly, references to @code{System.Address_Size} may need
31113 to be replaced by @code{System.Short_Address'Size}.
31114 The program @command{gnatfind} may be useful for locating
31115 references to the above constants, so that you can verify that they
31118 @node Interfacing with C
31119 @subsubsection Interfacing with C
31122 In order to minimize the impact of the transition to 64-bit addresses on
31123 legacy programs, some fundamental types in the @code{Interfaces.C}
31124 package hierarchy continue to be represented in 32 bits.
31125 These types are: @code{ptrdiff_t}, @code{size_t}, and @code{chars_ptr}.
31126 This eases integration with the default HP C layout choices, for example
31127 as found in the system routines in @code{DECC$SHR.EXE}.
31128 Because of this implementation choice, the type fully compatible with
31129 @code{chars_ptr} is now @code{Short_Address} and not @code{Address}.
31130 Depending on the context the compiler will issue a
31131 warning or an error when type @code{Address} is used, alerting the user to a
31132 potential problem. Otherwise 32-bit programs that use
31133 @code{Interfaces.C} should normally not require code modifications
31135 The other issue arising with C interfacing concerns pragma @code{Convention}.
31136 For VMS 64-bit systems, there is an issue of the appropriate default size
31137 of C convention pointers in the absence of an explicit size clause. The HP
31138 C compiler can choose either 32 or 64 bits depending on compiler options.
31139 GNAT chooses 32-bits rather than 64-bits in the default case where no size
31140 clause is given. This proves a better choice for porting 32-bit legacy
31141 applications. In order to have a 64-bit representation, it is necessary to
31142 specify a size representation clause. For example:
31144 @smallexample @c ada
31145 type int_star is access Interfaces.C.int;
31146 pragma Convention(C, int_star);
31147 for int_star'Size use 64; -- Necessary to get 64 and not 32 bits
31150 @node Experience with source compatibility
31151 @subsubsection Experience with source compatibility
31154 The Security Server and STARLET on I64 provide an interesting ``test case''
31155 for source compatibility issues, since it is in such system code
31156 where assumptions about @code{Address} size might be expected to occur.
31157 Indeed, there were a small number of occasions in the Security Server
31158 file @file{jibdef.ads}
31159 where a representation clause for a record type specified
31160 32 bits for a component of type @code{Address}.
31161 All of these errors were detected by the compiler.
31162 The repair was obvious and immediate; to simply replace @code{Address} by
31163 @code{Short_Address}.
31165 In the case of STARLET, there were several record types that should
31166 have had representation clauses but did not. In these record types
31167 there was an implicit assumption that an @code{Address} value occupied
31169 These compiled without error, but their usage resulted in run-time error
31170 returns from STARLET system calls.
31171 Future GNAT technology enhancements may include a tool that detects and flags
31172 these sorts of potential source code porting problems.
31174 @c ****************************************
31175 @node Taking advantage of 64 bit addressing
31176 @subsection Taking advantage of 64-bit addressing
31179 * Making code 64 bit clean::
31180 * Allocating memory from the 64 bit storage pool::
31181 * Restrictions on use of 64 bit objects::
31182 * Using 64 bit storage pools by default::
31183 * General access types::
31184 * STARLET and other predefined libraries::
31187 @node Making code 64 bit clean
31188 @subsubsection Making code 64-bit clean
31191 In order to prevent problems that may occur when (parts of) a
31192 system start using memory outside the 32-bit address range,
31193 we recommend some additional guidelines:
31197 For imported subprograms that take parameters of the
31198 type @code{System.Address}, ensure that these subprograms can
31199 indeed handle 64-bit addresses. If not, or when in doubt,
31200 change the subprogram declaration to specify
31201 @code{System.Short_Address} instead.
31204 Resolve all warnings related to size mismatches in
31205 unchecked conversions. Failing to do so causes
31206 erroneous execution if the source object is outside
31207 the 32-bit address space.
31210 (optional) Explicitly use the 32-bit storage pool
31211 for access types used in a 32-bit context, or use
31212 generic access types where possible
31213 (@pxref{Restrictions on use of 64 bit objects}).
31217 If these rules are followed, the compiler will automatically insert
31218 any necessary checks to ensure that no addresses or access values
31219 passed to 32-bit code ever refer to objects outside the 32-bit
31221 Any attempt to do this will raise @code{Constraint_Error}.
31223 @node Allocating memory from the 64 bit storage pool
31224 @subsubsection Allocating memory from the 64-bit storage pool
31227 For any access type @code{T} that potentially requires memory allocations
31228 beyond the 32-bit address space,
31229 use the following representation clause:
31231 @smallexample @c ada
31232 for T'Storage_Pool use System.Pool_64;
31235 @node Restrictions on use of 64 bit objects
31236 @subsubsection Restrictions on use of 64-bit objects
31239 Taking the address of an object allocated from a 64-bit storage pool,
31240 and then passing this address to a subprogram expecting
31241 @code{System.Short_Address},
31242 or assigning it to a variable of type @code{Short_Address}, will cause
31243 @code{Constraint_Error} to be raised. In case the code is not 64-bit clean
31244 (@pxref{Making code 64 bit clean}), or checks are suppressed,
31245 no exception is raised and execution
31246 will become erroneous.
31248 @node Using 64 bit storage pools by default
31249 @subsubsection Using 64-bit storage pools by default
31252 In some cases it may be desirable to have the compiler allocate
31253 from 64-bit storage pools by default. This may be the case for
31254 libraries that are 64-bit clean, but may be used in both 32-bit
31255 and 64-bit contexts. For these cases the following configuration
31256 pragma may be specified:
31258 @smallexample @c ada
31259 pragma Pool_64_Default;
31263 Any code compiled in the context of this pragma will by default
31264 use the @code{System.Pool_64} storage pool. This default may be overridden
31265 for a specific access type @code{T} by the representation clause:
31267 @smallexample @c ada
31268 for T'Storage_Pool use System.Pool_32;
31272 Any object whose address may be passed to a subprogram with a
31273 @code{Short_Address} argument, or assigned to a variable of type
31274 @code{Short_Address}, needs to be allocated from this pool.
31276 @node General access types
31277 @subsubsection General access types
31280 Objects designated by access values from a
31281 general access type (declared with @code{access all}) are never allocated
31282 from a 64-bit storage pool. Code that uses general access types will
31283 accept objects allocated in either 32-bit or 64-bit address spaces,
31284 but never allocate objects outside the 32-bit address space.
31285 Using general access types ensures maximum compatibility with both
31286 32-bit and 64-bit code.
31288 @node STARLET and other predefined libraries
31289 @subsubsection STARLET and other predefined libraries
31292 All code that comes as part of GNAT is 64-bit clean, but the
31293 restrictions given in @ref{Restrictions on use of 64 bit objects},
31294 still apply. Look at the package
31295 specs to see in which contexts objects allocated
31296 in 64-bit address space are acceptable.
31298 @node Technical details
31299 @subsection Technical details
31302 64-bit @value{EDITION} for Open VMS takes advantage of the freedom given in the
31303 Ada standard with respect to the type of @code{System.Address}. Previous
31304 versions of GNAT Pro have defined this type as private and implemented it as a
31307 In order to allow defining @code{System.Short_Address} as a proper subtype,
31308 and to match the implicit sign extension in parameter passing,
31309 in 64-bit @value{EDITION} for Open VMS, @code{System.Address} is defined as a
31310 visible (i.e., non-private) integer type.
31311 Standard operations on the type, such as the binary operators ``+'', ``-'',
31312 etc., that take @code{Address} operands and return an @code{Address} result,
31313 have been hidden by declaring these
31314 @code{abstract}, a feature introduced in Ada 95 that helps avoid the potential
31315 ambiguities that would otherwise result from overloading.
31316 (Note that, although @code{Address} is a visible integer type,
31317 good programming practice dictates against exploiting the type's
31318 integer properties such as literals, since this will compromise
31321 Defining @code{Address} as a visible integer type helps achieve
31322 maximum compatibility for existing Ada code,
31323 without sacrificing the capabilities of the 64-bit architecture.
31326 @c ************************************************
31328 @node Microsoft Windows Topics
31329 @appendix Microsoft Windows Topics
31335 This chapter describes topics that are specific to the Microsoft Windows
31336 platforms (NT, 2000, and XP Professional).
31339 * Using GNAT on Windows::
31340 * Using a network installation of GNAT::
31341 * CONSOLE and WINDOWS subsystems::
31342 * Temporary Files::
31343 * Mixed-Language Programming on Windows::
31344 * Windows Calling Conventions::
31345 * Introduction to Dynamic Link Libraries (DLLs)::
31346 * Using DLLs with GNAT::
31347 * Building DLLs with GNAT::
31348 * Building DLLs with GNAT Project files::
31349 * Building DLLs with gnatdll::
31350 * GNAT and Windows Resources::
31351 * Debugging a DLL::
31352 * Setting Stack Size from gnatlink::
31353 * Setting Heap Size from gnatlink::
31356 @node Using GNAT on Windows
31357 @section Using GNAT on Windows
31360 One of the strengths of the GNAT technology is that its tool set
31361 (@command{gcc}, @command{gnatbind}, @command{gnatlink}, @command{gnatmake}, the
31362 @code{gdb} debugger, etc.) is used in the same way regardless of the
31365 On Windows this tool set is complemented by a number of Microsoft-specific
31366 tools that have been provided to facilitate interoperability with Windows
31367 when this is required. With these tools:
31372 You can build applications using the @code{CONSOLE} or @code{WINDOWS}
31376 You can use any Dynamically Linked Library (DLL) in your Ada code (both
31377 relocatable and non-relocatable DLLs are supported).
31380 You can build Ada DLLs for use in other applications. These applications
31381 can be written in a language other than Ada (e.g., C, C++, etc). Again both
31382 relocatable and non-relocatable Ada DLLs are supported.
31385 You can include Windows resources in your Ada application.
31388 You can use or create COM/DCOM objects.
31392 Immediately below are listed all known general GNAT-for-Windows restrictions.
31393 Other restrictions about specific features like Windows Resources and DLLs
31394 are listed in separate sections below.
31399 It is not possible to use @code{GetLastError} and @code{SetLastError}
31400 when tasking, protected records, or exceptions are used. In these
31401 cases, in order to implement Ada semantics, the GNAT run-time system
31402 calls certain Win32 routines that set the last error variable to 0 upon
31403 success. It should be possible to use @code{GetLastError} and
31404 @code{SetLastError} when tasking, protected record, and exception
31405 features are not used, but it is not guaranteed to work.
31408 It is not possible to link against Microsoft libraries except for
31409 import libraries. The library must be built to be compatible with
31410 @file{MSVCRT.LIB} (/MD Microsoft compiler option), @file{LIBC.LIB} and
31411 @file{LIBCMT.LIB} (/ML or /MT Microsoft compiler options) are known to
31412 not be compatible with the GNAT runtime. Even if the library is
31413 compatible with @file{MSVCRT.LIB} it is not guaranteed to work.
31416 When the compilation environment is located on FAT32 drives, users may
31417 experience recompilations of the source files that have not changed if
31418 Daylight Saving Time (DST) state has changed since the last time files
31419 were compiled. NTFS drives do not have this problem.
31422 No components of the GNAT toolset use any entries in the Windows
31423 registry. The only entries that can be created are file associations and
31424 PATH settings, provided the user has chosen to create them at installation
31425 time, as well as some minimal book-keeping information needed to correctly
31426 uninstall or integrate different GNAT products.
31429 @node Using a network installation of GNAT
31430 @section Using a network installation of GNAT
31433 Make sure the system on which GNAT is installed is accessible from the
31434 current machine, i.e., the install location is shared over the network.
31435 Shared resources are accessed on Windows by means of UNC paths, which
31436 have the format @code{\\server\sharename\path}
31438 In order to use such a network installation, simply add the UNC path of the
31439 @file{bin} directory of your GNAT installation in front of your PATH. For
31440 example, if GNAT is installed in @file{\GNAT} directory of a share location
31441 called @file{c-drive} on a machine @file{LOKI}, the following command will
31444 @code{@ @ @ path \\loki\c-drive\gnat\bin;%path%}
31446 Be aware that every compilation using the network installation results in the
31447 transfer of large amounts of data across the network and will likely cause
31448 serious performance penalty.
31450 @node CONSOLE and WINDOWS subsystems
31451 @section CONSOLE and WINDOWS subsystems
31452 @cindex CONSOLE Subsystem
31453 @cindex WINDOWS Subsystem
31457 There are two main subsystems under Windows. The @code{CONSOLE} subsystem
31458 (which is the default subsystem) will always create a console when
31459 launching the application. This is not something desirable when the
31460 application has a Windows GUI. To get rid of this console the
31461 application must be using the @code{WINDOWS} subsystem. To do so
31462 the @option{-mwindows} linker option must be specified.
31465 $ gnatmake winprog -largs -mwindows
31468 @node Temporary Files
31469 @section Temporary Files
31470 @cindex Temporary files
31473 It is possible to control where temporary files gets created by setting
31474 the @env{TMP} environment variable. The file will be created:
31477 @item Under the directory pointed to by the @env{TMP} environment variable if
31478 this directory exists.
31480 @item Under @file{c:\temp}, if the @env{TMP} environment variable is not
31481 set (or not pointing to a directory) and if this directory exists.
31483 @item Under the current working directory otherwise.
31487 This allows you to determine exactly where the temporary
31488 file will be created. This is particularly useful in networked
31489 environments where you may not have write access to some
31492 @node Mixed-Language Programming on Windows
31493 @section Mixed-Language Programming on Windows
31496 Developing pure Ada applications on Windows is no different than on
31497 other GNAT-supported platforms. However, when developing or porting an
31498 application that contains a mix of Ada and C/C++, the choice of your
31499 Windows C/C++ development environment conditions your overall
31500 interoperability strategy.
31502 If you use @command{gcc} to compile the non-Ada part of your application,
31503 there are no Windows-specific restrictions that affect the overall
31504 interoperability with your Ada code. If you plan to use
31505 Microsoft tools (e.g.@: Microsoft Visual C/C++), you should be aware of
31506 the following limitations:
31510 You cannot link your Ada code with an object or library generated with
31511 Microsoft tools if these use the @code{.tls} section (Thread Local
31512 Storage section) since the GNAT linker does not yet support this section.
31515 You cannot link your Ada code with an object or library generated with
31516 Microsoft tools if these use I/O routines other than those provided in
31517 the Microsoft DLL: @code{msvcrt.dll}. This is because the GNAT run time
31518 uses the services of @code{msvcrt.dll} for its I/Os. Use of other I/O
31519 libraries can cause a conflict with @code{msvcrt.dll} services. For
31520 instance Visual C++ I/O stream routines conflict with those in
31525 If you do want to use the Microsoft tools for your non-Ada code and hit one
31526 of the above limitations, you have two choices:
31530 Encapsulate your non-Ada code in a DLL to be linked with your Ada
31531 application. In this case, use the Microsoft or whatever environment to
31532 build the DLL and use GNAT to build your executable
31533 (@pxref{Using DLLs with GNAT}).
31536 Or you can encapsulate your Ada code in a DLL to be linked with the
31537 other part of your application. In this case, use GNAT to build the DLL
31538 (@pxref{Building DLLs with GNAT}) and use the Microsoft or whatever
31539 environment to build your executable.
31542 @node Windows Calling Conventions
31543 @section Windows Calling Conventions
31548 * C Calling Convention::
31549 * Stdcall Calling Convention::
31550 * Win32 Calling Convention::
31551 * DLL Calling Convention::
31555 When a subprogram @code{F} (caller) calls a subprogram @code{G}
31556 (callee), there are several ways to push @code{G}'s parameters on the
31557 stack and there are several possible scenarios to clean up the stack
31558 upon @code{G}'s return. A calling convention is an agreed upon software
31559 protocol whereby the responsibilities between the caller (@code{F}) and
31560 the callee (@code{G}) are clearly defined. Several calling conventions
31561 are available for Windows:
31565 @code{C} (Microsoft defined)
31568 @code{Stdcall} (Microsoft defined)
31571 @code{Win32} (GNAT specific)
31574 @code{DLL} (GNAT specific)
31577 @node C Calling Convention
31578 @subsection @code{C} Calling Convention
31581 This is the default calling convention used when interfacing to C/C++
31582 routines compiled with either @command{gcc} or Microsoft Visual C++.
31584 In the @code{C} calling convention subprogram parameters are pushed on the
31585 stack by the caller from right to left. The caller itself is in charge of
31586 cleaning up the stack after the call. In addition, the name of a routine
31587 with @code{C} calling convention is mangled by adding a leading underscore.
31589 The name to use on the Ada side when importing (or exporting) a routine
31590 with @code{C} calling convention is the name of the routine. For
31591 instance the C function:
31594 int get_val (long);
31598 should be imported from Ada as follows:
31600 @smallexample @c ada
31602 function Get_Val (V : Interfaces.C.long) return Interfaces.C.int;
31603 pragma Import (C, Get_Val, External_Name => "get_val");
31608 Note that in this particular case the @code{External_Name} parameter could
31609 have been omitted since, when missing, this parameter is taken to be the
31610 name of the Ada entity in lower case. When the @code{Link_Name} parameter
31611 is missing, as in the above example, this parameter is set to be the
31612 @code{External_Name} with a leading underscore.
31614 When importing a variable defined in C, you should always use the @code{C}
31615 calling convention unless the object containing the variable is part of a
31616 DLL (in which case you should use the @code{Stdcall} calling
31617 convention, @pxref{Stdcall Calling Convention}).
31619 @node Stdcall Calling Convention
31620 @subsection @code{Stdcall} Calling Convention
31623 This convention, which was the calling convention used for Pascal
31624 programs, is used by Microsoft for all the routines in the Win32 API for
31625 efficiency reasons. It must be used to import any routine for which this
31626 convention was specified.
31628 In the @code{Stdcall} calling convention subprogram parameters are pushed
31629 on the stack by the caller from right to left. The callee (and not the
31630 caller) is in charge of cleaning the stack on routine exit. In addition,
31631 the name of a routine with @code{Stdcall} calling convention is mangled by
31632 adding a leading underscore (as for the @code{C} calling convention) and a
31633 trailing @code{@@}@code{@var{nn}}, where @var{nn} is the overall size (in
31634 bytes) of the parameters passed to the routine.
31636 The name to use on the Ada side when importing a C routine with a
31637 @code{Stdcall} calling convention is the name of the C routine. The leading
31638 underscore and trailing @code{@@}@code{@var{nn}} are added automatically by
31639 the compiler. For instance the Win32 function:
31642 @b{APIENTRY} int get_val (long);
31646 should be imported from Ada as follows:
31648 @smallexample @c ada
31650 function Get_Val (V : Interfaces.C.long) return Interfaces.C.int;
31651 pragma Import (Stdcall, Get_Val);
31652 -- On the x86 a long is 4 bytes, so the Link_Name is "_get_val@@4"
31657 As for the @code{C} calling convention, when the @code{External_Name}
31658 parameter is missing, it is taken to be the name of the Ada entity in lower
31659 case. If instead of writing the above import pragma you write:
31661 @smallexample @c ada
31663 function Get_Val (V : Interfaces.C.long) return Interfaces.C.int;
31664 pragma Import (Stdcall, Get_Val, External_Name => "retrieve_val");
31669 then the imported routine is @code{_retrieve_val@@4}. However, if instead
31670 of specifying the @code{External_Name} parameter you specify the
31671 @code{Link_Name} as in the following example:
31673 @smallexample @c ada
31675 function Get_Val (V : Interfaces.C.long) return Interfaces.C.int;
31676 pragma Import (Stdcall, Get_Val, Link_Name => "retrieve_val");
31681 then the imported routine is @code{retrieve_val}, that is, there is no
31682 decoration at all. No leading underscore and no Stdcall suffix
31683 @code{@@}@code{@var{nn}}.
31686 This is especially important as in some special cases a DLL's entry
31687 point name lacks a trailing @code{@@}@code{@var{nn}} while the exported
31688 name generated for a call has it.
31691 It is also possible to import variables defined in a DLL by using an
31692 import pragma for a variable. As an example, if a DLL contains a
31693 variable defined as:
31700 then, to access this variable from Ada you should write:
31702 @smallexample @c ada
31704 My_Var : Interfaces.C.int;
31705 pragma Import (Stdcall, My_Var);
31710 Note that to ease building cross-platform bindings this convention
31711 will be handled as a @code{C} calling convention on non-Windows platforms.
31713 @node Win32 Calling Convention
31714 @subsection @code{Win32} Calling Convention
31717 This convention, which is GNAT-specific is fully equivalent to the
31718 @code{Stdcall} calling convention described above.
31720 @node DLL Calling Convention
31721 @subsection @code{DLL} Calling Convention
31724 This convention, which is GNAT-specific is fully equivalent to the
31725 @code{Stdcall} calling convention described above.
31727 @node Introduction to Dynamic Link Libraries (DLLs)
31728 @section Introduction to Dynamic Link Libraries (DLLs)
31732 A Dynamically Linked Library (DLL) is a library that can be shared by
31733 several applications running under Windows. A DLL can contain any number of
31734 routines and variables.
31736 One advantage of DLLs is that you can change and enhance them without
31737 forcing all the applications that depend on them to be relinked or
31738 recompiled. However, you should be aware than all calls to DLL routines are
31739 slower since, as you will understand below, such calls are indirect.
31741 To illustrate the remainder of this section, suppose that an application
31742 wants to use the services of a DLL @file{API.dll}. To use the services
31743 provided by @file{API.dll} you must statically link against the DLL or
31744 an import library which contains a jump table with an entry for each
31745 routine and variable exported by the DLL. In the Microsoft world this
31746 import library is called @file{API.lib}. When using GNAT this import
31747 library is called either @file{libAPI.dll.a}, @file{libapi.dll.a},
31748 @file{libAPI.a} or @file{libapi.a} (names are case insensitive).
31750 After you have linked your application with the DLL or the import library
31751 and you run your application, here is what happens:
31755 Your application is loaded into memory.
31758 The DLL @file{API.dll} is mapped into the address space of your
31759 application. This means that:
31763 The DLL will use the stack of the calling thread.
31766 The DLL will use the virtual address space of the calling process.
31769 The DLL will allocate memory from the virtual address space of the calling
31773 Handles (pointers) can be safely exchanged between routines in the DLL
31774 routines and routines in the application using the DLL.
31778 The entries in the jump table (from the import library @file{libAPI.dll.a}
31779 or @file{API.lib} or automatically created when linking against a DLL)
31780 which is part of your application are initialized with the addresses
31781 of the routines and variables in @file{API.dll}.
31784 If present in @file{API.dll}, routines @code{DllMain} or
31785 @code{DllMainCRTStartup} are invoked. These routines typically contain
31786 the initialization code needed for the well-being of the routines and
31787 variables exported by the DLL.
31791 There is an additional point which is worth mentioning. In the Windows
31792 world there are two kind of DLLs: relocatable and non-relocatable
31793 DLLs. Non-relocatable DLLs can only be loaded at a very specific address
31794 in the target application address space. If the addresses of two
31795 non-relocatable DLLs overlap and these happen to be used by the same
31796 application, a conflict will occur and the application will run
31797 incorrectly. Hence, when possible, it is always preferable to use and
31798 build relocatable DLLs. Both relocatable and non-relocatable DLLs are
31799 supported by GNAT. Note that the @option{-s} linker option (see GNU Linker
31800 User's Guide) removes the debugging symbols from the DLL but the DLL can
31801 still be relocated.
31803 As a side note, an interesting difference between Microsoft DLLs and
31804 Unix shared libraries, is the fact that on most Unix systems all public
31805 routines are exported by default in a Unix shared library, while under
31806 Windows it is possible (but not required) to list exported routines in
31807 a definition file (@pxref{The Definition File}).
31809 @node Using DLLs with GNAT
31810 @section Using DLLs with GNAT
31813 * Creating an Ada Spec for the DLL Services::
31814 * Creating an Import Library::
31818 To use the services of a DLL, say @file{API.dll}, in your Ada application
31823 The Ada spec for the routines and/or variables you want to access in
31824 @file{API.dll}. If not available this Ada spec must be built from the C/C++
31825 header files provided with the DLL.
31828 The import library (@file{libAPI.dll.a} or @file{API.lib}). As previously
31829 mentioned an import library is a statically linked library containing the
31830 import table which will be filled at load time to point to the actual
31831 @file{API.dll} routines. Sometimes you don't have an import library for the
31832 DLL you want to use. The following sections will explain how to build
31833 one. Note that this is optional.
31836 The actual DLL, @file{API.dll}.
31840 Once you have all the above, to compile an Ada application that uses the
31841 services of @file{API.dll} and whose main subprogram is @code{My_Ada_App},
31842 you simply issue the command
31845 $ gnatmake my_ada_app -largs -lAPI
31849 The argument @option{-largs -lAPI} at the end of the @command{gnatmake} command
31850 tells the GNAT linker to look first for a library named @file{API.lib}
31851 (Microsoft-style name) and if not found for a libraries named
31852 @file{libAPI.dll.a}, @file{API.dll.a} or @file{libAPI.a}.
31853 (GNAT-style name). Note that if the Ada package spec for @file{API.dll}
31854 contains the following pragma
31856 @smallexample @c ada
31857 pragma Linker_Options ("-lAPI");
31861 you do not have to add @option{-largs -lAPI} at the end of the
31862 @command{gnatmake} command.
31864 If any one of the items above is missing you will have to create it
31865 yourself. The following sections explain how to do so using as an
31866 example a fictitious DLL called @file{API.dll}.
31868 @node Creating an Ada Spec for the DLL Services
31869 @subsection Creating an Ada Spec for the DLL Services
31872 A DLL typically comes with a C/C++ header file which provides the
31873 definitions of the routines and variables exported by the DLL. The Ada
31874 equivalent of this header file is a package spec that contains definitions
31875 for the imported entities. If the DLL you intend to use does not come with
31876 an Ada spec you have to generate one such spec yourself. For example if
31877 the header file of @file{API.dll} is a file @file{api.h} containing the
31878 following two definitions:
31890 then the equivalent Ada spec could be:
31892 @smallexample @c ada
31895 with Interfaces.C.Strings;
31900 function Get (Str : C.Strings.Chars_Ptr) return C.int;
31903 pragma Import (C, Get);
31904 pragma Import (DLL, Some_Var);
31911 Note that a variable is
31912 @strong{always imported with a Stdcall convention}. A function
31913 can have @code{C} or @code{Stdcall} convention.
31914 (@pxref{Windows Calling Conventions}).
31916 @node Creating an Import Library
31917 @subsection Creating an Import Library
31918 @cindex Import library
31921 * The Definition File::
31922 * GNAT-Style Import Library::
31923 * Microsoft-Style Import Library::
31927 If a Microsoft-style import library @file{API.lib} or a GNAT-style
31928 import library @file{libAPI.dll.a} or @file{libAPI.a} is available
31929 with @file{API.dll} you can skip this section. You can also skip this
31930 section if @file{API.dll} or @file{libAPI.dll} is built with GNU tools
31931 as in this case it is possible to link directly against the
31932 DLL. Otherwise read on.
31934 @node The Definition File
31935 @subsubsection The Definition File
31936 @cindex Definition file
31940 As previously mentioned, and unlike Unix systems, the list of symbols
31941 that are exported from a DLL must be provided explicitly in Windows.
31942 The main goal of a definition file is precisely that: list the symbols
31943 exported by a DLL. A definition file (usually a file with a @code{.def}
31944 suffix) has the following structure:
31949 @r{[}LIBRARY @var{name}@r{]}
31950 @r{[}DESCRIPTION @var{string}@r{]}
31960 @item LIBRARY @var{name}
31961 This section, which is optional, gives the name of the DLL.
31963 @item DESCRIPTION @var{string}
31964 This section, which is optional, gives a description string that will be
31965 embedded in the import library.
31968 This section gives the list of exported symbols (procedures, functions or
31969 variables). For instance in the case of @file{API.dll} the @code{EXPORTS}
31970 section of @file{API.def} looks like:
31984 Note that you must specify the correct suffix (@code{@@}@code{@var{nn}})
31985 (@pxref{Windows Calling Conventions}) for a Stdcall
31986 calling convention function in the exported symbols list.
31989 There can actually be other sections in a definition file, but these
31990 sections are not relevant to the discussion at hand.
31992 @node GNAT-Style Import Library
31993 @subsubsection GNAT-Style Import Library
31996 To create a static import library from @file{API.dll} with the GNAT tools
31997 you should proceed as follows:
32001 Create the definition file @file{API.def} (@pxref{The Definition File}).
32002 For that use the @code{dll2def} tool as follows:
32005 $ dll2def API.dll > API.def
32009 @code{dll2def} is a very simple tool: it takes as input a DLL and prints
32010 to standard output the list of entry points in the DLL. Note that if
32011 some routines in the DLL have the @code{Stdcall} convention
32012 (@pxref{Windows Calling Conventions}) with stripped @code{@@}@var{nn}
32013 suffix then you'll have to edit @file{api.def} to add it, and specify
32014 @option{-k} to @command{gnatdll} when creating the import library.
32017 Here are some hints to find the right @code{@@}@var{nn} suffix.
32021 If you have the Microsoft import library (.lib), it is possible to get
32022 the right symbols by using Microsoft @code{dumpbin} tool (see the
32023 corresponding Microsoft documentation for further details).
32026 $ dumpbin /exports api.lib
32030 If you have a message about a missing symbol at link time the compiler
32031 tells you what symbol is expected. You just have to go back to the
32032 definition file and add the right suffix.
32036 Build the import library @code{libAPI.dll.a}, using @code{gnatdll}
32037 (@pxref{Using gnatdll}) as follows:
32040 $ gnatdll -e API.def -d API.dll
32044 @code{gnatdll} takes as input a definition file @file{API.def} and the
32045 name of the DLL containing the services listed in the definition file
32046 @file{API.dll}. The name of the static import library generated is
32047 computed from the name of the definition file as follows: if the
32048 definition file name is @var{xyz}@code{.def}, the import library name will
32049 be @code{lib}@var{xyz}@code{.a}. Note that in the previous example option
32050 @option{-e} could have been removed because the name of the definition
32051 file (before the ``@code{.def}'' suffix) is the same as the name of the
32052 DLL (@pxref{Using gnatdll} for more information about @code{gnatdll}).
32055 @node Microsoft-Style Import Library
32056 @subsubsection Microsoft-Style Import Library
32059 With GNAT you can either use a GNAT-style or Microsoft-style import
32060 library. A Microsoft import library is needed only if you plan to make an
32061 Ada DLL available to applications developed with Microsoft
32062 tools (@pxref{Mixed-Language Programming on Windows}).
32064 To create a Microsoft-style import library for @file{API.dll} you
32065 should proceed as follows:
32069 Create the definition file @file{API.def} from the DLL. For this use either
32070 the @code{dll2def} tool as described above or the Microsoft @code{dumpbin}
32071 tool (see the corresponding Microsoft documentation for further details).
32074 Build the actual import library using Microsoft's @code{lib} utility:
32077 $ lib -machine:IX86 -def:API.def -out:API.lib
32081 If you use the above command the definition file @file{API.def} must
32082 contain a line giving the name of the DLL:
32089 See the Microsoft documentation for further details about the usage of
32093 @node Building DLLs with GNAT
32094 @section Building DLLs with GNAT
32095 @cindex DLLs, building
32098 This section explain how to build DLLs using the GNAT built-in DLL
32099 support. With the following procedure it is straight forward to build
32100 and use DLLs with GNAT.
32104 @item building object files
32106 The first step is to build all objects files that are to be included
32107 into the DLL. This is done by using the standard @command{gnatmake} tool.
32109 @item building the DLL
32111 To build the DLL you must use @command{gcc}'s @option{-shared}
32112 option. It is quite simple to use this method:
32115 $ gcc -shared -o api.dll obj1.o obj2.o @dots{}
32118 It is important to note that in this case all symbols found in the
32119 object files are automatically exported. It is possible to restrict
32120 the set of symbols to export by passing to @command{gcc} a definition
32121 file, @pxref{The Definition File}. For example:
32124 $ gcc -shared -o api.dll api.def obj1.o obj2.o @dots{}
32127 If you use a definition file you must export the elaboration procedures
32128 for every package that required one. Elaboration procedures are named
32129 using the package name followed by "_E".
32131 @item preparing DLL to be used
32133 For the DLL to be used by client programs the bodies must be hidden
32134 from it and the .ali set with read-only attribute. This is very important
32135 otherwise GNAT will recompile all packages and will not actually use
32136 the code in the DLL. For example:
32140 $ copy *.ads *.ali api.dll apilib
32141 $ attrib +R apilib\*.ali
32146 At this point it is possible to use the DLL by directly linking
32147 against it. Note that you must use the GNAT shared runtime when using
32148 GNAT shared libraries. This is achieved by using @option{-shared} binder's
32152 $ gnatmake main -Iapilib -bargs -shared -largs -Lapilib -lAPI
32155 @node Building DLLs with GNAT Project files
32156 @section Building DLLs with GNAT Project files
32157 @cindex DLLs, building
32160 There is nothing specific to Windows in the build process.
32161 @pxref{Library Projects}.
32164 Due to a system limitation, it is not possible under Windows to create threads
32165 when inside the @code{DllMain} routine which is used for auto-initialization
32166 of shared libraries, so it is not possible to have library level tasks in SALs.
32168 @node Building DLLs with gnatdll
32169 @section Building DLLs with gnatdll
32170 @cindex DLLs, building
32173 * Limitations When Using Ada DLLs from Ada::
32174 * Exporting Ada Entities::
32175 * Ada DLLs and Elaboration::
32176 * Ada DLLs and Finalization::
32177 * Creating a Spec for Ada DLLs::
32178 * Creating the Definition File::
32183 Note that it is preferred to use the built-in GNAT DLL support
32184 (@pxref{Building DLLs with GNAT}) or GNAT Project files
32185 (@pxref{Building DLLs with GNAT Project files}) to build DLLs.
32187 This section explains how to build DLLs containing Ada code using
32188 @code{gnatdll}. These DLLs will be referred to as Ada DLLs in the
32189 remainder of this section.
32191 The steps required to build an Ada DLL that is to be used by Ada as well as
32192 non-Ada applications are as follows:
32196 You need to mark each Ada @i{entity} exported by the DLL with a @code{C} or
32197 @code{Stdcall} calling convention to avoid any Ada name mangling for the
32198 entities exported by the DLL (@pxref{Exporting Ada Entities}). You can
32199 skip this step if you plan to use the Ada DLL only from Ada applications.
32202 Your Ada code must export an initialization routine which calls the routine
32203 @code{adainit} generated by @command{gnatbind} to perform the elaboration of
32204 the Ada code in the DLL (@pxref{Ada DLLs and Elaboration}). The initialization
32205 routine exported by the Ada DLL must be invoked by the clients of the DLL
32206 to initialize the DLL.
32209 When useful, the DLL should also export a finalization routine which calls
32210 routine @code{adafinal} generated by @command{gnatbind} to perform the
32211 finalization of the Ada code in the DLL (@pxref{Ada DLLs and Finalization}).
32212 The finalization routine exported by the Ada DLL must be invoked by the
32213 clients of the DLL when the DLL services are no further needed.
32216 You must provide a spec for the services exported by the Ada DLL in each
32217 of the programming languages to which you plan to make the DLL available.
32220 You must provide a definition file listing the exported entities
32221 (@pxref{The Definition File}).
32224 Finally you must use @code{gnatdll} to produce the DLL and the import
32225 library (@pxref{Using gnatdll}).
32229 Note that a relocatable DLL stripped using the @code{strip}
32230 binutils tool will not be relocatable anymore. To build a DLL without
32231 debug information pass @code{-largs -s} to @code{gnatdll}. This
32232 restriction does not apply to a DLL built using a Library Project.
32233 @pxref{Library Projects}.
32235 @node Limitations When Using Ada DLLs from Ada
32236 @subsection Limitations When Using Ada DLLs from Ada
32239 When using Ada DLLs from Ada applications there is a limitation users
32240 should be aware of. Because on Windows the GNAT run time is not in a DLL of
32241 its own, each Ada DLL includes a part of the GNAT run time. Specifically,
32242 each Ada DLL includes the services of the GNAT run time that are necessary
32243 to the Ada code inside the DLL. As a result, when an Ada program uses an
32244 Ada DLL there are two independent GNAT run times: one in the Ada DLL and
32245 one in the main program.
32247 It is therefore not possible to exchange GNAT run-time objects between the
32248 Ada DLL and the main Ada program. Example of GNAT run-time objects are file
32249 handles (e.g.@: @code{Text_IO.File_Type}), tasks types, protected objects
32252 It is completely safe to exchange plain elementary, array or record types,
32253 Windows object handles, etc.
32255 @node Exporting Ada Entities
32256 @subsection Exporting Ada Entities
32257 @cindex Export table
32260 Building a DLL is a way to encapsulate a set of services usable from any
32261 application. As a result, the Ada entities exported by a DLL should be
32262 exported with the @code{C} or @code{Stdcall} calling conventions to avoid
32263 any Ada name mangling. As an example here is an Ada package
32264 @code{API}, spec and body, exporting two procedures, a function, and a
32267 @smallexample @c ada
32270 with Interfaces.C; use Interfaces;
32272 Count : C.int := 0;
32273 function Factorial (Val : C.int) return C.int;
32275 procedure Initialize_API;
32276 procedure Finalize_API;
32277 -- Initialization & Finalization routines. More in the next section.
32279 pragma Export (C, Initialize_API);
32280 pragma Export (C, Finalize_API);
32281 pragma Export (C, Count);
32282 pragma Export (C, Factorial);
32288 @smallexample @c ada
32291 package body API is
32292 function Factorial (Val : C.int) return C.int is
32295 Count := Count + 1;
32296 for K in 1 .. Val loop
32302 procedure Initialize_API is
32304 pragma Import (C, Adainit);
32307 end Initialize_API;
32309 procedure Finalize_API is
32310 procedure Adafinal;
32311 pragma Import (C, Adafinal);
32321 If the Ada DLL you are building will only be used by Ada applications
32322 you do not have to export Ada entities with a @code{C} or @code{Stdcall}
32323 convention. As an example, the previous package could be written as
32326 @smallexample @c ada
32330 Count : Integer := 0;
32331 function Factorial (Val : Integer) return Integer;
32333 procedure Initialize_API;
32334 procedure Finalize_API;
32335 -- Initialization and Finalization routines.
32341 @smallexample @c ada
32344 package body API is
32345 function Factorial (Val : Integer) return Integer is
32346 Fact : Integer := 1;
32348 Count := Count + 1;
32349 for K in 1 .. Val loop
32356 -- The remainder of this package body is unchanged.
32363 Note that if you do not export the Ada entities with a @code{C} or
32364 @code{Stdcall} convention you will have to provide the mangled Ada names
32365 in the definition file of the Ada DLL
32366 (@pxref{Creating the Definition File}).
32368 @node Ada DLLs and Elaboration
32369 @subsection Ada DLLs and Elaboration
32370 @cindex DLLs and elaboration
32373 The DLL that you are building contains your Ada code as well as all the
32374 routines in the Ada library that are needed by it. The first thing a
32375 user of your DLL must do is elaborate the Ada code
32376 (@pxref{Elaboration Order Handling in GNAT}).
32378 To achieve this you must export an initialization routine
32379 (@code{Initialize_API} in the previous example), which must be invoked
32380 before using any of the DLL services. This elaboration routine must call
32381 the Ada elaboration routine @code{adainit} generated by the GNAT binder
32382 (@pxref{Binding with Non-Ada Main Programs}). See the body of
32383 @code{Initialize_Api} for an example. Note that the GNAT binder is
32384 automatically invoked during the DLL build process by the @code{gnatdll}
32385 tool (@pxref{Using gnatdll}).
32387 When a DLL is loaded, Windows systematically invokes a routine called
32388 @code{DllMain}. It would therefore be possible to call @code{adainit}
32389 directly from @code{DllMain} without having to provide an explicit
32390 initialization routine. Unfortunately, it is not possible to call
32391 @code{adainit} from the @code{DllMain} if your program has library level
32392 tasks because access to the @code{DllMain} entry point is serialized by
32393 the system (that is, only a single thread can execute ``through'' it at a
32394 time), which means that the GNAT run time will deadlock waiting for the
32395 newly created task to complete its initialization.
32397 @node Ada DLLs and Finalization
32398 @subsection Ada DLLs and Finalization
32399 @cindex DLLs and finalization
32402 When the services of an Ada DLL are no longer needed, the client code should
32403 invoke the DLL finalization routine, if available. The DLL finalization
32404 routine is in charge of releasing all resources acquired by the DLL. In the
32405 case of the Ada code contained in the DLL, this is achieved by calling
32406 routine @code{adafinal} generated by the GNAT binder
32407 (@pxref{Binding with Non-Ada Main Programs}).
32408 See the body of @code{Finalize_Api} for an
32409 example. As already pointed out the GNAT binder is automatically invoked
32410 during the DLL build process by the @code{gnatdll} tool
32411 (@pxref{Using gnatdll}).
32413 @node Creating a Spec for Ada DLLs
32414 @subsection Creating a Spec for Ada DLLs
32417 To use the services exported by the Ada DLL from another programming
32418 language (e.g.@: C), you have to translate the specs of the exported Ada
32419 entities in that language. For instance in the case of @code{API.dll},
32420 the corresponding C header file could look like:
32425 extern int *_imp__count;
32426 #define count (*_imp__count)
32427 int factorial (int);
32433 It is important to understand that when building an Ada DLL to be used by
32434 other Ada applications, you need two different specs for the packages
32435 contained in the DLL: one for building the DLL and the other for using
32436 the DLL. This is because the @code{DLL} calling convention is needed to
32437 use a variable defined in a DLL, but when building the DLL, the variable
32438 must have either the @code{Ada} or @code{C} calling convention. As an
32439 example consider a DLL comprising the following package @code{API}:
32441 @smallexample @c ada
32445 Count : Integer := 0;
32447 -- Remainder of the package omitted.
32454 After producing a DLL containing package @code{API}, the spec that
32455 must be used to import @code{API.Count} from Ada code outside of the
32458 @smallexample @c ada
32463 pragma Import (DLL, Count);
32469 @node Creating the Definition File
32470 @subsection Creating the Definition File
32473 The definition file is the last file needed to build the DLL. It lists
32474 the exported symbols. As an example, the definition file for a DLL
32475 containing only package @code{API} (where all the entities are exported
32476 with a @code{C} calling convention) is:
32491 If the @code{C} calling convention is missing from package @code{API},
32492 then the definition file contains the mangled Ada names of the above
32493 entities, which in this case are:
32502 api__initialize_api
32507 @node Using gnatdll
32508 @subsection Using @code{gnatdll}
32512 * gnatdll Example::
32513 * gnatdll behind the Scenes::
32518 @code{gnatdll} is a tool to automate the DLL build process once all the Ada
32519 and non-Ada sources that make up your DLL have been compiled.
32520 @code{gnatdll} is actually in charge of two distinct tasks: build the
32521 static import library for the DLL and the actual DLL. The form of the
32522 @code{gnatdll} command is
32526 $ gnatdll @ovar{switches} @var{list-of-files} @r{[}-largs @var{opts}@r{]}
32531 where @var{list-of-files} is a list of ALI and object files. The object
32532 file list must be the exact list of objects corresponding to the non-Ada
32533 sources whose services are to be included in the DLL. The ALI file list
32534 must be the exact list of ALI files for the corresponding Ada sources
32535 whose services are to be included in the DLL. If @var{list-of-files} is
32536 missing, only the static import library is generated.
32539 You may specify any of the following switches to @code{gnatdll}:
32542 @item -a@ovar{address}
32543 @cindex @option{-a} (@code{gnatdll})
32544 Build a non-relocatable DLL at @var{address}. If @var{address} is not
32545 specified the default address @var{0x11000000} will be used. By default,
32546 when this switch is missing, @code{gnatdll} builds relocatable DLL. We
32547 advise the reader to build relocatable DLL.
32549 @item -b @var{address}
32550 @cindex @option{-b} (@code{gnatdll})
32551 Set the relocatable DLL base address. By default the address is
32554 @item -bargs @var{opts}
32555 @cindex @option{-bargs} (@code{gnatdll})
32556 Binder options. Pass @var{opts} to the binder.
32558 @item -d @var{dllfile}
32559 @cindex @option{-d} (@code{gnatdll})
32560 @var{dllfile} is the name of the DLL. This switch must be present for
32561 @code{gnatdll} to do anything. The name of the generated import library is
32562 obtained algorithmically from @var{dllfile} as shown in the following
32563 example: if @var{dllfile} is @code{xyz.dll}, the import library name is
32564 @code{libxyz.dll.a}. The name of the definition file to use (if not specified
32565 by option @option{-e}) is obtained algorithmically from @var{dllfile}
32566 as shown in the following example:
32567 if @var{dllfile} is @code{xyz.dll}, the definition
32568 file used is @code{xyz.def}.
32570 @item -e @var{deffile}
32571 @cindex @option{-e} (@code{gnatdll})
32572 @var{deffile} is the name of the definition file.
32575 @cindex @option{-g} (@code{gnatdll})
32576 Generate debugging information. This information is stored in the object
32577 file and copied from there to the final DLL file by the linker,
32578 where it can be read by the debugger. You must use the
32579 @option{-g} switch if you plan on using the debugger or the symbolic
32583 @cindex @option{-h} (@code{gnatdll})
32584 Help mode. Displays @code{gnatdll} switch usage information.
32587 @cindex @option{-I} (@code{gnatdll})
32588 Direct @code{gnatdll} to search the @var{dir} directory for source and
32589 object files needed to build the DLL.
32590 (@pxref{Search Paths and the Run-Time Library (RTL)}).
32593 @cindex @option{-k} (@code{gnatdll})
32594 Removes the @code{@@}@var{nn} suffix from the import library's exported
32595 names, but keeps them for the link names. You must specify this
32596 option if you want to use a @code{Stdcall} function in a DLL for which
32597 the @code{@@}@var{nn} suffix has been removed. This is the case for most
32598 of the Windows NT DLL for example. This option has no effect when
32599 @option{-n} option is specified.
32601 @item -l @var{file}
32602 @cindex @option{-l} (@code{gnatdll})
32603 The list of ALI and object files used to build the DLL are listed in
32604 @var{file}, instead of being given in the command line. Each line in
32605 @var{file} contains the name of an ALI or object file.
32608 @cindex @option{-n} (@code{gnatdll})
32609 No Import. Do not create the import library.
32612 @cindex @option{-q} (@code{gnatdll})
32613 Quiet mode. Do not display unnecessary messages.
32616 @cindex @option{-v} (@code{gnatdll})
32617 Verbose mode. Display extra information.
32619 @item -largs @var{opts}
32620 @cindex @option{-largs} (@code{gnatdll})
32621 Linker options. Pass @var{opts} to the linker.
32624 @node gnatdll Example
32625 @subsubsection @code{gnatdll} Example
32628 As an example the command to build a relocatable DLL from @file{api.adb}
32629 once @file{api.adb} has been compiled and @file{api.def} created is
32632 $ gnatdll -d api.dll api.ali
32636 The above command creates two files: @file{libapi.dll.a} (the import
32637 library) and @file{api.dll} (the actual DLL). If you want to create
32638 only the DLL, just type:
32641 $ gnatdll -d api.dll -n api.ali
32645 Alternatively if you want to create just the import library, type:
32648 $ gnatdll -d api.dll
32651 @node gnatdll behind the Scenes
32652 @subsubsection @code{gnatdll} behind the Scenes
32655 This section details the steps involved in creating a DLL. @code{gnatdll}
32656 does these steps for you. Unless you are interested in understanding what
32657 goes on behind the scenes, you should skip this section.
32659 We use the previous example of a DLL containing the Ada package @code{API},
32660 to illustrate the steps necessary to build a DLL. The starting point is a
32661 set of objects that will make up the DLL and the corresponding ALI
32662 files. In the case of this example this means that @file{api.o} and
32663 @file{api.ali} are available. To build a relocatable DLL, @code{gnatdll} does
32668 @code{gnatdll} builds the base file (@file{api.base}). A base file gives
32669 the information necessary to generate relocation information for the
32675 $ gnatlink api -o api.jnk -mdll -Wl,--base-file,api.base
32680 In addition to the base file, the @command{gnatlink} command generates an
32681 output file @file{api.jnk} which can be discarded. The @option{-mdll} switch
32682 asks @command{gnatlink} to generate the routines @code{DllMain} and
32683 @code{DllMainCRTStartup} that are called by the Windows loader when the DLL
32684 is loaded into memory.
32687 @code{gnatdll} uses @code{dlltool} (@pxref{Using dlltool}) to build the
32688 export table (@file{api.exp}). The export table contains the relocation
32689 information in a form which can be used during the final link to ensure
32690 that the Windows loader is able to place the DLL anywhere in memory.
32694 $ dlltool --dllname api.dll --def api.def --base-file api.base \
32695 --output-exp api.exp
32700 @code{gnatdll} builds the base file using the new export table. Note that
32701 @command{gnatbind} must be called once again since the binder generated file
32702 has been deleted during the previous call to @command{gnatlink}.
32707 $ gnatlink api -o api.jnk api.exp -mdll
32708 -Wl,--base-file,api.base
32713 @code{gnatdll} builds the new export table using the new base file and
32714 generates the DLL import library @file{libAPI.dll.a}.
32718 $ dlltool --dllname api.dll --def api.def --base-file api.base \
32719 --output-exp api.exp --output-lib libAPI.a
32724 Finally @code{gnatdll} builds the relocatable DLL using the final export
32730 $ gnatlink api api.exp -o api.dll -mdll
32735 @node Using dlltool
32736 @subsubsection Using @code{dlltool}
32739 @code{dlltool} is the low-level tool used by @code{gnatdll} to build
32740 DLLs and static import libraries. This section summarizes the most
32741 common @code{dlltool} switches. The form of the @code{dlltool} command
32745 $ dlltool @ovar{switches}
32749 @code{dlltool} switches include:
32752 @item --base-file @var{basefile}
32753 @cindex @option{--base-file} (@command{dlltool})
32754 Read the base file @var{basefile} generated by the linker. This switch
32755 is used to create a relocatable DLL.
32757 @item --def @var{deffile}
32758 @cindex @option{--def} (@command{dlltool})
32759 Read the definition file.
32761 @item --dllname @var{name}
32762 @cindex @option{--dllname} (@command{dlltool})
32763 Gives the name of the DLL. This switch is used to embed the name of the
32764 DLL in the static import library generated by @code{dlltool} with switch
32765 @option{--output-lib}.
32768 @cindex @option{-k} (@command{dlltool})
32769 Kill @code{@@}@var{nn} from exported names
32770 (@pxref{Windows Calling Conventions}
32771 for a discussion about @code{Stdcall}-style symbols.
32774 @cindex @option{--help} (@command{dlltool})
32775 Prints the @code{dlltool} switches with a concise description.
32777 @item --output-exp @var{exportfile}
32778 @cindex @option{--output-exp} (@command{dlltool})
32779 Generate an export file @var{exportfile}. The export file contains the
32780 export table (list of symbols in the DLL) and is used to create the DLL.
32782 @item --output-lib @var{libfile}
32783 @cindex @option{--output-lib} (@command{dlltool})
32784 Generate a static import library @var{libfile}.
32787 @cindex @option{-v} (@command{dlltool})
32790 @item --as @var{assembler-name}
32791 @cindex @option{--as} (@command{dlltool})
32792 Use @var{assembler-name} as the assembler. The default is @code{as}.
32795 @node GNAT and Windows Resources
32796 @section GNAT and Windows Resources
32797 @cindex Resources, windows
32800 * Building Resources::
32801 * Compiling Resources::
32802 * Using Resources::
32806 Resources are an easy way to add Windows specific objects to your
32807 application. The objects that can be added as resources include:
32836 This section explains how to build, compile and use resources.
32838 @node Building Resources
32839 @subsection Building Resources
32840 @cindex Resources, building
32843 A resource file is an ASCII file. By convention resource files have an
32844 @file{.rc} extension.
32845 The easiest way to build a resource file is to use Microsoft tools
32846 such as @code{imagedit.exe} to build bitmaps, icons and cursors and
32847 @code{dlgedit.exe} to build dialogs.
32848 It is always possible to build an @file{.rc} file yourself by writing a
32851 It is not our objective to explain how to write a resource file. A
32852 complete description of the resource script language can be found in the
32853 Microsoft documentation.
32855 @node Compiling Resources
32856 @subsection Compiling Resources
32859 @cindex Resources, compiling
32862 This section describes how to build a GNAT-compatible (COFF) object file
32863 containing the resources. This is done using the Resource Compiler
32864 @code{windres} as follows:
32867 $ windres -i myres.rc -o myres.o
32871 By default @code{windres} will run @command{gcc} to preprocess the @file{.rc}
32872 file. You can specify an alternate preprocessor (usually named
32873 @file{cpp.exe}) using the @code{windres} @option{--preprocessor}
32874 parameter. A list of all possible options may be obtained by entering
32875 the command @code{windres} @option{--help}.
32877 It is also possible to use the Microsoft resource compiler @code{rc.exe}
32878 to produce a @file{.res} file (binary resource file). See the
32879 corresponding Microsoft documentation for further details. In this case
32880 you need to use @code{windres} to translate the @file{.res} file to a
32881 GNAT-compatible object file as follows:
32884 $ windres -i myres.res -o myres.o
32887 @node Using Resources
32888 @subsection Using Resources
32889 @cindex Resources, using
32892 To include the resource file in your program just add the
32893 GNAT-compatible object file for the resource(s) to the linker
32894 arguments. With @command{gnatmake} this is done by using the @option{-largs}
32898 $ gnatmake myprog -largs myres.o
32901 @node Debugging a DLL
32902 @section Debugging a DLL
32903 @cindex DLL debugging
32906 * Program and DLL Both Built with GCC/GNAT::
32907 * Program Built with Foreign Tools and DLL Built with GCC/GNAT::
32911 Debugging a DLL is similar to debugging a standard program. But
32912 we have to deal with two different executable parts: the DLL and the
32913 program that uses it. We have the following four possibilities:
32917 The program and the DLL are built with @code{GCC/GNAT}.
32919 The program is built with foreign tools and the DLL is built with
32922 The program is built with @code{GCC/GNAT} and the DLL is built with
32928 In this section we address only cases one and two above.
32929 There is no point in trying to debug
32930 a DLL with @code{GNU/GDB}, if there is no GDB-compatible debugging
32931 information in it. To do so you must use a debugger compatible with the
32932 tools suite used to build the DLL.
32934 @node Program and DLL Both Built with GCC/GNAT
32935 @subsection Program and DLL Both Built with GCC/GNAT
32938 This is the simplest case. Both the DLL and the program have @code{GDB}
32939 compatible debugging information. It is then possible to break anywhere in
32940 the process. Let's suppose here that the main procedure is named
32941 @code{ada_main} and that in the DLL there is an entry point named
32945 The DLL (@pxref{Introduction to Dynamic Link Libraries (DLLs)}) and
32946 program must have been built with the debugging information (see GNAT -g
32947 switch). Here are the step-by-step instructions for debugging it:
32950 @item Launch @code{GDB} on the main program.
32956 @item Start the program and stop at the beginning of the main procedure
32963 This step is required to be able to set a breakpoint inside the DLL. As long
32964 as the program is not run, the DLL is not loaded. This has the
32965 consequence that the DLL debugging information is also not loaded, so it is not
32966 possible to set a breakpoint in the DLL.
32968 @item Set a breakpoint inside the DLL
32971 (gdb) break ada_dll
32978 At this stage a breakpoint is set inside the DLL. From there on
32979 you can use the standard approach to debug the whole program
32980 (@pxref{Running and Debugging Ada Programs}).
32983 @c This used to work, probably because the DLLs were non-relocatable
32984 @c keep this section around until the problem is sorted out.
32986 To break on the @code{DllMain} routine it is not possible to follow
32987 the procedure above. At the time the program stop on @code{ada_main}
32988 the @code{DllMain} routine as already been called. Either you can use
32989 the procedure below @pxref{Debugging the DLL Directly} or this procedure:
32992 @item Launch @code{GDB} on the main program.
32998 @item Load DLL symbols
33001 (gdb) add-sym api.dll
33004 @item Set a breakpoint inside the DLL
33007 (gdb) break ada_dll.adb:45
33010 Note that at this point it is not possible to break using the routine symbol
33011 directly as the program is not yet running. The solution is to break
33012 on the proper line (break in @file{ada_dll.adb} line 45).
33014 @item Start the program
33023 @node Program Built with Foreign Tools and DLL Built with GCC/GNAT
33024 @subsection Program Built with Foreign Tools and DLL Built with GCC/GNAT
33027 * Debugging the DLL Directly::
33028 * Attaching to a Running Process::
33032 In this case things are slightly more complex because it is not possible to
33033 start the main program and then break at the beginning to load the DLL and the
33034 associated DLL debugging information. It is not possible to break at the
33035 beginning of the program because there is no @code{GDB} debugging information,
33036 and therefore there is no direct way of getting initial control. This
33037 section addresses this issue by describing some methods that can be used
33038 to break somewhere in the DLL to debug it.
33041 First suppose that the main procedure is named @code{main} (this is for
33042 example some C code built with Microsoft Visual C) and that there is a
33043 DLL named @code{test.dll} containing an Ada entry point named
33047 The DLL (@pxref{Introduction to Dynamic Link Libraries (DLLs)}) must have
33048 been built with debugging information (see GNAT -g option).
33050 @node Debugging the DLL Directly
33051 @subsubsection Debugging the DLL Directly
33055 Find out the executable starting address
33058 $ objdump --file-header main.exe
33061 The starting address is reported on the last line. For example:
33064 main.exe: file format pei-i386
33065 architecture: i386, flags 0x0000010a:
33066 EXEC_P, HAS_DEBUG, D_PAGED
33067 start address 0x00401010
33071 Launch the debugger on the executable.
33078 Set a breakpoint at the starting address, and launch the program.
33081 $ (gdb) break *0x00401010
33085 The program will stop at the given address.
33088 Set a breakpoint on a DLL subroutine.
33091 (gdb) break ada_dll.adb:45
33094 Or if you want to break using a symbol on the DLL, you need first to
33095 select the Ada language (language used by the DLL).
33098 (gdb) set language ada
33099 (gdb) break ada_dll
33103 Continue the program.
33110 This will run the program until it reaches the breakpoint that has been
33111 set. From that point you can use the standard way to debug a program
33112 as described in (@pxref{Running and Debugging Ada Programs}).
33117 It is also possible to debug the DLL by attaching to a running process.
33119 @node Attaching to a Running Process
33120 @subsubsection Attaching to a Running Process
33121 @cindex DLL debugging, attach to process
33124 With @code{GDB} it is always possible to debug a running process by
33125 attaching to it. It is possible to debug a DLL this way. The limitation
33126 of this approach is that the DLL must run long enough to perform the
33127 attach operation. It may be useful for instance to insert a time wasting
33128 loop in the code of the DLL to meet this criterion.
33132 @item Launch the main program @file{main.exe}.
33138 @item Use the Windows @i{Task Manager} to find the process ID. Let's say
33139 that the process PID for @file{main.exe} is 208.
33147 @item Attach to the running process to be debugged.
33153 @item Load the process debugging information.
33156 (gdb) symbol-file main.exe
33159 @item Break somewhere in the DLL.
33162 (gdb) break ada_dll
33165 @item Continue process execution.
33174 This last step will resume the process execution, and stop at
33175 the breakpoint we have set. From there you can use the standard
33176 approach to debug a program as described in
33177 (@pxref{Running and Debugging Ada Programs}).
33179 @node Setting Stack Size from gnatlink
33180 @section Setting Stack Size from @command{gnatlink}
33183 It is possible to specify the program stack size at link time. On modern
33184 versions of Windows, starting with XP, this is mostly useful to set the size of
33185 the main stack (environment task). The other task stacks are set with pragma
33186 Storage_Size or with the @command{gnatbind -d} command.
33188 Since older versions of Windows (2000, NT4, etc.) do not allow setting the
33189 reserve size of individual tasks, the link-time stack size applies to all
33190 tasks, and pragma Storage_Size has no effect.
33191 In particular, Stack Overflow checks are made against this
33192 link-time specified size.
33194 This setting can be done with
33195 @command{gnatlink} using either:
33199 @item using @option{-Xlinker} linker option
33202 $ gnatlink hello -Xlinker --stack=0x10000,0x1000
33205 This sets the stack reserve size to 0x10000 bytes and the stack commit
33206 size to 0x1000 bytes.
33208 @item using @option{-Wl} linker option
33211 $ gnatlink hello -Wl,--stack=0x1000000
33214 This sets the stack reserve size to 0x1000000 bytes. Note that with
33215 @option{-Wl} option it is not possible to set the stack commit size
33216 because the coma is a separator for this option.
33220 @node Setting Heap Size from gnatlink
33221 @section Setting Heap Size from @command{gnatlink}
33224 Under Windows systems, it is possible to specify the program heap size from
33225 @command{gnatlink} using either:
33229 @item using @option{-Xlinker} linker option
33232 $ gnatlink hello -Xlinker --heap=0x10000,0x1000
33235 This sets the heap reserve size to 0x10000 bytes and the heap commit
33236 size to 0x1000 bytes.
33238 @item using @option{-Wl} linker option
33241 $ gnatlink hello -Wl,--heap=0x1000000
33244 This sets the heap reserve size to 0x1000000 bytes. Note that with
33245 @option{-Wl} option it is not possible to set the heap commit size
33246 because the coma is a separator for this option.
33252 @c **********************************
33253 @c * GNU Free Documentation License *
33254 @c **********************************
33256 @c GNU Free Documentation License
33258 @node Index,,GNU Free Documentation License, Top
33264 @c Put table of contents at end, otherwise it precedes the "title page" in
33265 @c the .txt version
33266 @c Edit the pdf file to move the contents to the beginning, after the title