This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Trigraph warnings broken
- To: bug-gcc at gnu dot org, Zack Weinberg <zack at rabi dot columbia dot edu>, Eric Christopher <echristo at cygnus dot com>
- Subject: Trigraph warnings broken
- From: Martin Buchholz <martin at xemacs dot org>
- Date: Thu, 27 Jan 2000 20:04:59 -0800 (PST)
- Reply-to: martin at xemacs dot org
Compiling XEmacs 21.2 CVS with egcs-20000124, --enable-cpplib:
/xemacs/ws/dev/src/regex.c:533:43: warning: trigraph ??' encountered
/xemacs/ws/dev/src/regex.c:535:67: warning: trigraph ??' encountered
First of all, it's _very_ nice that gcc has started printing column
numbers for warnings messages. However....
The column number in that message is correct, but the line number is
WRONG - not even close - the correct line number is 2061.
Here's the code:
/* `*?' and `+?' and `??' are okay (and mean match
minimally), but other sequences (such as `*??' and
`+++') are rejected (reserved for future use). */
Furthermore, gcc should NOT warn about trigraphs used inside comments
unless the pathological use of a trigraph would change the end of the
comment, such as in
/* some text *??/
/ some more text? */
Martin