Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751393AbVIICaT (ORCPT ); Thu, 8 Sep 2005 22:30:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751395AbVIICaT (ORCPT ); Thu, 8 Sep 2005 22:30:19 -0400 Received: from koto.vergenet.net ([210.128.90.7]:4830 "EHLO koto.vergenet.net") by vger.kernel.org with ESMTP id S1751393AbVIICaS (ORCPT ); Thu, 8 Sep 2005 22:30:18 -0400 Date: Fri, 9 Sep 2005 11:19:48 +0900 From: Horms To: Brian Gerst Cc: andy@wolfsinger.com, 326494@bugs.debian.org, Marcel Holtmann , Maxim Krasnyansky , bluez-devel@lists.sf.ne, linux-kernel@vger.kernel.org Subject: Re: Problems Building Bluetooth with K6 and CONFIG_REGPARM Message-ID: <20050909021948.GI7236@verge.net.au> References: <20050908101207.GA7236@verge.net.au> <43206B8D.5020908@didntduck.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43206B8D.5020908@didntduck.org> X-Cluestick: seven User-Agent: Mutt/1.5.10i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1555 Lines: 39 On Thu, Sep 08, 2005 at 12:49:17PM -0400, Brian Gerst wrote: > Horms wrote: > >Hi Andy, > > > >that does indeed seem to be a problem. I have narrowed it down to > >a combination of using K6 and CONFIG_REGPARM. Hunting around a bit > >I found this http://my.execpc.com/~geezer/osd/gotchas/, which > >suggests the problem is that the asm in question tries to add a register > >to the clobber list which is not available. This makes sense, > >I guess REGPARM is using edx, so inline assembly can't. > > > >I've CCed the bluetooth maintainers and lkml, hopefully someone there > >will have some input on how to resolve this problem, as inline assembly > >isn't my strong point and the problem seems to manifest in Linus' current > >git tree. > > > >The relevant code is the following call to BUILDIO(b,b,char) towards the > >bottom of include/asm/io.h > > > >BUILDIO is as follows, and I am guessing it is the "Nd"(port) and > >possibley "d"(port) portions that are problematic. > > Sounds like a compiler bug, especially since changing the CPU type fixes > it. What version of GCC? I definately think it is compiler related, I was using Debian's GCC 4.0.1-6. I could try with 3.3 or soemthing like that if you like. The problem was easily reproducable with 4.0.1 and a K6+CONFIG_REGPARM config. -- Horms - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/