From: Jakub Jelinek <jakub@redhat.com>
To: Giacomo Catenazzi <cate@debian.org>
Cc: ncw@axis.demon.co.uk, linux-kernel@vger.kernel.org
Subject: Re: Asm style
Date: Thu, 22 Nov 2001 06:31:09 -0500 [thread overview]
Message-ID: <20011122063109.O4087@devserv.devel.redhat.com> (raw)
In-Reply-To: <fa.derh1nv.1h0ai0b@ifi.uio.no> <fa.njuqm5v.100c5ak@ifi.uio.no> <3BFD0BB3.2000000@debian.org>
In-Reply-To: <3BFD0BB3.2000000@debian.org>; from cate@debian.org on Thu, Nov 22, 2001 at 03:29:07PM +0100
On Thu, Nov 22, 2001 at 03:29:07PM +0100, Giacomo Catenazzi wrote:
> gcc should warn in both case (when calling it with -pedantic -ansi).
> But forget my comment:
> Talking about ANSI C for asm construct doen't make much sense.
It should not warn.
Please read ISO C99 5.1.1.2:
2. Each instance of a backslash character (\) immediately followed by a new-line
character is deleted, splicing physical source lines to form logical source lines.
Only the last backslash on any physical source line shall be eligible for being part
of such a splice. A source file that is not empty shall end in a new-line character,
which shall not be immediately preceded by a backslash character before any such
splicing takes place.
This happens even before tokenizing (and before macro expansion too).
Jakub
next prev parent reply other threads:[~2001-11-22 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.derh1nv.1h0ai0b@ifi.uio.no>
[not found] ` <fa.njuqm5v.100c5ak@ifi.uio.no>
2001-11-22 14:29 ` Asm style Giacomo Catenazzi
2001-11-22 11:31 ` Jakub Jelinek [this message]
[not found] <fa.d6k3juv.16q3on@ifi.uio.no>
[not found] ` <fa.cbkkrrv.m72ejr@ifi.uio.no>
2001-11-22 12:43 ` Giacomo Catenazzi
2001-11-22 9:27 ` ncw
2001-11-21 23:07 vda
2001-11-21 21:21 ` Ben Collins
[not found] <01112123070300.05447@manta.suse.lists.linux.kernel>
2001-11-21 21:23 ` Andi Kleen
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=20011122063109.O4087@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=cate@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncw@axis.demon.co.uk \
/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.