From: Toon Moene <toon@moene.indiv.nluug.nl>
To: egcs@egcs.cygnus.com
Subject: Some timings after LCM, resp. alignment of stack doubles on i686
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <36F8846D.3F7E17FF@moene.indiv.nluug.nl> (raw)
Message-ID: <19990331234600.E6xKSdl-dxcCndD3toLC_9V9BarD0S21S5DAxxNXiXk@z> (raw)
L.S.,
Here are some timings for our NWP code after addition of LCM and after
the alignment code for stack doubles went into egcs.
Pre-LCM with LCM with alignment
0SUPOBS TOOK : 0.30999946594 0.32000064850 0.31000041962
0DATACH TOOK : 147.2699890137 150.6799926758 148.7799987793
0ANAEVA TOOK : 214.6200103760 209.6599884033 200.5200042725
0GRPEVA TOOK : 1259.9199218750 1973.4698486328 1227.4000244141
0HUMSUP TOOK : 0.05993652344 0.05004882812 0.05004882812
0DATACH TOOK : 46.0799560547 46.5000000000 46.8900146484
0HUMEVA TOOK : 23.9699707031 23.1499023438 23.2700195312
0GRPEVA TOOK : 31.8000488281 32.6699218750 31.3900146484
See the fourth line ! This code contains _some_ DOUBLE PRECISION
variables and automatic arrays. Apparently something in the LCM code
generation threw it off-alignment, which was repaired by the alignment
updates.
Unfortunately, the forecast code crashes (it generates NaNs and then
dies) since the LCM change; I'll have to dig into that.
HTH,
--
Toon Moene (toon@moene.indiv.nluug.nl)
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Phone: +31 346 214290; Fax: +31 346 214286
g77 Support: fortran@gnu.org; egcs: egcs-bugs@cygnus.com
next reply other threads:[~1999-03-31 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-23 22:26 Toon Moene [this message]
1999-03-31 23:46 ` Toon Moene
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36F8846D.3F7E17FF@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=egcs@egcs.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).