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,5a51ee2b8ee36d5f
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-03-17 03:18:08 PST
Path: 
 supernews.google.com!sn-xit-03!supernews.com!freenix!fr.clara.net!heighliner.fr.clara.net!newsfeed.germany.net!newsfeed2.easynews.net!easynews.net!news.cid.net!news.enyo.de!news1.enyo.de!not-for-mail
From: Florian Weimer <fw@deneb.enyo.de>
Newsgroups: comp.lang.ada
Subject: Re: Code Generation Question
Date: 17 Mar 2001 12:16:22 +0100
Organization: Enyo's not your organization
Message-ID: <87elvw4pdl.fsf@deneb.enyo.de>
References: <98ug7e$9oj$1@newpoisson.nosc.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Xref: supernews.google.com comp.lang.ada:5797
Date: 2001-03-17T12:16:22+01:00
List-Id: <comp.lang.ada>

claveman@cod.nosc.mil (Charles H. Sampson) writes:

>      This causes quite a bit of problem, as you might guess when you re-
> flect on it for a minute.  Whenever the module is modified (fortunately,
> it's now pretty stable), we have to investigate the code generated by
> the compiler to verify that there are no byte reads or writes to the
> board's memory.  If there are, we have to figure out a way to trick the
> compiler into not doing it.

You might want to ask the compiler vendor to provide a pragma to force
the compiler to generate the appropriate read/write instructions.

Using machine code insertions is another possibility.