From: Jeffrey A Law <law@cygnus.com>
To: N8TM@aol.com
Cc: Jerry.Quinn.jquinn@nt.com, egcs@cygnus.com
Subject: Re: egcs produces slow code on HPUX 10.20
Date: Sun, 27 Sep 1998 16:28:00 -0000 [thread overview]
Message-ID: <1411.906870125@upchuck> (raw)
In-Reply-To: <c4b48993.3607a123@aol.com>
In message < c4b48993.3607a123@aol.com >you write:
> In a message dated 9/21/98 10:14:32 PM Pacific Daylight Time,
> Jerry.Quinn.jquinn@nt.com writes:
>
> > code that is
> > significantly slower for egcs 1.1a on an HPUX 10.20 pa-risc 2.0
> > machine
> You might be interested in the current main line snapshots. I've seen
> improvements up to 50% from egcs-1.1.
Note egcs doesn't optimize specifically for pa2.0 machines. Certain opts
which improve code for pa1.1 (fmpyadd/fmpysub generation) are terrible for
performance on pa2.0 machines.
Jeff
next prev parent reply other threads:[~1998-09-27 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-22 6:09 N8TM
1998-09-27 16:28 ` Jeffrey A Law [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-09-21 19:37 Jerry Quinn
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=1411.906870125@upchuck \
--to=law@cygnus.com \
--cc=Jerry.Quinn.jquinn@nt.com \
--cc=N8TM@aol.com \
--cc=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).