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-Thread: 103376,6609c40f81b32989 X-Google-NewGroupId: yes X-Google-Thread: 1094ba,9bdec20bcc7f3687 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,gid8d3408f8c3,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx02.iad01.newshosting.com!newshosting.com!83.128.0.11.MISMATCH!news-out1.kabelfoon.nl!newsfeed.kabelfoon.nl!bandi.nntp.kabelfoon.nl!feeder.news-service.com!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!gegeweb.org!aioe.org!not-for-mail From: glen herrmannsfeldt Newsgroups: comp.lang.ada,comp.lang.fortran,comp.lang.pl1 Subject: Re: Why is Ada considered "too specialized" for scientific use Date: Tue, 8 Jun 2010 12:03:45 +0000 (UTC) Organization: Aioe.org NNTP Server Message-ID: References: <4bbb5386$0$56422$c30e37c6@exi-reader.telstra.net> <4bbdf5c6$1$fuzhry+tra$mr2ice@news.patriot.net> <4c0a2e36$0$34205$c30e37c6@exi-reader.telstra.net> <4c0b234f$1$fuzhry+tra$mr2ice@news.patriot.net> <7plPn.6395$z%6.5719@edtnps83> NNTP-Posting-Host: iv0FLp+Uhvv05NzXKWDP0Q.user.speranza.aioe.org X-Complaints-To: abuse@aioe.org User-Agent: tin/1.9.3-20080506 ("Dalintober") (UNIX) (Linux/2.6.26-2-686 (i686)) X-Notice: Filtered by postfilter v. 0.8.2 Xref: g2news1.google.com comp.lang.ada:11475 comp.lang.fortran:24192 comp.lang.pl1:1430 Date: 2010-06-08T12:03:45+00:00 List-Id: In comp.lang.fortran James J. Weinkam wrote: > Your point is well taken for machines of the 60's and 70's, > at least for the IBM ones with which I am most familiar. > For example in 360 assembler, if you wanted to add two numbers > you had your choice of A, AR, AH, AP, AL, ALR, AE, AER, AD, > ADR, AXR, AU, AUR, AW, AWR and maybe a few more that I have > forgotten. There was a one-to-one correspondence between each > of these mnemonics and their corresponding numerical op codes. > The assembly language programmer had to choose the correct > mnemonic instruction to suit the circumstances. (snip) And note that the hex value for the opcode for many of those add instructions has A for its low digit. Also, the divide instructions have D for their low hex digit. Subtract and multiply come in between, with B and C. Starting with S/370, some instructions have a two byte opcode. There are now even more add instructions with 64 bit operations in z/Architecture, AGR, AGFR, AY, AG, AGF, add logical with carry ALCR, ALCGR, ALC, ALCG, IEEE binary floating point operations AEBR, ADBR, and AXBR, and finally decimal floating point instructions ADTR and AXTR. -- glen