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=unavailable autolearn_force=no version=3.4.4 Newsgroups: comp.lang.ada Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!engin.umich.edu!warack From: warack@engin.umich.edu (Christopher Warack) Subject: Summary of Diana Status Message-ID: <1991Apr8.163413.7071@engin.umich.edu> Summary: At least three compiler manufacturers use it... Keywords: Ada, Diana, Compilers Sender: news@engin.umich.edu (CAEN Netnews) Organization: University of Michigan Engineering, Ann Arbor Date: Mon, 8 Apr 1991 16:34:13 GMT List-Id: Here's the summary of what I learned about Diana. I got several request to post this. I'm still interested in a pointer to the latest Diana definition. jls mentioned a Tartan document about 5 years old. Anyone know an exact reference and how to get it? The version I have is somewhat older (~'83). Does someone at the AJPO know? Thanks again to everyone that responded. - Chris SUMMARY FOLLOWS: vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv From: jls@rational.Rational.COM The standard we use is the one from Tartan. I think it is about 5 years old. Original-msg: ________________________________ Thanks for the response. This is pretty much what I thought... In article you write: >>What is the latest version? >>Where can you get the documentation for that version? > >Hard to say. I believe the draft standard was never formally adopted >by a standards body, and has sort of sat around for several years. >We adhered quite closely to the standard, but there are areas where >we diverged: so much for the dream of a common APSE core, huh? me>Do you guys have a definition available that I could get my hands on? me>By the 'draft standard' do you mean the '83 version that showed up in me>Lecture Notes for Comp Sci #161 or something else? >>Is anybody using it for tools other than compilers? > >We use it for code analysis tools, PDL, hyper-code traversal, and >a number of other things. >>Has anyone added object code attributes or somehow represented optimizations? > >We decorate the tree with code segments and other compiler information >not specified in the original standard. >From carlisle@eng.auburn.edu Fri Mar 29 16:21:50 1991 We're using it here at Auburn - via a VERDIX/ADA tool to get at the net (which apparently they use in their compiler). I would be interested in finding out what you find out about others who are using it. Thanks. From: ryer@inmet.inmet.com Intermetrics compilers use DIANA. Our DIANA has some locally defined extensions and representation tricks. The interface is open. We have provided it to other developers. Currently, General Research Corp's "Ada Test and Verification System (ATVS)" is the only commercially available product from another company that is based on our DIANA. GRC has also developed an "Expert Avionics Code Modification" system that uses our DIANA as a database. Intermetrics uses DIANA as the IL for code generation, for our AdaView symbolic debugger, and our Byron PDL tool. Mike Ryer From: ryer@inmet.inmet.com (Mike Ryer) DIANA is not an easy thing to send -- we represent it as a disk-resident structure with associated paging/long-pointer machinery. It is defined in IDL (which we have also extended), and the dereference/paging routines are automatically generated (except the assembly language part). The Ada specification part that gets plugged into the rest of the compiler is a single Ada package containing one variant record declaration about 10,000 lines long. The interface is open, but it is not at all simple -- it usually takes a bit of training time on our part to get a new DIANA user up to speed. Code generation is just "maximal munch" (Cattell/CMU, about 1976), with no special smarts in the DIANA -- in fact we generate a lower-lever (level) IL from DIANA before generating machine code. -- Christopher A. Warack warack@eecs.umich.edu Graduate Dept, EECS (313) 665-4789 University of Michigan