diff options
| author | Robert Dewar <dewar@gnat.com> | 2004-10-04 14:58:47 +0000 |
|---|---|---|
| committer | Arnaud Charlet <charlet@gcc.gnu.org> | 2004-10-04 16:58:47 +0200 |
| commit | 1fdebfe5fd9189af6e36d46c1b6a2733ad145bf0 (patch) | |
| tree | eee69f9476365cf2db06be3df66d76e53f8c8b30 /gcc/c-pragma.c | |
| parent | cd91501c62733d6bc51340cbbdcb6ca0b8015524 (diff) | |
| download | gcc-1fdebfe5fd9189af6e36d46c1b6a2733ad145bf0.zip gcc-1fdebfe5fd9189af6e36d46c1b6a2733ad145bf0.tar.gz gcc-1fdebfe5fd9189af6e36d46c1b6a2733ad145bf0.tar.bz2 | |
exp_ch3.adb (Needs_Simple_Initialization): Modular packed arrays no longer need to be initialized to zero.
2004-10-04 Robert Dewar <dewar@gnat.com>
* exp_ch3.adb (Needs_Simple_Initialization): Modular packed arrays no
longer need to be initialized to zero.
(Get_Simple_Init_Val): Modular packed arrays no longer need to be
initialized to zero.
* checks.adb (Expr_Known_Valid): Packed arrays are now always
considered valid, even if the representation is modular. That's correct
now that we no longer initialize packed modular arrays to zero.
* exp_dbug.ads: Clarify documentation on handling of PAD and JM
suffixes. These are now documented as the only cases in which the
debugger ignores outer records.
Previously, the spec allowed arbitrary suffixes for this purpose.
Change name of LJM to JM for packed array pad records
Create separate section on packed array handling, and add a whole new
set of comments to this section describing the situation with packed
modular types and justification requirements depending on endianness.
From-SVN: r88500
Diffstat (limited to 'gcc/c-pragma.c')
0 files changed, 0 insertions, 0 deletions