This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug optimization/8092] [3.3/3.4/3.5 regression] cross-jump triggers too often
- From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 Mar 2004 18:07:14 -0000
- Subject: [Bug optimization/8092] [3.3/3.4/3.5 regression] cross-jump triggers too often
- References: <20020930012601.8092.bernd.paysan@gmx.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From mmitchel at gcc dot gnu dot org 2004-03-21 18:07 -------
I'm going to close this PR.
AFAICT, the complaint is that when using computed gotos with -fno-reorder-blocks
and -fno-crossjumping, we generate inferior code (i.e., code that uses a
crossjump). However, the current behavior is due to the fact that we've made
changes that make the compiler run efficiently when compiling big functions with
computed gotos. Furthermore, with -freorder-blocks, the problem goes away.
If there's a problem here, then, it is that the submitter cannot use
-freorder-blocks. If that's the case, let's have a new PR explaining that.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8092