At 12:01 08.02.00 , Martin Buchholz wrote:
>>>>> "ZW" == Zack Weinberg
<zack(a)wolery.cumb.org> writes:
ZW> Odds are that the bug was fixed by this patch:
ZW> 2000-02-04 Richard Henderson <rth(a)cygnus.com>
ZW> * integrate.c (expand_inline_function): Revert 19 Jan change.
I am sorry to report that this inlining bug is still there in
egcs-20000207. Again I offer access to my machine if provided with an
ssh public key. A reproducible test case is worth its weight in electrons.
Don't try reproducing it on CVS XEmacs 21.2. That has my egcs bug
workaround patch applied.
I also found another workaround that sheds light on the bug.
Recap: The original bug concerned C++ inlining a function with 6
arguments, one of which has its address taken. This is a rare enough
operation that one can see how the compiler can easily get it wrong -
it wants arguments to be in registers, maybe.
That sounds familiar to one bug I'm seeing on powerpc-linuc-gnu with C++.
Can you check if adding -fno-strict-aliasing fixes the bug? If yes, could
you try if the patch in
<
http://gcc.gnu.org/ml/gcc-bugs/2000-01/msg00038.html> fixes the bug for
the default -fstrict-aliasing too? I would be very interested to get a C
testcase for that problem.
Franz.