diff options
| author | Pierre-Marie de Rodat <pmderodat@gcc.gnu.org> | 2017-12-15 11:16:14 +0000 |
|---|---|---|
| committer | Pierre-Marie de Rodat <pmderodat@gcc.gnu.org> | 2017-12-15 11:16:14 +0000 |
| commit | b3801819f495f925bc7c26f03e4e98f448423839 (patch) | |
| tree | 05bbd4a2275dcfa45bede507f65507549a26bbb8 /gcc/ada/doc | |
| parent | fe663f3750d37cc7edacd07caf5872d18f04889f (diff) | |
| download | gcc-b3801819f495f925bc7c26f03e4e98f448423839.zip gcc-b3801819f495f925bc7c26f03e4e98f448423839.tar.gz gcc-b3801819f495f925bc7c26f03e4e98f448423839.tar.bz2 | |
gnat_and_program_execution.rst: Update section "Dynamic Stack Usage Analysis" to include more details about...
gcc/ada/
2017-12-15 Patrick Bernardi <bernardi@adacore.com>
* doc/gnat_ugn/gnat_and_program_execution.rst: Update section "Dynamic
Stack Usage Analysis" to include more details about GNAT_STACK_LIMIT.
2017-12-15 Hristian Kirtchev <kirtchev@adacore.com>
* exp_util.adb (Add_Own_DIC): Ensure that the expression of the pragma
is available (Is_Verifiable_DIC_Pragma): Moved from Sem_Util.
* sem_util.adb (Has_Full_Default_Initialization):
Has_Fully_Default_Initializing_DIC_Pragma is now used to determine
whether a type has full default initialization due to pragma
Default_Initial_Condition.
(Has_Fully_Default_Initializing_DIC_Pragma): New routine.
(Is_Verifiable_DIC_Pragma): Moved to Exp_Util.
* sem_util.ads (Has_Fully_Default_Initializing_DIC_Pragma): New
routine.
(Is_Verifiable_DIC_Pragma): Moved to Exp_Util.
* sem_warn.adb (Is_OK_Fully_Initialized):
Has_Fully_Default_Initializing_DIC_Pragma is now used to determine
whether a type has full default initialization due to pragma
Default_Initial_Condition.
2017-12-15 Hristian Kirtchev <kirtchev@adacore.com>
* sem_prag.adb (Match_Constituent): Do not quietly accept constants as
suitable constituents.
* exp_util.adb: Minor reformatting.
2017-12-15 Ed Schonberg <schonberg@adacore.com>
* exp_aggr.adb (In_Place_Assign_OK): Extend the predicate to recognize
an array aggregate in an allocator, when the designated type is
unconstrained and the upper bound of the aggregate belongs to the base
type of the index.
2017-12-15 Bob Duff <duff@adacore.com>
* exp_ch6.adb (Expand_N_Extended_Return_Statement,
Expand_Simple_Function_Return): Assert that the b-i-p-ness of the
caller and callee match. Otherwise, we would need some substantial
changes to allow b-i-p calls non-b-i-p, and vice versa.
gcc/testsuite/
2017-12-15 Hristian Kirtchev <kirtchev@adacore.com>
* gnat.dg/dflt_init_cond.adb, gnat.dg/dflt_init_cond_pkg.ads: New
testcase.
From-SVN: r255685
Diffstat (limited to 'gcc/ada/doc')
| -rw-r--r-- | gcc/ada/doc/gnat_ugn/gnat_and_program_execution.rst | 15 |
1 files changed, 12 insertions, 3 deletions
diff --git a/gcc/ada/doc/gnat_ugn/gnat_and_program_execution.rst b/gcc/ada/doc/gnat_ugn/gnat_and_program_execution.rst index e350cb9..6ce22f4 100644 --- a/gcc/ada/doc/gnat_ugn/gnat_and_program_execution.rst +++ b/gcc/ada/doc/gnat_ugn/gnat_and_program_execution.rst @@ -3817,11 +3817,20 @@ where: is not entirely analyzed, and it's not possible to know exactly how much has actually been used. -The environment task stack, e.g., the stack that contains the main unit, is -only processed when the environment variable GNAT_STACK_LIMIT is set. +By default the environment task stack, the stack that contains the main unit, +is not processed. To enable processing of the environment task stack, the +environment variable GNAT_STACK_LIMIT needs to be set to the maximum size of +the environment task stack. This amount is given in kilobytes. For example: + + :: + + $ set GNAT_STACK_LIMIT 1600 + +would specify to the analyzer that the environment task stack has a limit +of 1.6 megabytes. Any stack usage beyond this will be ignored by the analysis. The package ``GNAT.Task_Stack_Usage`` provides facilities to get -stack usage reports at run-time. See its body for the details. +stack-usage reports at run time. See its body for the details. |