|Re: Are 64 Int or FP registers useful? email@example.com (1992-09-14)|
|Re: Are 64 Int or FP registers useful? firstname.lastname@example.org (1992-09-16)|
|Re: Are 64 Int or FP registers useful? email@example.com (1992-09-17)|
|Re: Are 64 Int or FP registers useful? firstname.lastname@example.org (Dave Gillespie) (1992-09-17)|
|Re: Are 64 Int or FP registers useful? email@example.com (1992-09-17)|
|Re: Are 64 Int or FP registers useful? firstname.lastname@example.org (1992-09-19)|
|From:||email@example.com (Larry Meadows)|
|Organization:||The Portland Group, Portland, OR|
|Date:||Sat, 19 Sep 1992 14:39:54 GMT|
Dave Gillespie <firstname.lastname@example.org> writes:
>On the other hand, I've never seen a compiler that could really take
>advantage of the 860's pipelining; our inner loops are all hand-coded.
>860 optimizers tend to be essentially vectorizing compilers, where the
>"vector instructions" are hand-coded assembly language routines.
Actually, our i860 compiler generates software pipelined code for the inner
loop, unless we happen to have a hand-code routine that matches the
inner loop. So, for example, a vector add will be matched, but some
complicated collection of adds and multiplies will be software
pipelined. On many codes it works quite well, although I'd be the first
to admit that hand code usually does better. A lot of the problem
is in communicating dependence information from the user to the compiler.
Larry Meadows The Portland Group
Return to the
Search the comp.compilers archives again.