Re: What's more important optimisations or debugging?
- From: Hans-Bernhard Bröker <HBBroeker@xxxxxxxxxxx>
- Date: Thu, 31 May 2007 21:18:23 +0200
David Brown wrote:
Remember Knuth's golden rules about optimisation:
1. Don't do it.
2. (For experts only) Don't do it yet.
I remember there being a third:
3. Before you do it, measure.
That applies to hand-tuning of the source code, rather than automatic optimisations in a compiler, but it's important to remember that the speed of the code is irrelevant if it does not work.
While that latter statement applies rather widely, let's keep in mind that this is the embedded programming newsgroup after all, where real-time constraints are a regular old fact of life. That means speed and correctness may not be separable just like that. Sometimes, if code is slow, that alone means it does not work.
.
- References:
- What's more important optimisations or debugging?
- From: rhapgood
- Re: What's more important optimisations or debugging?
- From: Dave Hansen
- Re: What's more important optimisations or debugging?
- From: David Brown
- What's more important optimisations or debugging?
- Prev by Date: Re: What's more important optimisations or debugging?
- Next by Date: Re: an interesting CAN driver issue
- Previous by thread: Re: What's more important optimisations or debugging?
- Next by thread: Re: What's more important optimisations or debugging?
- Index(es):
Relevant Pages
|