This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/8092] [3.3/3.4/4.0 regression] cross-jump triggers too often
- From: "e98cuenc at yahoo dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Apr 2006 09:10:44 -0000
- Subject: [Bug rtl-optimization/8092] [3.3/3.4/4.0 regression] cross-jump triggers too often
- References: <bug-8092-4580@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #31 from e98cuenc at yahoo dot com 2006-04-26 09:10 -------
This bug was closed under the assumption that ""Furthermore, with
-freorder-blocks, the problem goes away.""
That's false (most of the time), with 3.4.2. AFAICT there is no set of flags
able to reliably desactivate that cross-jumping.
It should be noted that when the extra jmp is shared by a low number of BB,
then it's put inline, as asked (with -fno-crossjumping). In my VM, when I went
over 10 opcodes (ie, 12 or more "goto *(opcodes[*ip++])") I got again an extra
BB for jmp *%eax.
Any hopes of resurrecting this bug?
--
e98cuenc at yahoo dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |e98cuenc at yahoo dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8092