Related articles |
---|
[2 earlier articles] |
Re: Justifying Optimization srikanth@cup.hp.com (srikanth) (2003-01-21) |
Re: Justifying Optimization christian.bau@cbau.freeserve.co.uk (Christian Bau) (2003-01-21) |
Re: Justifying Optimization vbdis@aol.com (2003-01-21) |
Re: Justifying Optimization jgd@cix.co.uk (2003-01-21) |
Re: Justifying Optimization touati@prism.uvsq.fr (Sid TOUATI) (2003-01-25) |
Re: Justifying Optimization ONeillCJ@logica.com (Conor O'Neill) (2003-01-25) |
Re: Justifying Optimization jvorbrueggen@mediasec.de (Jan C. =?iso-8859-1?Q?Vorbr=FCggen?=) (2003-01-25) |
Re: Justifying Optimization jvorbrueggen@mediasec.de (Jan C.=?iso-8859-1?Q?Vorbr=FCggen?=) (2003-01-25) |
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) |
[11 later articles] |
From: | "Jan C. =?iso-8859-1?Q?Vorbr=FCggen?=" <jvorbrueggen@mediasec.de> |
Newsgroups: | comp.compilers |
Date: | 25 Jan 2003 01:03:56 -0500 |
Organization: | MediaSec Technologies GmbH |
References: | 03-01-088 03-01-108 |
Keywords: | optimize, arithmetic, testing |
Posted-Date: | 25 Jan 2003 01:03:56 EST |
> We do hear this argument from developers working on floating point
> intensive code. The optimized program may produce results that
> differ from the unoptimized program by a very "small" amount. If all
> the test suite is does is a textual diff against masters generated
> by an unoptimized run, then many spurious failures may show up,
> forcing the developers to eyeball the results.
Then specdiff, from the SPEC CPU2000 benchmark, will be your
friend. See John Henning's article in IEEE COMPUTER (sometime in
mid-2000, IIRC) on what it does and why.
Jan
Return to the
comp.compilers page.
Search the
comp.compilers archives again.