public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Rich Baum" <baumr1@coral.indstate.edu>
To: gcc@gcc.gnu.org
Subject: Trigraph warnings when compiling linux-2.4.0-prerelease1
Date: Mon, 01 Jan 2001 09:56:00 -0000	[thread overview]
Message-ID: <3A507E7C.4279.3313E2@localhost> (raw)

I get the following warnings when compiling the latest linux kernel 
with the 20001225 gcc snapshot:

gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-
prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -
mpreferred-stack-boundary=2 -march=k6    -c -o names.o names.c
In file included from names.c:38:
devlist.h:1278:33: warning: trigraph ??) ignored
devlist.h:6370:25: warning: trigraph ??) ignored
In file included from names.c:44:
devlist.h:1278:33: warning: trigraph ??) ignored
devlist.h:6370:25: warning: trigraph ??) ignored
In file included from names.c:50:
devlist.h:1278:33: warning: trigraph ??) ignored
devlist.h:6370:25: warning: trigraph ??) ignored

gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-
prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -
mpreferred-stack-boundary=2 -march=k6 -DMODULE -
DMODVERSIONS -include 
/usr/src/linux/include/linux/modversions.h   -c -o imm.o imm.c
imm.c:929:37: warning: trigraph ??) ignored
imm.c:938:38: warning: trigraph ??) ignored

The lines are as follows:
devlist.h:
line 1278: 	DEVICE(109e,036c,"Bt879(??) Video Capture")
line 6370:   VENDOR(2a15,"3D Vision(???)")

imm.c:
line 929: 	printk("imm: parity error (???)\n");
line 938: 	printk("imm: bad interrupt (???)\n");

From looking at the code it is apparent to me that the authors of 
these files meant to print the string ??) and not the character ].  Is 
there a possible fix to remove these warnings or should I just ignore 
them?  I felt this would be the appropriate list to send this to since 
it compiles without these warnings with egcs-1.1.2.

Rich.

             reply	other threads:[~2001-01-01  9:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-01  9:56 Rich Baum [this message]
2001-01-01 11:50 ` Tim Hollebeek
2001-01-01 15:16 ` Joe Buck
     [not found] <200101020654.WAA03344@neosilicon.transmeta.com>
2001-01-01 23:00 ` Linus Torvalds
2001-01-02  0:23   ` Fergus Henderson
2001-01-02  9:18   ` Joe Buck
2001-01-02 10:38     ` Linus Torvalds
2001-01-02 10:58       ` Joe Buck
2001-01-02 11:15         ` Linus Torvalds
2001-01-02 11:50           ` Per Bothner
2001-01-02 11:55             ` Linus Torvalds
2001-01-02 12:40               ` Joe Buck
2001-01-02 13:50                 ` Linus Torvalds
2001-01-02 14:50             ` Toon Moene
2001-01-03 23:39             ` Zack Weinberg
2001-01-02  9:26 dewar
2001-01-02 12:05 dewar
2001-01-02 13:27 dewar
2001-01-02 15:20 ` Joe Buck
2001-01-02 19:03 ` Fergus Henderson
2001-01-03 11:21   ` Joe Buck

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=3A507E7C.4279.3313E2@localhost \
    --to=baumr1@coral.indstate.edu \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).