public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Brad Boyer <flar@allandria.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: aranym bug, manifests as "ida_remove called for id=13" on recent kernels
Date: Sun, 10 Oct 2010 21:36:32 -0700	[thread overview]
Message-ID: <20101011043632.GA2566@cynthia.pants.nu> (raw)
In-Reply-To: <20101011024103.GH19804@ZenIV.linux.org.uk>

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

  reply	other threads:[~2010-10-11  5:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 17:49 aranym bug, manifests as "ida_remove called for id=13" on recent kernels Al Viro
2010-10-10  9:47 ` Geert Uytterhoeven
2010-10-10 14:49   ` Al Viro
2010-10-10 20:18     ` Geert Uytterhoeven
2010-10-10 23:52       ` Al Viro
2010-10-11  2:41         ` Al Viro
2010-10-11  4:36           ` Brad Boyer [this message]
2010-10-11  4:48             ` Al Viro
2010-10-11 12:21               ` Thorsten Glaser
2010-10-11 13:10                 ` Andreas Schwab
2010-10-11 13:35                 ` Al Viro
2010-10-11 13:45                   ` Thorsten Glaser
2010-10-11 14:15                   ` Andreas Schwab
2010-10-11 14:24                     ` Al Viro
2010-10-11 22:02                       ` Al Viro
2010-11-02 15:30                       ` Geert Uytterhoeven
2010-10-11 19:05                 ` Mikael Pettersson
2010-10-11  9:27           ` Mikael Pettersson
2010-10-11 11:50             ` Mikael Pettersson
2010-10-11 12:29             ` Andreas Schwab
2010-10-11  8:39         ` Geert Uytterhoeven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101011043632.GA2566@cynthia.pants.nu \
    --to=flar@allandria.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox