From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Announce: ksymoops 2.4.3 is available
Date: 22 Sep 2001 09:16:00 +0200 [thread overview]
Message-ID: <89M2o6gXw-B@khms.westfalen.de> (raw)
In-Reply-To: <15764.1001122752@ocs3.intra.ocs.com.au>
In-Reply-To: <Pine.LNX.4.33.0109211238010.1454-100000@base.torri.linux> <15764.1001122752@ocs3.intra.ocs.com.au>
kaos@ocs.com.au (Keith Owens) wrote on 22.09.01 in <15764.1001122752@ocs3.intra.ocs.com.au>:
> >symbol.c:220:58: warning: trigraph ??> ignored
> >symbol.c:221:44: warning: trigraph ??> ignored
> >symbol.c:225:49: warning: trigraph ??> ignored
> >symbol.c:226:35: warning: trigraph ??> ignored
>
> I believe that is a gcc bug. The text is
> snprintf(map, size,
> options->hex ? "<END_OF_CODE+%llx/????>"
> : "<END_OF_CODE+%lld/????>",
> offset);
> gcc is complaining about trigraphs but they are inside a string
> constant, not in code. IMHO gcc should not flag trigraphs in string
> constants, report it as a gcc bug.
Trigraphs are defined to work within string constants. In fact, the
standard requires trigraphs to be replaced before the very first
tokenizing of the input.
How else could the ??/ trigraph for \ possibly work?
Gcc is correct.
MfG Kai
next prev parent reply other threads:[~2001-09-22 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 9:09 Keith Owens
2001-09-21 16:43 ` Stephen Torri
2001-09-22 1:39 ` Keith Owens
2001-09-22 7:16 ` Kai Henningsen [this message]
2001-09-22 1:49 ` Keith Owens
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=89M2o6gXw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--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
Powered by JetHome