This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Finding the end of the catch clauses
- To: martin at loewis dot home dot cs dot tu-berlin dot de
- Subject: Re: Finding the end of the catch clauses
- From: Mark Mitchell <mark at codesourcery dot com>
- Date: Sun, 19 Mar 2000 09:48:47 -0800
- Cc: gcc-patches at gcc dot gnu dot org
- Organization: CodeSourcery, LLC
- References: <200003191441.PAA20370@loewis.home.cs.tu-berlin.de>
>>>>> "Martin" == Martin v Loewis <martin@loewis.home.cs.tu-berlin.de> writes:
Martin> When compiling large C++ programs, significant time is
Martin> spent in push_to_sequence, when switching to the
Martin> catch_clauses insn sequence. In particular, the time is
Martin> spent in iterating over the growing insn list, every time
Martin> a handler is added to the list.
Yup. I've become increasingly convinced that the whole notion of
catch_clauses is wrong; we should use flow analysis to find them
later, and to generic code motion of unlikely code to the end of the
function. (Such a mechanism would allow us to use profiling feedback
easily as well, for example.) But, for now, we've got what we've got.
Martin> The full bootstrap and testsuite run was successfully
Martin> performed on i586-pc-linux-gnu. If approved, the cp and
Martin> java Changelog entries will go in their separate change
Martin> logs, of course.
This is OK. Thanks!
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com