mirror of
git://gcc.gnu.org/git/gcc.git
synced 2025-03-25 10:20:43 +08:00
exp_ch6.adb: Minor reformatting.
2010-06-18 Robert Dewar <dewar@adacore.com> * exp_ch6.adb: Minor reformatting. * gnatname.adb: Add comment. From-SVN: r160996
This commit is contained in:
parent
9c8ff9b97d
commit
8a45b58c5d
@ -1,3 +1,8 @@
|
||||
2010-06-18 Robert Dewar <dewar@adacore.com>
|
||||
|
||||
* exp_ch6.adb: Minor reformatting.
|
||||
* gnatname.adb: Add comment.
|
||||
|
||||
2010-06-18 Vincent Celier <celier@adacore.com>
|
||||
|
||||
* gnatname.adb (Scan_Args): When --and is used, make sure that the
|
||||
|
@ -3720,13 +3720,12 @@ package body Exp_Ch6 is
|
||||
if Nkind (Orig_Bod) = N_Defining_Identifier
|
||||
or else Nkind (Orig_Bod) = N_Defining_Operator_Symbol
|
||||
then
|
||||
-- Subprogram is a renaming_as_body. Calls appearing after the
|
||||
-- renaming can be replaced with calls to the renamed entity
|
||||
-- directly, because the subprograms are subtype conformant. If
|
||||
-- the renamed subprogram is an inherited operation, we must redo
|
||||
-- the expansion because implicit conversions may be needed.
|
||||
-- Similarly, if the renamed entity is inlined, expand the call
|
||||
-- for further optimizations.
|
||||
-- Subprogram is renaming_as_body. Calls occurring after the renaming
|
||||
-- can be replaced with calls to the renamed entity directly, because
|
||||
-- the subprograms are subtype conformant. If the renamed subprogram
|
||||
-- is an inherited operation, we must redo the expansion because
|
||||
-- implicit conversions may be needed. Similarly, if the renamed
|
||||
-- entity is inlined, expand the call for further optimizations.
|
||||
|
||||
Set_Name (N, New_Occurrence_Of (Orig_Bod, Loc));
|
||||
|
||||
|
@ -309,9 +309,13 @@ procedure Gnatname is
|
||||
declare
|
||||
New_Arguments : Argument_Data;
|
||||
pragma Warnings (Off, New_Arguments);
|
||||
-- Declaring this defaulted itialized object ensures that
|
||||
-- the new allocated component of table Arguments is
|
||||
-- correctly initialized.
|
||||
-- Declaring this defaulted initialized object ensures
|
||||
-- that the new allocated component of table Arguments
|
||||
-- is correctly initialized.
|
||||
|
||||
-- This is VERY ugly, Table should never be used with
|
||||
-- data requiring default initialization. We should
|
||||
-- find a way to avoid violating this rule ???
|
||||
|
||||
begin
|
||||
Arguments.Append (New_Arguments);
|
||||
|
Loading…
x
Reference in New Issue
Block a user