This is the mail archive of the gcc@gcc.gnu.org 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]

Re: Results for egcs-2.92.18 19981103 (gcc2 ss-980609 experimental) testsuite on powerpc-redhat-linux-gnu


At 03:47 06.11.98 , Mike Stump wrote:
>> From: fsirl@kernel.crashing.org
>> Date: Tue, 3 Nov 1998 15:47:31 -0600
>> To: egcs@cygnus.com
>
>> Native configuration is powerpc-redhat-linux-gnu
>
>> FAIL: g++.mike/dyncast5.C  Execution test
>> FAIL: g++.mike/net39.C  Execution test
>> FAIL: g++.mike/offset1.C  Execution test
>> FAIL: g++.mike/p3708b.C  Execution test
>> FAIL: g++.mike/p4246.C  Execution test
>> FAIL: g++.mike/p4736c.C  Execution test
>> FAIL: g++.mike/p6610b.C  Execution test
>> FAIL: g++.mike/virt5.C  Execution test
>
>I wonder if all these failures mean I don't know how to write a
>portable testcase or if I just know how to right really good ones.
>Maybe you can help track these problems down and let us know...

I haven't looked into them yet, cause I thought the reason of the failures
might be the implementation of ASM_OUTPUT_MI_THUNK by Michael Meissner
(which is quite fresh to PPC/SVR in the mainline branch) and I was waiting
for the mainline to calm down a bit after the local spilling patches to
look into them.
It would be nice if you could tell me if ASM_OUTPUT_MI_THUNK might be
related to these failures (and if this is the case, which testcase is best
suited to track down the failures).

Franz.



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