From: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>
To: Fabian Arias <dewback@vtr.net>
Cc: Anuradha Ratnaweera <anuradha@gnu.org>,
Anatoly Ivanov <avi@levi.spb.ru>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.5 and gcc v3 final
Date: Sun, 24 Jun 2001 13:33:51 -0400 [thread overview]
Message-ID: <200106241733.f5OHXpW2000565@sleipnir.valparaiso.cl> (raw)
In-Reply-To: Message from Fabian Arias <dewback@vtr.net> of "Sun, 24 Jun 2001 12:33:58 -0400." <Pine.LNX.4.21.0106241230300.876-100000@localhost.localdomain>
Fabian Arias <dewback@vtr.net> said:
> On Sun, 24 Jun 2001, Anuradha Ratnaweera wrote:
> > On Fri, Jun 22, 2001 at 10:29:25AM +0400, Anatoly Ivanov wrote:
> > > I hope that lk-developers would fix it one day.
> > Multi-string literals is a nice little ANSI C feature that appears
> > everywhere. Why it is necessary to "fix" them?
> I think that "fix" doesn't necesary mean "kill" the feature.
> But is a problem that some of us, compiling the ac series with gcc-3, have
> had.
What gcc objects to is stuff like:
"This is a nice long string
that just goes on
and on\n"
which is illegal in C AFAIU. It does not object to:
"This long string"
"spans several lines, "
"but legally.\n"
The first form does/did appear in several asm()s. Fix them, send a patch.
--
Horst von Brand vonbrand@sleipnir.valparaiso.cl
Casilla 9G, Vin~a del Mar, Chile +56 32 672616
next prev parent reply other threads:[~2001-06-25 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 12:03 Kissandrakis S. George
2001-06-20 12:24 ` Anatoly Ivanov
2001-06-22 1:47 ` Fabian Arias
2001-06-22 6:29 ` Anatoly Ivanov
2001-06-24 3:52 ` Anuradha Ratnaweera
2001-06-24 16:33 ` Fabian Arias
2001-06-24 17:33 ` Horst von Brand [this message]
2001-06-25 16:58 ` Anuradha Ratnaweera
2001-06-25 18:59 ` [PATCH] GCC v3 warning fixes #1 (Was: Re: 2.4.5 and gcc v3 final) Anuradha Ratnaweera
2001-06-25 22:41 ` 2.4.5 and gcc v3 final Andreas Bombe
2001-06-26 15:04 ` Anuradha Ratnaweera
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=200106241733.f5OHXpW2000565@sleipnir.valparaiso.cl \
--to=vonbrand@sleipnir.valparaiso.cl \
--cc=anuradha@gnu.org \
--cc=avi@levi.spb.ru \
--cc=dewback@vtr.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 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®