Re: C code .vs. Assembly code for Microcontrollers/DSPs ?

Stefan Monnier <stefan.monnier@lia.di.epfl.ch>
21 Mar 1996 23:41:46 -0500

          From comp.compilers

Related articles
[30 earlier articles]
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? stefan.monnier@lia.di.epfl.ch (Stefan Monnier) (1996-03-16)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? albaugh@agames.com (1996-03-16)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? preston@cs.rice.edu (1996-03-17)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? elvey@hal.com (1996-03-17)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? john.gilliver@gecm.com (1996-03-20)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? leichter@smarts.com (Jerry Leichter) (1996-03-21)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? stefan.monnier@lia.di.epfl.ch (Stefan Monnier) (1996-03-21)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? cdg@nullstone.com (1996-03-21)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? pdonovan@netcom.com (1996-03-21)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? fjh@cs.mu.OZ.AU (1996-03-21)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? cliffc@ami.sps.mot.com (1996-03-21)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? schwarz@mips.complang.tuwien.ac.at (1996-03-22)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? jfc@mit.edu (1996-03-22)
[13 later articles]
| List of all articles for this month |

From: Stefan Monnier <stefan.monnier@lia.di.epfl.ch>
Newsgroups: comp.compilers
Date: 21 Mar 1996 23:41:46 -0500
Organization: Ecole Polytechnique Federale de Lausanne
References: 96-03-006 96-03-091 96-03-106
Keywords: C, optimize
Originator: monnier@lia.di.epfl.ch (Stefan Monnier)

Christopher Glaeser <cdg@nullstone.com> wrote:
] 2) static - Static can cause significant performance problems for many
] C compilers. In particular, few C compilers can keep static variables
] in registers over a region of code. This is most notable when using


I see "static" as an alternative to global or "extern" rather than to
"auto" variables. In this sense static will not make things worse. It
might even make things better since the compiler can then do
interprocedural analysis with full information.




                Stefan


--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.