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 04:39:38 PST Path: supernews.google.com!sn-xit-02!supernews.com!news.gv.tsc.tdk.com!falcon.america.net!sunqbc.risq.qc.ca!feeder.qis.net!feed2.onemain.com!feed1.onemain.com!cyclone-sf.pbi.net!206.13.28.143!news.pacbell.net.POSTED!not-for-mail From: David Kristola Organization: heaps of stacks MIME-Version: 1.0 User-Agent: Hogwasher 2.0 (Macintosh) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <01HW.B6D89A42000E27BC06E1A95C@news.pacbell.net> Subject: Re: Code Generation Question Newsgroups: comp.lang.ada References: <98ug7e$9oj$1@newpoisson.nosc.mil> <87elvw4pdl.fsf@deneb.enyo.de> Date: Sat, 17 Mar 2001 4:36:18 -0800 NNTP-Posting-Host: 63.194.212.92 X-Complaints-To: abuse@pacbell.net X-Trace: news.pacbell.net 984832566 63.194.212.92 (Sat, 17 Mar 2001 04:36:06 PST) NNTP-Posting-Date: Sat, 17 Mar 2001 04:36:06 PST Xref: supernews.google.com comp.lang.ada:5800 Date: 2001-03-17T04:36:18-08:00 List-Id: On Sat, 17 Mar 2001 3:16:22 -0800, Florian Weimer wrote (in message <87elvw4pdl.fsf@deneb.enyo.de>): > 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. > > Using machine code insertions is another possibility. Combine this (machine code insertions) with Jeff Creem's answer, and you will have (IMHO) the best solution. Since you are working with picky hardware, use the power of machine code insertion to insure the access operations you need. Isolate this in a package for easy maintenance and to help portability (since this part probably isn't portable anyway, but that's okay, it is isolated, and it is meant to work with a particular card in your PowerPC VME system). -- --djk, keeper of arcane lore & trivial fluff Home: David95036 plus 1 at america on-line Spam: goto.hades@welovespam.com