From: Brian Gerst <bgerst@didntduck.org>
To: Horms <horms@verge.net.au>
Cc: andy@wolfsinger.com, 326494@bugs.debian.org,
Marcel Holtmann <marcel@holtmann.org>,
Maxim Krasnyansky <maxk@qualcomm.com>,
bluez-devel@lists.sf.ne, linux-kernel@vger.kernel.org
Subject: Re: Problems Building Bluetooth with K6 and CONFIG_REGPARM
Date: Thu, 08 Sep 2005 12:49:17 -0400 [thread overview]
Message-ID: <43206B8D.5020908@didntduck.org> (raw)
In-Reply-To: <20050908101207.GA7236@verge.net.au>
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?
--
Brian Gerst
next prev parent reply other threads:[~2005-09-08 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1EBc9E-0001jo-RU@localhost>
2005-09-08 10:12 ` Problems Building Bluetooth with K6 and CONFIG_REGPARM Horms
2005-09-08 16:49 ` Brian Gerst [this message]
2005-09-09 2:19 ` Horms
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=43206B8D.5020908@didntduck.org \
--to=bgerst@didntduck.org \
--cc=326494@bugs.debian.org \
--cc=andy@wolfsinger.com \
--cc=bluez-devel@lists.sf.ne \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.com \
/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