public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Andi Kleen <ak@suse.de>, Joel Sherrill <joel@OARcorp.com>
Cc: gcc@gcc.gnu.org
Subject: Re: inline asm string/line break rules change
Date: Sat, 13 Apr 2002 14:24:00 -0000	[thread overview]
Message-ID: <200204132303.04966@enzo.bigblue.local> (raw)
In-Reply-To: <p737knbbdkm.fsf@oldwotan.suse.de>

On Saturday 13 April 2002 21:31, Andi Kleen wrote:
> Joel Sherrill <joel@OARcorp.com> writes:
> > If there was a discussion on this, I must not have missed
> > it or not realized the potential impact.  I sure don't want
> > to begin to modify other code bases until I know the intention.
>
> It's also a big problem for the linux kernel and for various other
> packages.

kernel is fixed for a long time and there are only a few packages out there 
using inline assembly heavily.

>  Even if there should be good reasons to discourage multi line string
> I think it shouldn't be warned until an alternative inline assembly
> syntax that doesn't rely on strings exists. Currently it is discouraging
> one practice with no good replacement.

Please? A warning is there since gcc-3.0! And adding the 3 chars \n\ to each 
multiline isn't that hard, with Joel's example:

 asm volatile(" movw %%ds,%0  
                movw %, %%es" 
               : "=r" (tmp_segment) :
               : "0" (tmp_segment) );


would turn into

 asm volatile(" movw %%ds,%0  \n\
                movw %, %%es" 
               : "=r" (tmp_segment) :
               : "0" (tmp_segment) );

Seems easy enough to me (did it to the ppc assmbly in glibc for example).

Franz.

  reply	other threads:[~2002-04-13 21:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3CB88687.85AA58CB@OARcorp.com.suse.lists.egcs>
2002-04-13 12:59 ` Andi Kleen
2002-04-13 14:24   ` Franz Sirl [this message]
2002-04-13 15:09     ` Andi Kleen
2002-04-13 22:36       ` David S. Miller
2002-04-13 23:27         ` Tim Hollebeek
2002-04-14  2:24           ` Andi Kleen
2002-04-14  2:47             ` David S. Miller
2002-04-14  2:52             ` Tim Hollebeek
2002-04-14  6:04               ` Andi Kleen
2002-04-14  7:18                 ` Joel Sherrill
2002-04-14  1:46         ` Andi Kleen
2002-04-14 18:15           ` Jamie Lokier
2002-04-14 18:47             ` Joel Sherrill
2002-04-14 23:23               ` Zack Weinberg
2002-04-20 11:46                 ` Joel Sherrill
2002-04-15  8:05     ` Joel Sherrill
2002-04-16 13:13       ` Jim Wilson
2002-04-16 13:15         ` Joel Sherrill
2002-04-13 11:57 Joel Sherrill

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=200204132303.04966@enzo.bigblue.local \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=ak@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=joel@OARcorp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).