Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!spool.mu.edu!munnari.oz.au!metro!tplrd!keithh
From: keithh@tplrd.tpl.oz.au (Keith Harwood)
Newsgroups: comp.arch
Subject: Re: Optimising C compiler question
Summary: It's been done.
Message-ID: <1991Apr23.010727.2123@tplrd.tpl.oz.au>
Date: 23 Apr 91 01:07:27 GMT
References: <1991Apr15.134417.24380@bigsur.uucp> <9537@cognos.UUCP> <kcollins.671991559@convex.convex.com>
Sender: keithh@tplrd.tpl.oz.au
Distribution: comp
Organization: Telectronics Pacing Systems
Lines: 9

In article <kcollins.671991559@convex.convex.com> kcollins@convex.com (Kirby L. Collins) writes:
>Rather than provide a means for the programmer to "hand optimize" register
>allocation, a more useful solution would be to give the programmer a way
>to inform the compiler about branch frequency.

The FORTRAN II (sorry about the F... word) circa 1959 had the FREQUENCY
statement for exactly that purpose.

Keith Harwood.