From: Toon Moene <toon@moene.indiv.nluug.nl>
To: law@cygnus.com, wilson@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: Fortran array indexing on 64-bit targets & snapshot 971023
Date: Fri, 24 Oct 1997 11:21:00 -0000 [thread overview]
Message-ID: <9710241721.AA16967@moene.indiv.nluug.nl> (raw)
In-Reply-To: <11138.877705479@hurl.cygnus.com>
In message < 9710241223.AA02380@moene.indiv.nluug.nl > I wrote:
> It seems that Richard Henderson's `expr.c' (get_inner_reference)
> patch didn't make into snapshot 971023.
>
> Was there a compelling reason to exclude it ?
Jeff:
> Jim had some questions about it, which nobody has answered yet:
[ Complicated discussion about the special handling of zero lower
bound array references elided ]
Yes, I've looked into this and didn't understand it either.
Nevertheless, to inject some numbers into this discussion (using
Patick Queutey's CFD benchmark example on a 500 Mhz Alpha):
egcs-971023, bare (3 runs):
7.60user 0.02system 0:20.87elapsed 36%CPU (0avgtext+0avgdata
0maxresident)k
7.25user 0.01system 0:11.27elapsed 64%CPU (0avgtext+0avgdata
0maxresident)k
7.78user 0.02system 0:11.18elapsed 69%CPU (0avgtext+0avgdata
0maxresident)k
After applying Richard Henderson's `exp.c' patch (4 runs):
4.51user 0.14system 0:09.17elapsed 50%CPU (0avgtext+0avgdata
0maxresident)k
4.53user 0.01system 0:08.20elapsed 55%CPU (0avgtext+0avgdata
0maxresident)k
4.15user 0.02system 0:07.72elapsed 54%CPU (0avgtext+0avgdata
0maxresident)k
4.37user 0.01system 0:07.29elapsed 60%CPU (0avgtext+0avgdata
0maxresident)k
(with your `use' patch I get between 3.6 and 3.9 seconds).
So I hope a decision will be reached (to say the least :-)
Cheers,
Toon.
next prev parent reply other threads:[~1997-10-24 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-24 5:26 Toon Moene
1997-10-24 8:03 ` Jeffrey A Law
1997-10-24 11:21 ` Toon Moene [this message]
1997-10-26 5:26 ` Toon Moene
1997-10-26 8:09 ` Jeffrey A Law
1997-10-26 10:31 ` Per Bothner
1997-10-27 14:46 ` Jim Wilson
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=9710241721.AA16967@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=wilson@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).