This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Trunk broken for MMIX, CRIS, i960, m32r, (v850, ARM)

The patch which broke this, also introduced some regression on i686-pc-linux-gnu
so they should have caught it before applying the patch in the first place.

I always check on the patch I am working on two different platforms, i686-pc-linux-gnu and
powerpc-apple-darwin6.6 (and i686-unknown-openbsd3.1 for kicks).

I also look the emails from Keating's regression tester
(which runs on powerpc-apple-darwin6.3) and see if I could
track the regressions down or build failures.

In fact if the build comes back up for powerpc-apple-darwin6.3, there should only be 3 regressions
down from the 19 listed in the last passing of the bootstrap.

Someone needs a regression tester on those platforms running.
I do not have the computing power to run them, unless I get the old machine from my parents.

Thanks, Andrew Pinski

On Friday, Jul 4, 2003, at 18:53 US/Eastern, Hans-Peter Nilsson wrote:

Using *-unknown-elf, except mmix-knuth-mmixware.

Worked LAST_UPDATED Thu Jul  3 10:03:12 GMT 2003
Broken LAST_UPDATED Fri Jul  4 11:17:49 GMT 2003
*Still* broken, at least on MMIX and CRIS
    at LAST_UPDATED Fri Jul  4 22:17:01 GMT 2003
(i.e. including Jeff's and Zdenek's patches, which looked

The targets in parentheses didn't build last time either (at
"Worked"), but they all see something like this (for
mmix-knuth-mmixware)  compiling different files:

x/gcc/libgcc2.c: In function `__gcc_bcmp':
x/gcc/libgcc2.c:1519: error: head insn 111 for block 0 not found in the insn stream
x/gcc/libgcc2.c:1519: internal compiler error: Segmentation fault

I see related messages for sparc64, and the regression tester
reported same breakage for powerpc-apple-darwin6.3.  A wild
guess says it'd also be visible with powerpc-unknown-eabisim.

Hey, what's the big hurry with patches that people don't have
the time to run test them with a couple of *complete
cross-toolchains including simulators* available at their
fingertips at no extra charge:
<URL:>.  Nag, nag, nobody
cares; "*these* patches are good enough that they should just
need a bootstrap+check on my PC, and only for face value".

Please help improve the simtest instructions, if that's the

Hmm, I'll see to adding instructions for MMIX, despite that
you'd have to go get a separate package for the simulator
(Knuth's "MMIXware", see
A separate section seems in order for such targets requiring
external components.

brgds, H-P

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]