public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
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 14:20:00 -0000	[thread overview]
Message-ID: <20000324232045.A6465@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20000324113420.E19711@cygnus.com>

> Eh?  We've crossed wires.  I said there was no reason we didn't
> have the switch, which means that there's no reason not to add one.
> Feel free to generate a patch.  ;-)
Heh :) OK
I will probably do that.
> 
> > The slowdowns caused by latest snapshot are quite notable (at least
> > on Athlon/spec2000 approx 15%)
> 
> Yowza.  I wonder if simply removing the cleanup_cfg call
> from optimize_sibling_and_tail_recursive_calls is enough
> to fix things.
I didn't tested (and the machine is now about 70Km away turned off)
at friday I didn't understand the code enought to realize that disabling
may be so easy.
I've found some occurences of following constrcucts:
condjump label1
jmp label2
label1:
<some code>
label2:

And similar. It seems to me that flowgraph construction adds some notes
between the labels that makes imposible for jump1 to optimize even
such trivial examples. I am just trying to download the sources
here and continue in looking for real purpose.

But this don't seems to be only  purpose for those slowdowns.
Another one was the partial register stall introduced by my propagation
patch (this is not problem for Athlon), I have fix for this pending.

Honza
> 
> 
> r~

  reply	other threads:[~2000-03-24 14:20 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
2000-03-24 11:34     ` Richard Henderson
2000-03-24 14:20       ` Jan Hubicka [this message]
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=20000324232045.A6465@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).