From: Richard Henderson <rth@twiddle.net>
To: Keith Owens <kaos@ocs.com.au>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Announce: Kernel Build for 2.5, Release 1.1 is available.
Date: Sun, 19 Aug 2001 00:13:44 -0700 [thread overview]
Message-ID: <20010819001344.C29533@twiddle.net> (raw)
In-Reply-To: <1904.997542180@ocs3.ocs-net>
In-Reply-To: <1904.997542180@ocs3.ocs-net>; from kaos@ocs.com.au on Sun, Aug 12, 2001 at 01:03:00AM +1000
On Sun, Aug 12, 2001 at 01:03:00AM +1000, Keith Owens wrote:
> asm volatile("\n-> " #sym " %c0 " #val " " #marker : : "i" (val))
This is bad -- 'c' requests an address constant (CONSTANT_ADDRESS_P
if you're playing from home), and as defined this constant must be
valid in an instruction.
Such things are by nature target specific. On ia64, for instance,
there are *no* valid address constants, since all valid memory
addresses are simple registers.
You can do what you want here with just "%0".
r~
next prev parent reply other threads:[~2001-08-19 7:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-11 15:03 Announce: Kernel Build for 2.5, Release 1.1 is available Keith Owens
2001-08-11 15:20 ` Russell King
2001-08-11 16:03 ` Keith Owens
2001-08-11 16:08 ` Philip Blundell
2001-08-11 16:14 ` Russell King
2001-08-11 21:35 ` [kbuild-devel] " Tom Rini
2001-08-11 21:55 ` Roman Zippel
2001-08-12 1:17 ` Keith Owens
2001-08-11 22:02 ` [kbuild-devel] " Tom Rini
2001-08-12 1:21 ` Keith Owens
2001-08-12 1:44 ` Tom Rini
2001-08-12 14:36 ` David Woodhouse
2001-08-12 14:48 ` Keith Owens
2001-08-12 14:56 ` David Woodhouse
2001-08-12 14:56 ` Russell King
2001-08-13 2:23 ` Keith Owens
2001-08-12 2:24 ` Keith Owens
2001-08-12 4:30 ` Keith Owens
2001-08-19 7:13 ` Richard Henderson [this message]
[not found] <20010811212051.A819@jaquet.dk>
2001-08-12 2:11 ` Keith Owens
2001-08-12 2:27 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2001-08-12 7:31 [kbuild-devel] " Rasmus Andersen
2001-08-12 7:44 ` Keith Owens
2001-08-12 7:57 ` Daniel T. Chen
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=20010819001344.C29533@twiddle.net \
--to=rth@twiddle.net \
--cc=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.