Re: Compilers producing assembly language

haddock!csun!aeusesef (Sean Eric Fagan)
6 Dec 87 15:08:39 PST (Sun)

          From comp.compilers

Related articles
Compilers producing assembly language uiucdcs!gatech!emory!arnold (1987-11-24)
Re: Compilers producing assembly language harvard!drilex!dricej (1987-11-29)
Re: Compilers producing assembly language allegra!utzoo!henry (1987-12-03)
Re: Compilers producing assembly language gla@nixpbe.UUCP (1987-12-02)
Re: Compilers producing assembly language haddock!csun!aeusesef (1987-12-06)
Re: Compilers producing assembly language atbowler@orchid.waterloo.edu (1987-12-09)
Re: Compilers producing assembly language rcd@ico.isc.COM (1987-12-10)
Re: Compilers producing assembly language rcodi@yabbie.rmit.oz.au (1987-12-14)
| List of all articles for this month |

Newsgroups: comp.compilers
References: <767@ima.ISC.COM>
From: haddock!csun!aeusesef (Sean Eric Fagan)
Organization: California State University, Northridge
Keywords: CDC ftn etc.
Date: 6 Dec 87 15:08:39 PST (Sun)

In article <767@ima.ISC.COM> harvard!drilex!dricej writes:
>The only other compiler which I have heard of which generates intermediate
>assembler was the CDC FTN compiler. ...


NO! The CDC fortran compiler can generate assembly OUTPUT if you wish (sort
of like the -S option for cc), but it internally generates an intermediate
language, than has the Common Code Generator turn that directly into binary
code. Also, you could have a routine be in assembly by just using the
COMPASS mnemonics (i.e., have 'IDENT' in column 11); ftn is smart enough to
realize that you are using assembly and call the assembler.
My experience with this is about 45 seconds old; I just got off of a CDC
Cyber 170/750.


  Sean Eric Fagan Office of Computing/Communications Resources
  (213) 852 5742 Suite 2600
  1GTLSEF@CALSTATE.BITNET 5670 Wilshire Boulevard
                                                    Los Angeles, CA 90036
{litvax, rdlvax, psivax, hplabs, ihnp4}!csun!aeusesef
[So how fast is the compiler?]
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.