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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Sep 23 2001 - 21:00:47 EST