From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brad Boyer Subject: Re: aranym bug, manifests as "ida_remove called for id=13" on recent kernels Date: Sun, 10 Oct 2010 21:36:32 -0700 Message-ID: <20101011043632.GA2566@cynthia.pants.nu> References: <20101007174948.GT19804@ZenIV.linux.org.uk> <20101010144952.GF19804@ZenIV.linux.org.uk> <20101010235256.GG19804@ZenIV.linux.org.uk> <20101011024103.GH19804@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cynthia.allandria.com ([76.245.85.235]:40967 "EHLO cynthia.pants.nu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751340Ab0JKFYq (ORCPT ); Mon, 11 Oct 2010 01:24:46 -0400 Content-Disposition: inline In-Reply-To: <20101011024103.GH19804@ZenIV.linux.org.uk> Sender: linux-m68k-owner@vger.kernel.org List-Id: linux-m68k@vger.kernel.org To: Al Viro Cc: Geert Uytterhoeven , linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org On Mon, Oct 11, 2010 at 03:41:03AM +0100, Al Viro wrote: > Argh... OK, going through aranym with debugger has exhonorated it. My > apologies ;-/ It *is* gcc in sid. Testcase: > > extern int foo(int); > void *bar(int n) > { > return (void *)foo(n); > } > > and gcc -S -O2 turns that into > bar: > link.w %fp,#0 > unlk %fp > jra foo > I presume the bug is that foo put the return value in %d0 while bar should have its return value in %a0. This function isn't eligible for the optimization being used due to this need to move the result into a different register. > Spot the obvious bug... BTW, why on the Earth does debian-ports m68k tree > use gcc-4.3 with Cthulhu-scaring 700Kb gzipped patch and does *not* have > gcc-4.4? I believe that gcc-4.4 for m68k is being held up by the TLS support patches. While I haven't been personally involved to any great degree, I got the impression that the work is pretty much done other than getting it included. Brad Boyer flar@allandria.com