Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.compilers > #1260
| From | Ivan Godard <ivan@ootbcomp.com> |
|---|---|
| Newsgroups | comp.compilers |
| Subject | Re: optimizing compilers for low power design |
| Date | 2014-06-15 11:19 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <14-06-005@comp.compilers> (permalink) |
| References | <14-06-003@comp.compilers> <14-06-004@comp.compilers> |
On 6/15/2014 8:43 AM, Kaz Kylheku wrote: > On 2014-06-15, idatarm@gmail.com <idatarm@gmail.com> wrote: >> Abstract: We describe an algorithm for optimizing compilers for low >> power design. The algorithm can be applied to almost any c compiler >> and in particular we target gcc compiler. The algorithm works by >> modifying optimization table lookup of gcc. This works in theory. We > <snip> < An excellent critique omitted. > Only one addition: the amount of active power (switching gates) and the amount of passive power (leakage) varies by fab process, but as a rule the proportion of the passive part increases with smaller feature sizes. Smaller than roughly the 28nm node, actual execution of ops increasingly comes for free. However, leakage is (roughly) proportional to area or equivalently, gate count), so by far the greatest power saving available derives from reducing area/count for a given amount of computation. In a modern OOO chip, the great bulk of the area/count is devoted to figuring out what you are going to do next, getting everything ready to do it, and then dealing which what you have done. The amount spent in actually doing it (in an adder, for example) is near trivial. So changing op A into op B doesn't win anything, because the hardware surrounding A or B dominates the power, and even if B uses less active power than A the hardware to do A is still there leaking away. This is why so much has shifted to in-order architectures: they have much less area/power required around the functional units. The problem with them is that they cannot achieve the ILP of an OOO architecture; all that cruft around the adders really does do something, it's just expensive. Exchanging ops won't help; you have to do something architectural, like our Mill, to get the ILP of OOO and the area/power of a DSP. Ivan [Are we on the verge of reinventing VLIW? -John]
Back to comp.compilers | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
optimizing compilers for low power design idatarm@gmail.com - 2014-06-15 05:20 -0700
Re: optimizing compilers for low power design Kaz Kylheku <kaz@kylheku.com> - 2014-06-15 15:43 +0000
Re: optimizing compilers for low power design Ivan Godard <ivan@ootbcomp.com> - 2014-06-15 11:19 -0700
Re: optimizing compilers for low power design <Pidgeot18@verizon.com.invalid> - 2014-06-15 18:58 -0500
Re: optimizing compilers for low power design "Derek M. Jones" <derek@_NOSPAM_knosof.co.uk> - 2014-06-16 12:11 +0100
Re: optimizing compilers for low power design George Neuner <gneuner2@comcast.net> - 2014-06-18 04:44 -0400
Re: optimizing compilers for low power design glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2014-06-20 18:13 +0000
Re: optimizing compilers for low power design Ivan Godard <ivan@ootbcomp.com> - 2014-06-20 11:52 -0700
Re: optimizing compilers for low power design Gene Wirchenko <genew@telus.net> - 2014-06-20 12:16 -0700
Re: optimizing compilers for low power design George Neuner <gneuner2@comcast.net> - 2014-06-20 17:24 -0400
Re: optimizing compilers for low power design Walter Banks <walter@bytecraft.com> - 2014-06-16 13:30 -0400
Re: optimizing compilers for low power design andrewchamberss@gmail.com - 2014-06-20 05:03 -0700
csiph-web