Related articles |
---|
[10 earlier articles] |
Re: Justifying Optimization jvorbrueggen@mediasec.de (Jan C.=?iso-8859-1?Q?Vorbr=FCggen?=) (2003-01-25) |
Re: Justifying Optimization joachim_d@gmx.de (Joachim Durchholz) (2003-01-26) |
Re: Justifying Optimization lars@bearnip.com (2003-01-26) |
Re: Justifying Optimization cgweav@aol.com (2003-01-29) |
Re: Justifying Optimization tmk@netvision.net.il (2003-01-30) |
Re: Justifying Optimization lex@cc.gatech.edu (Lex Spoon) (2003-02-05) |
Re: Justifying Optimization bobduff@shell01.TheWorld.com (Robert A Duff) (2003-02-05) |
Re: Justifying Optimization vbdis@aol.com (2003-02-06) |
Re: Justifying Optimization vbdis@aol.com (2003-02-06) |
Re: Justifying Optimization joachim_d@gmx.de (Joachim Durchholz) (2003-02-11) |
Re: Justifying Optimization joachim_d@gmx.de (Joachim Durchholz) (2003-02-11) |
Re: Justifying Optimization joachim_d@gmx.de (Joachim Durchholz) (2003-02-11) |
Re: Justifying Optimization bhurt@spnz.org (2003-02-11) |
[3 later articles] |
From: | Robert A Duff <bobduff@shell01.TheWorld.com> |
Newsgroups: | comp.compilers |
Date: | 5 Feb 2003 23:57:15 -0500 |
Organization: | The World Public Access UNIX, Brookline, MA |
References: | 03-01-088 03-01-098 03-01-141 03-01-158 |
Keywords: | optimize, practice |
Posted-Date: | 05 Feb 2003 23:57:15 EST |
Joachim Durchholz <joachim_d@gmx.de> writes:
> Additional testing with the optimizer turned on will just find a lot
> of bugs that were never relevant in debug code - why fix them?
Those bugs might rear their ugly heads when you upgrade to a new
compiler version. Or when you make seemingly-irrelevant changes in
nearby code. Or when you port your program to a new machine or OS.
(How many times have a I seen projects where portability was
explicitly "not important" but it turned out to important later one?)
Seems to me, you'd like to find those optimizer-triggered bugs earlier
rather than later.
- Bob
Return to the
comp.compilers page.
Search the
comp.compilers archives again.