Re: Announce: ksymoops 2.4.3 is available

[Kai Henningsen]

[e-mail] (Keith Owens)  wrote on 22.09.01 in <[e-mail]>:

> >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