From: Jan Hubicka <hubicka@atrey.karlin.mff.cuni.cz>
To: Richard Henderson <rth@cygnus.com>
Cc: egcs@egcs.cygnus.com
Subject: Re: How to disable sibcall optimization?
Date: Fri, 24 Mar 2000 07:01:00 -0000 [thread overview]
Message-ID: <20000324160046.B11160@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20000324015740.A19110@cygnus.com>
> On Wed, Mar 22, 2000 at 12:12:13PM +0100, Jan Hubicka wrote:
> > It looks like there is no way to disable sibcalls easilly. Why?
>
> No reason.
I personally think that the performance regressions caused by the early
flowgraph construction and jump mentioned in this email are reason, but OK. I
will try to figure out what really happends w/o such switch.
It looks to me, that it is not too hard to implement it for my testing
purposes temporary now.
The slowdowns caused by latest snapshot are quite notable (at least
on Athlon/spec2000 approx 15%)
Honza
>
>
> r~
next prev parent reply other threads:[~2000-03-24 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-22 3:12 Jan Hubicka
2000-03-24 1:57 ` Richard Henderson
2000-03-24 7:01 ` Jan Hubicka [this message]
2000-03-24 11:34 ` Richard Henderson
2000-03-24 14:20 ` Jan Hubicka
2000-03-24 13:06 ` Gerald Pfeifer
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=20000324160046.B11160@atrey.karlin.mff.cuni.cz \
--to=hubicka@atrey.karlin.mff.cuni.cz \
--cc=egcs@egcs.cygnus.com \
--cc=rth@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).