Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!bunda
From: bunda@cs.utexas.edu (John Bunda)
Newsgroups: gnu.gcc
Subject: Re: Porting gcc to the new Sun SPARCstation 1 and SPARCstation 300 series
Summary: working on it
Message-ID: <5441@cs.utexas.edu>
Date: 3 May 89 05:30:55 GMT
References: <8905030323.AA27122@jato.Jpl.Nasa.Gov>
Distribution: gnu
Organization: U. Texas CS Dept., Austin, Texas
Lines: 16

In article <8905030323.AA27122@jato.Jpl.Nasa.Gov>, earle@JATO.JPL.NASA.GOV (Greg Earle - Sun Software Support) writes:

> [is it possible to modify gcc to avoid back-to-back writes?]

I have been working on scheduling code to allow gcc to reorder
instructions to deal with this problem in general, but that
doesn't help at the moment.  Short of hacking gcc proper,
it *might* be possible to catch some cases with peepholes in
the machine description, but this would not be a complete
(or satisfying) solution.

-John
-- 
...................................
John Bunda            UT CS Dept.      
bunda@cs.utexas.edu   Austin, Texas