mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Gareth Hughes <gareth.hughes@acm.org>
Cc: paulr <reichp@ameritech.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.7 -- GCC-3.0 -- "multiline string literals deprecated" -- PATCH
Date: Tue, 31 Jul 2001 17:11:29 +0300	[thread overview]
Message-ID: <20010731171129.U2650@mea-ext.zmailer.org> (raw)
In-Reply-To: <3B663AC9.3A290C32@ameritech.net> <3B66B838.C8B427B1@acm.org>
In-Reply-To: <3B66B838.C8B427B1@acm.org>; from gareth.hughes@acm.org on Tue, Jul 31, 2001 at 11:52:56PM +1000

On Tue, Jul 31, 2001 at 11:52:56PM +1000, Gareth Hughes wrote:
> paulr wrote:
> > Folks,
> > 
> > While building both kernels 2.4.6 and 2.4.7,
> > I encountered a series of compiler warnings,
> > 
> > warning: multiline string literals are deprecated.
> > 
> > The build environment was gcc3.0 and binutils-2.11.2.
> 
> Yes, unfortunately GCC 3.0 deprecated multiline string literals -- I saw
> someone arguing on the GCC mailing lists that writing large chunks of
> inline asm shouldn't be "easy",....

   Those are different things.

   The multiline string literal deprecation comes from people who
   define what the new ANSI-C (C9X, or whatever) is, and inline asm
   just uses literal strings as its input data.

   The inline asm() does essentially want to look like a function call
   with lots of strings as parameters.  It has special __builtin_ meaning,
   of course, but that is way after the lexical input scanner has done
   its work.

> -- Gareth

/Matti Aarnio

  reply	other threads:[~2001-07-31 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-31  4:57 paulr
2001-07-31 13:52 ` Gareth Hughes
2001-07-31 14:11   ` Matti Aarnio [this message]
2001-07-31 14:15   ` Horst von Brand
2001-07-31 15:57     ` Gareth Hughes

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=20010731171129.U2650@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=gareth.hughes@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reichp@ameritech.net \
    /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

all inboxes | Powered by JetHome®