Skip to content

R
riscv-gcc-1
Commit e42d2186 by Arnaud Charlet Committed by Arnaud Charlet
Options

gnat_ugn.texi, [...]: Regenerate. 

	* gnat_ugn.texi, gnat_rm.texi: Regenerate.
	* doc/gnat_ugn/gnat_project_manager.rst,
	doc/gnat_ugn/building_executable_programs_with_gnat.rst,
	doc/gnat_ugn/the_gnat_compilation_model.rst,
	doc/gnat_rm/standard_and_implementation_defined_restrictions.rst,
	doc/gnat_rm/implementation_defined_pragmas.rst,
	doc/gnat_rm/the_gnat_library.rst,
	doc/gnat_rm/implementation_defined_characteristics.rst: Update doc.

From-SVN: r229046
parent 2ee31fbf
Showing with 98 additions and 83 deletions
gcc/ada/ChangeLog
2015-10-20 Arnaud Charlet <charlet@adacore.com>
* gnat_ugn.texi, gnat_rm.texi: Regenerate.
* doc/gnat_ugn/gnat_project_manager.rst,
doc/gnat_ugn/building_executable_programs_with_gnat.rst,
doc/gnat_ugn/the_gnat_compilation_model.rst,
doc/gnat_rm/standard_and_implementation_defined_restrictions.rst,
doc/gnat_rm/implementation_defined_pragmas.rst,
doc/gnat_rm/the_gnat_library.rst,
doc/gnat_rm/implementation_defined_characteristics.rst: Update doc.
2015-10-20 Arnaud Charlet <charlet@adacore.com>
* gcc-interface/Makefile.in: Update targets.
2015-10-20 Bob Duff <duff@adacore.com>
......
gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst
......@@ -803,24 +803,6 @@ compatibility with the standard `Assertion_Policy` pragma. The check
policy setting `DISABLE` causes the second argument of a corresponding
`Check` pragma to be completely ignored and not analyzed.
Pragma CIL_Constructor
======================
Syntax:
::
pragma CIL_Constructor ([Entity =>] function_LOCAL_NAME);
This pragma is used to assert that the specified Ada function should be
mapped to the .NET constructor for some Ada tagged record type.
See section 4.1 of the
`GNAT User's Guide: Supplement for the .NET Platform.`
for related information.
Pragma Comment
==============
......@@ -2864,42 +2846,6 @@ invariant pragma for the same entity.
For further details on the use of this pragma, see the Ada 2012 documentation
of the Type_Invariant aspect.
Pragma Java_Constructor
=======================
Syntax:
::
pragma Java_Constructor ([Entity =>] function_LOCAL_NAME);
This pragma is used to assert that the specified Ada function should be
mapped to the Java constructor for some Ada tagged record type.
See section 7.3.2 of the
`GNAT User's Guide: Supplement for the JVM Platform.`
for related information.
Pragma Java_Interface
=====================
Syntax:
::
pragma Java_Interface ([Entity =>] abstract_tagged_type_LOCAL_NAME);
This pragma is used to assert that the specified Ada abstract tagged type
is to be mapped to a Java interface name.
See sections 7.1 and 7.2 of the
`GNAT User's Guide: Supplement for the JVM Platform.`
for related information.
Pragma Keep_Names
=================
......@@ -5770,6 +5716,13 @@ names that are implementation defined (as permitted by the RM):
for a duplicated tag value when a tagged type is declared.
*
`Container_Checks` Can be used to suppress all checks within Ada.Containers
and instances of its children, including Tampering_Check.
*
`Tampering_Check` Can be used to suppress tampering check in the containers.
*
`Predicate_Check` can be used to control whether predicate checks are
active. It is applicable only to predicates for which the policy is
`Check`. Unlike `Assertion_Policy`, which determines if a given
......@@ -6479,8 +6432,8 @@ configuration pragma will ensure this test is not suppressed:
This pragma is standard in Ada 2005. It is available in all earlier versions
of Ada as an implementation-defined pragma.
Note that in addition to the checks defined in the Ada RM, GNAT recogizes
a number of implementation-defined check names. See description of pragma
Note that in addition to the checks defined in the Ada RM, GNAT recogizes a
number of implementation-defined check names. See the description of pragma
`Suppress` for full details.
Pragma Use_VADS_Size
......
gcc/ada/doc/gnat_rm/standard_and_implementation_defined_restrictions.rst
......@@ -137,12 +137,19 @@ No_Anonymous_Allocators
[RM H.4] This restriction ensures at compile time that there are no
occurrences of an allocator of anonymous access type.
No_Asynchronous_Control
-----------------------
.. index:: No_Asynchronous_Control
[RM J.13] This restriction ensures at compile time that there are no semantic
dependences on the predefined package Asynchronous_Task_Control.
No_Calendar
-----------
.. index:: No_Calendar
[GNAT] This restriction ensures at compile time that there is no implicit or
explicit dependence on the package `Ada.Calendar`.
[GNAT] This restriction ensures at compile time that there are no semantic
dependences on package Calendar.
No_Coextensions
---------------
......@@ -170,14 +177,14 @@ No_Delay
.. index:: No_Delay
[RM H.4] This restriction ensures at compile time that there are no
delay statements and no dependences on package Calendar.
delay statements and no semantic dependences on package Calendar.
No_Dependence
-------------
.. index:: No_Dependence
[RM 13.12.1] This restriction checks at compile time that there are no
dependence on a library unit.
[RM 13.12.1] This restriction ensures at compile time that there are no
dependences on a library unit.
No_Direct_Boolean_Operators
---------------------------
......@@ -709,6 +716,20 @@ No_Unchecked_Access
[RM H.4] This restriction ensures at compile time that there are no
occurrences of the Unchecked_Access attribute.
No_Unchecked_Conversion
-----------------------
.. index:: No_Unchecked_Conversion
[RM J.13] This restriction ensures at compile time that there are no semantic
dependences on the predefined generic function Unchecked_Conversion.
No_Unchecked_Deallocation
-------------------------
.. index:: No_Unchecked_Deallocation
[RM J.13] This restriction ensures at compile time that there are no semantic
dependences on the predefined generic procedure Unchecked_Deallocation.
No_Use_Of_Entity
----------------
.. index:: No_Use_Of_Entity
......
gcc/ada/doc/gnat_rm/the_gnat_library.rst
......@@ -641,6 +641,19 @@ Provides AWK-like parsing functions, with an easy interface for parsing one
or more files containing formatted data. The file is viewed as a database
where each record is a line and a field is a data element in this line.
.. _`GNAT.Bind_Environment_(g-binenv.ads)`:
`GNAT.Bind_Environment` (:file:`g-binenv.ads`)
==============================================
.. index:: GNAT.Bind_Environment (g-binenv.ads)
.. index:: Bind environment
Provides access to key=value associations captured at bind time.
These associations can be specified using the `-V` binder command
line switch.
.. _`GNAT.Bounded_Buffers_(g-boubuf.ads)`:
`GNAT.Bounded_Buffers` (:file:`g-boubuf.ads`)
......
gcc/ada/doc/gnat_ugn/building_executable_programs_with_gnat.rst
......@@ -4911,13 +4911,12 @@ following *gcc* switches refine this default behavior.
the condition being checked is true, which can result in erroneous
execution if that assumption is wrong.
The checks subject to suppression include all the checks defined by
the Ada standard, the additional implementation defined checks
`Alignment_Check`,
`Duplicated_Tag_Check`, `Predicate_Check`, and
`Validity_Check`, as well as any checks introduced using
`pragma Check_Name`. Note that `Atomic_Synchronization`
is not automatically suppressed by use of this option.
The checks subject to suppression include all the checks defined by the Ada
standard, the additional implementation defined checks `Alignment_Check`,
`Duplicated_Tag_Check`, `Predicate_Check`, Container_Checks, Tampering_Check,
and `Validity_Check`, as well as any checks introduced using `pragma
Check_Name`. Note that `Atomic_Synchronization` is not automatically
suppressed by use of this option.
If the code depends on certain checks being active, you can use
pragma `Unsuppress` either as a configuration pragma or as
......@@ -6326,6 +6325,14 @@ be presented in subsequent sections.
:file:`stdout`.
.. index:: -V (gnatbind)
:samp:`-V{key}={value}`
Store the given association of `key` to `value` in the bind environment.
Values stored this way can be retrieved at run time using
`GNAT.Bind_Environment`.
.. index:: -w (gnatbind)
:samp:`-w{x}`
......
gcc/ada/doc/gnat_ugn/the_gnat_compilation_model.rst
......@@ -4465,7 +4465,7 @@ If you want to generate a single Ada file and not the transitive closure, you
can use instead the *-fdump-ada-spec-slim* switch.
You can optionally specify a parent unit, of which all generated units will
be children, using `-fada-spec-parent=``unit`.
be children, using `-fada-spec-parent=<unit>`.
Note that we recommend when possible to use the *g++* driver to
generate bindings, even for most C headers, since this will in general
......
gcc/ada/gnat_rm.texi
This source diff could not be displayed because it is too large. You can view the blob instead.
gcc/ada/gnat_ugn.texi
......@@ -21,7 +21,7 @@
@copying
@quotation
GNAT User's Guide for Native Platforms , May 12, 2015
GNAT User's Guide for Native Platforms , October 20, 2015
AdaCore
......@@ -6630,7 +6630,7 @@ If you want to generate a single Ada file and not the transitive closure, you
can use instead the @emph{-fdump-ada-spec-slim} switch.
You can optionally specify a parent unit, of which all generated units will
be children, using @cite{-fada-spec-parent=`@w{`}unit}.
be children, using @cite{-fada-spec-parent=<unit>}.
Note that we recommend when possible to use the @emph{g++} driver to
generate bindings, even for most C headers, since this will in general
......@@ -9130,7 +9130,7 @@ messages showing
where implicit @cite{pragma Elaborate} and @cite{pragma Elaborate_All}
are generated. This is useful in diagnosing elaboration circularities
caused by these implicit pragmas when using the static elaboration
model. See the section in this guide on elaboration checking for
model. See See the section in this guide on elaboration checking for
further details. These messages are not generated by default, and are
intended only for temporary use when debugging circularity problems.
@end table
......@@ -13601,13 +13601,11 @@ year). The compiler will generate code based on the assumption that
the condition being checked is true, which can result in erroneous
execution if that assumption is wrong.
The checks subject to suppression include all the checks defined by
the Ada standard, the additional implementation defined checks
@cite{Alignment_Check},
@cite{Duplicated_Tag_Check}, @cite{Predicate_Check}, and
@cite{Validity_Check}, as well as any checks introduced using
@cite{pragma Check_Name}. Note that @cite{Atomic_Synchronization}
is not automatically suppressed by use of this option.
The checks subject to suppression include all the checks defined by the Ada
standard, the additional implementation defined checks @cite{Alignment_Check},
@cite{Duplicated_Tag_Check}, @cite{Predicate_Check}, Container_Checks, Tampering_Check,
and @cite{Validity_Check}, as well as any checks introduced using @cite{pragma Check_Name}. Note that @cite{Atomic_Synchronization} is not automatically
suppressed by use of this option.
If the code depends on certain checks being active, you can use
pragma @cite{Unsuppress} either as a configuration pragma or as
......@@ -15425,6 +15423,14 @@ platforms. (See @ref{125,,Dynamic Stack Usage Analysis} for details.)
Verbose mode. Write error messages, header, summary output to
@code{stdout}.
@geindex -V (gnatbind)
@item @code{-V@emph{key}=@emph{value}}
Store the given association of @cite{key} to @cite{value} in the bind environment.
Values stored this way can be retrieved at run time using
@cite{GNAT.Bind_Environment}.
@geindex -w (gnatbind)
@item @code{-w@emph{x}}
......@@ -17821,7 +17827,9 @@ Whether the project is to be installed, values are @cite{true}
An array attribute to declare a set of files not part of the sources
to be installed. The array discriminant is the directory where the
file is to be installed. If a relative directory then Prefix (see
below) is prepended.
below) is prepended. Note also that if the same file name occurs
multiple time in the attribute list, the last one will be the one
installed.
@end quotation
@geindex Prefix (GNAT Project Manager)
......@@ -21139,7 +21147,7 @@ in an executable.
@item
@strong{Run_Path_Origin}: single
Value is the string that may replace the path name of the executable
Value is the the string that may replace the path name of the executable
directory in the run path options.
@item
......@@ -21256,7 +21264,7 @@ the prefix is "lib".
@item
@strong{Shared_Library_Suffix}: single
Value is the extension of the name of shared library files. When not
Value is the the extension of the name of shared library files. When not
declared, the extension is ".so".
@item
......@@ -21913,7 +21921,9 @@ Value is the directory used to generate the documentation of source code.
An array attribute to declare a set of files not part of the sources
to be installed. The array discriminant is the directory where the
file is to be installed. If a relative directory then Prefix (see
below) is prepended.
below) is prepended. Note also that if the same file name occurs
multiple time in the attribute list, the last one will be the one
installed.
@item
@strong{Prefix}: single
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment