🚀 go-pugleaf

In article <4614@pt.cs.cmu.edu> schmitz@fas.ri.cmu.edu (Donald Schmitz) writes:
>In article david@sun.com  writes:
>>In article sclafani@jumbo.dec.com (Michael Sclafani) writes:
>>>Results for the Sun-3/60 are not reported because the data in
>>>[Presentation on Benchmarks given at Sun User Group Conference, Dec 5-7,
>>>1988 by Sun Microsystems, Inc.] uses compiler optimization level 4 which
>>>employs procedure inlining.
>>
>>FYI, this is incorrect.  Current Sun C compilers do not perform procedure
>>inlining at any optimization level.
>>
>>David DiGiacomo, Sun Microsystems, Mt. View, CA  sun!david david@sun.com
>

>Maybe you should look again -  our SUN3 C ....
>occasionally useful procedure inline facility - and the standard inline
>files have 1986 SUN copywrite notices in them.  Its actually pretty crude,
>you compile the source with a .il file (assembly code with a few special
>directives), and all of the original jsr's are macro replaced with the
>assembler for the routine.  It doesn't inline argument passing, but it does
>eliminate the jsr/rts overhead.
>

For the record......

-O4 has nothing to do with inlining (in any product currently released).

/usr/lib/f77/libm.il 
/usr/lib/libm.il

exist for cc and f77 on ALL sun platforms. The names vary a bit to
account for hardware (e.g. /usr/lib/f77/f68881 means use the f77
inline library for 68881 instructions).

Cheers.




Keith H. Bierman
It's Not My Fault ---- I Voted for Bill & Opus