warning: trigraph ... ignored
Thorsten Kranzkowski
th@Marvin.DL8BCU.ampr.org
Tue Jun 13 16:18:00 GMT 2000
Hi!
During my latest linux kernel compile I saw several of these warnings:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test1-ac18-work/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mno-fp-regs -ffixed-8 -mcpu=ev4 -Wa,-mev6 -DEXPORT_SYMTAB -c md.c
In file included from /usr/src/linux-2.4.0-test1-ac18-work/include/linux/raid/md.h:35,
from md.c:32:
/usr/src/linux-2.4.0-test1-ac18-work/include/linux/delay.h:19:44: warning: trigraph ??/ ignored
The relevant part of delay.h (linenumbers added):
14 /*
15 * Using udelay() for intervals greater than a few milliseconds can
16 * risk overflow for high loops_per_sec (high bogomips) machines. The
17 * mdelay() provides a wrapper to prevent this. For delays greater
18 * than MAX_UDELAY_MS milliseconds, the wrapper is used. Architecture
19 * specific values can be defined in asm-???/delay.h as an override.
20 * The 2nd mdelay() definition ensures GCC will optimize away the
21 * while loop for the common cases where n <= MAX_UDELAY_MS -- Paul G.
22 */
I don't exactly know what trigraphs are, I assume some weird replacement
expression for unusual characters. But I don't think gcc should warn about
them in _comments_ !
gcc version 2.96 20000530 (experimental)
linux 2.3.99-pre3
glibc 2.1.3
Alpha AXPpci33 'Noname'
please CC me as I'm not on the list
Bye,
Thorsten
--
| Thorsten Kranzkowski Internet: dl8bcu@gmx.net |
| Mobile: ++49 170 1876134 Snail: Niemannsweg 30, 49201 Dissen, Germany |
| Ampr: dl8bcu@db0lj.#rpl.deu.eu, dl8bcu@marvin.dl8bcu.ampr.org [44.130.8.19] |
More information about the Gcc
mailing list