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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2203a21a136b39cc X-Google-Attributes: gid103376,public From: kilgallen@eisner.decus.org (Larry Kilgallen) Subject: Re: Fortran's Equivalence Date: 1997/03/26 Message-ID: <1997Mar26.113448.1@eisner>#1/1 X-Deja-AN: 228545138 X-Nntp-Posting-Host: eisner.decus.org References: <333840D1.7B12@cae.ca> <5hbcdn$i1h@top.mitre.org> X-Nntp-Posting-User: KILGALLEN X-Trace: 859394091/24103 Organization: LJK Software Newsgroups: comp.lang.ada Date: 1997-03-26T00:00:00+00:00 List-Id: In article <5hbcdn$i1h@top.mitre.org>, mfb@mbunix.mitre.org (Michael F Brenner) writes: > manner. Had it done so, then about half of all bit field applications > would have been portable using address overlays. As it is, true > portability (without a changing global flag telling where bit one is), is > difficult to accomplish without using specific operations (like SHIFT), > which have effects on performance (both speed and logically overspecified > algorithms). But each compiler knows which end is up and has enough information to optimize away shifts done only for the sake of addressing this issue. For instance, many machines have a more efficient set of instructions for testing bit 3 (from whichever end) without actually shifting it to the end of a register. Larry Kilgallen