From mboxrd@z Thu Jan  1 00:00:00 1970
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
Message-id: <20000322121213.C8072@atrey.karlin.mff.cuni.cz>
X-SW-Source: 2000-03/msg00554.html

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