|Languages that give "hints" to the compiler jhummel@cy4.ICS.UCI.EDU (Joe Hummel) (1994-07-18)|
|Re: Languages that give "hints" to the compiler firstname.lastname@example.org (1994-07-29)|
|Re: Languages that give "hints" to the compiler email@example.com (1994-07-19)|
|Re: Languages that give "hints" to the compiler firstname.lastname@example.org (1994-07-21)|
|Re: Languages that give "hints" to the compiler email@example.com (1994-07-31)|
|Languages that give "hints" to the compiler firstname.lastname@example.org (1994-08-01)|
|Re: Languages that give "hints" to the compiler email@example.com (1994-08-02)|
|[1 later articles]|
|From:||Joe Hummel <jhummel@cy4.ICS.UCI.EDU>|
|Keywords:||Fortran, history, question, optimize, comment|
|Organization:||UC Irvine, Department of ICS|
|Date:||Mon, 18 Jul 1994 05:39:24 GMT|
I remember a post in the last year or two that mentioned in passing some
early FORTRAN compilers that allowed hints to be passed on to the
compiler; for example, the likelihood of a branch being taken. The goal
is to allow better optimization by supplying better info to the compiler.
I couldn't track down the post, and was wondering if anyone might have
some refs to work in this area? I'm interested in approaches for allowing
the programmer to supply optimization information to the compiler.
Today, the usual approaches seem to be:
- comment statements
- command-line compiler options/switches
What other approaches have languages or compilers supported?
Thanks for any information you might be able to share. I'll post a
summary if people are interested. Cheers,
ICS Graduate Student, UC Irvine
[The original FORTRAN compiler had a FREQUENCY statement that let you give
a hint to the compiler how many times a DO loop would run or which was the
most likely branch of an IF. It disappeared in Fortran II. Legend says
that the final nail in its coffin was when someone found that it was
implemented backwards and nobody had noticed. -John]
Return to the
Search the comp.compilers archives again.