From: Jan Hubicka <hubicka@atrey.karlin.mff.cuni.cz>
To: egcs@egcs.cygnus.com
Subject: How to disable sibcall optimization?
Date: Wed, 22 Mar 2000 03:12:00 -0000 [thread overview]
Message-ID: <20000322121213.C8072@atrey.karlin.mff.cuni.cz> (raw)
Hi
While doing the usual benchmarking for new snapshot, I found that there are
important performance regresions in number of benchmarks (the overall results
are again comparable with 2.95). While looking for the purpose I believe most
of those problems are caused by the sibcall code, that optimize flowgraph too
much and makes loop optimizer fail on even more loops than it does currently.
Now the loop fails in most cases on multiple entry points error.
It looks like there is no way to disable sibcalls easilly. Why? I think we
ought to have disabling flag for every such non-trivial transformation
for debugging purposes.
How far is the work on turning loop.c to use the new loop infrastructure?
Honza
next reply other threads:[~2000-03-22 3:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-22 3:12 Jan Hubicka [this message]
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
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=20000322121213.C8072@atrey.karlin.mff.cuni.cz \
--to=hubicka@atrey.karlin.mff.cuni.cz \
--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).