public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: bcrl@redhat.com, alan@lxorguk.ukuu.org.uk, hawkes@oss.sgi.com,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] gcc 3.0.1 warnings about multi-line literals
Date: Tue, 23 Oct 2001 13:04:27 +0100	[thread overview]
Message-ID: <11760.1003838667@warthog.cambridge.redhat.com> (raw)
In-Reply-To: Message from "David S. Miller" <davem@redhat.com>  of "Mon, 22 Oct 2001 14:39:58 PDT." <20011022.143958.78707983.davem@redhat.com>


"David S. Miller" <davem@redhat.com> wrote:   
>   /* try atomic lock inline, if that fails, spin out of line */
>   	"\tbtsl $1,%0\n"
>
> It's only gross because you decided to make it so, try:
> 
>   	"btsl $1,%0\n\t"

You can also do things like:

	"    btsl   $1,%0		\n"
	"    bne    2f			\n"
	"1:				\n"
	"    .section .text.lock	\n"
	"				\n"
	"2:  cmpl $0,%0			\n"
	"    bne 2b			\n"
	"    rep ; nop			\n"
	"    jmpl 1b			\n"
	"				\n"
	"    .section .previous		\n"

using tabs or spaces to pad out the assembly.

David

  reply	other threads:[~2001-10-23 12:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22 20:05 [PATCH] gcc 3.0.1 warnings about multi-line literals John Hawkes
2001-10-22 20:15 ` Benjamin LaHaise
2001-10-22 20:45   ` Alan Cox
2001-10-22 20:51     ` Benjamin LaHaise
2001-10-22 21:39       ` David S. Miller
2001-10-23 12:04         ` David Howells [this message]
2001-10-25  7:11       ` Richard Henderson
2001-10-25 16:47         ` Benjamin LaHaise
2001-10-22 20:51   ` H. Peter Anvin

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=11760.1003838667@warthog.cambridge.redhat.com \
    --to=dhowells@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bcrl@redhat.com \
    --cc=davem@redhat.com \
    --cc=hawkes@oss.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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