From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8247c32bb1260c74 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-04-22 15:25:44 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn13feed!wn12feed!wn14feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!rwcrnsc51.ops.asp.att.net.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: Q re pack & aliased References: X-Newsreader: Tom's custom newsreader Message-ID: NNTP-Posting-Host: 12.234.13.56 X-Complaints-To: abuse@attbi.com X-Trace: rwcrnsc51.ops.asp.att.net 1051050343 12.234.13.56 (Tue, 22 Apr 2003 22:25:43 GMT) NNTP-Posting-Date: Tue, 22 Apr 2003 22:25:43 GMT Organization: AT&T Broadband Date: Tue, 22 Apr 2003 22:25:43 GMT Xref: archiver1.google.com comp.lang.ada:36379 Date: 2003-04-22T22:25:43+00:00 List-Id: >Seems like the old and new behavior are the same. In both versions, the >compiler refuses to pack aliased 24-bit components. Or did I >misunderstand the ealier posting? 3.15p (& 3.16a) refuses to pack. It generates a warning and then ignores the pragma pack. Replacing pragma pack with "'component_size use 24" causes a fatal compilation error. Prior to 3.15, it packed automatically without being asked (the components have for xxx'size use 24, which I thought suggests that I want them to be 24, not 32, bits.). Janus similarly automatically packs. I tried it on OA 7.2.2 where pragma pack is silently ignored, but 'component_size is properly obeyed without complaint. >But it's not fine to make X.all slow even when X points to a component >of an unpacked array, or into the heap. It's even less fine to make the program no longer run. Something about "make it work right, then worry about speed" ;) The original question was "How can I get around this limitation." System.Address_To_Access_Conversions comes to mind, but seems awfully heavy handed. Compiling with no optimization makes no difference.