Article View: comp.sys.mac.programmer.help
Article #60Re: [Altivec Newbie] optimizing current code?
From: Ian Ollmann
Date: Thu, 18 Jan 2001 21:49
Date: Thu, 18 Jan 2001 21:49
25 lines
2476 bytes
2476 bytes
On 18 Jan 2001, Dave Howell wrote: > > > Personally, I try to keep things to one AltiVec instruction per line. > > > It helps me optimize later, but there's no reason you have to do it > > > that way. > > > > CodeWarrior does a reasonable job at scheduling if you write in C, so I am > > curious how keeping things one per line helps you optimize. > > Ian, you misunderstood. He didn't say it helps CodeWarrior to optimize, > but that it helped HIM to optimize. If your code is written one > instruction per line, it's easier from an editing standpoint to reorder > operations later, than if you have to edit complex vector expressions. I understood perfectly. Reordering the instructions line by line by hand doesn't do much if Codewarrior is doing the scheduling for you. It will rearrange them right back the way it wants them in my experience. I guess he could turn scheduling off, but goodness that wouldn't help the rest of the program much. Ian --------------------------------------------------- Ian Ollmann, Ph.D. iano@cco.caltech.edu ---------------------------------------------------
Technical Details
Message-ID:
<Pine.SGI.4.30.0101181348290.42035-100000@helix2.caltech.edu>Path:
arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!news.gv.tsc.tdk.com!falcon.america.net!sunqbc.risq.qc.ca!logbridge.uoregon.edu!nntp-server.caltech.edu!helix2.caltech.edu!ianoReferences:
<943r3l$hn2$1@nnrp1.deja.com> <170120011731277716%dcardani@buena.spamfree.com> <Pine.SGI.4.30.0101171735050.41019-100000@helix2.caltech.edu> <180120010242044690%dave@noreturnaddress.nulldev>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 101ec9,a6671d8e4f3ed02f X-Google-Attributes: gid101ec9,public X-Google-Thread: 10bcce,a6671d8e4f3ed02f X-Google-Attributes: gid10bcce,public X-Google-Thread: f635e,a6671d8e4f3ed02f X-Google-Attributes: gidf635e,public X-Google-ArrivalTime: 2001-01-18 13:43:53 PST Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!news.gv.tsc.tdk.com!falcon.america.net!sunqbc.risq.qc.ca!logbridge.uoregon.edu!nntp-server.caltech.edu!helix2.caltech.edu!iano From: Ian Ollmann <iano@cco.caltech.edu> Newsgroups: comp.sys.mac.programmer.help,comp.sys.mac.programmer.codewarrior,codewarrior.mac Subject: Re: [Altivec Newbie] optimizing current code? Date: Thu, 18 Jan 2001 13:49:50 -0800 Organization: California Institute of Technology, Pasadena Lines: 26 Message-ID: <Pine.SGI.4.30.0101181348290.42035-100000@helix2.caltech.edu> References: <943r3l$hn2$1@nnrp1.deja.com> <170120011731277716%dcardani@buena.spamfree.com> <Pine.SGI.4.30.0101171735050.41019-100000@helix2.caltech.edu> <180120010242044690%dave@noreturnaddress.nulldev> NNTP-Posting-Host: helix2.caltech.edu Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: <iano@helix2.caltech.edu> To: Dave Howell <dave@noreturnaddress.nulldev> In-Reply-To: <180120010242044690%dave@noreturnaddress.nulldev>