This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: What is this patch doing?
- To: Bernd Schmidt <bernds at pasanda dot cygnus dot co dot uk>
- Subject: Re: What is this patch doing?
- From: Joern Rennecke <amylaar at cygnus dot co dot uk>
- Date: Tue, 1 Aug 2000 20:35:15 +0100 (BST)
- CC: gcc at gcc dot gnu dot org, rth at cygnus dot com
> I found that the patch below seems to be at least partially responsible for
> the massive testsuite failures I'm seeing for the sh. I couldn't find a
> discussion of it in any of the mailing list archives (searching for "Must be
> split", "output_branchy_insn" and "cmpgt"). Why was it installed?
Well, the SH port didn't even build before. It was failing to build some
part of libgcc.a
> The problem appears to be that there's no JUMP_LABEL for the newly
> generated jump. Is it valid for splitters to create new basic blocks?
We talked in the thread '(i386-linux x sh-elf) build breakage' on gcc-bugs
about it. Richard Henderson said that the first post-reload splitter
could generate new blocks.
> The failure can be observed by compiling c-torture/execute/950612-1.c with
> "-m3". We get a segfault from cc1. This goes away if I revert this patch.
Do I need to pass any other flags to cc1? Or is this dependent on some
patch that was checked in after mine?