From: Xose Vazquez Perez <xose@wanadoo.es>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-bk30 and C trigraphs bugs
Date: Tue, 27 Jan 2004 17:21:45 +0100 [thread overview]
Message-ID: <40169019.5040002@wanadoo.es> (raw)
In-Reply-To: <20040119153814.5ebc3a87.rddunlap@osdl.org>
Randy.Dunlap wrote:
> On Thu, 09 Oct 2003 01:44:31 +0200 Xose Vazquez Perez <xose@wanadoo.es> wrote:
>
> | hi,
> |
> | There are some mistakes with C trigraphs:
> |
> | arch/m68k/atari/stram.c: PRINT_PROC( "??)\n" );
> | arch/sparc/kernel/traps.c: die_if_kernel("Penguin instruction from Penguin mode??!?!", regs);
> | drivers/atm/idt77252.c: printk("%s: PCI_COMMAND: %04x (???)\n",
> | drivers/acorn/scsi/acornscsi.c: "??-out", /* 1C */
> | drivers/acorn/scsi/acornscsi.c: "??-in", /* 1D */
> | drivers/block/acsi.c: { 0x00, "No error (??)" },
> | drivers/block/acsi.c: { 0x00, "No error (??)" },
> | drivers/media/video/saa7110.c: DEBUG(printk(KERN_INFO "unknown saa7110_command??(%d)\n",cmd));
> | drivers/mtd/maps/sun_uflash.c: name: "SUNW,???-????",
> | drivers/scsi/ppa.c: printk("ppa: parity error (???)\n");
> | drivers/scsi/ppa.c: printk("ppa: bad interrupt (???)\n");
> | drivers/scsi/imm.c: printk("imm: parity error (???)\n");
> | drivers/scsi/imm.c: printk("imm: bad interrupt (???)\n");
> | net/rose/af_rose.c: callsign = "??????-?";
> |
> | fixes are trivial.
> |
> | Is 2.6.0-pre free of them :-?
>
> Of course not. I grepped over 100 of them in 2.6.1.
>
> Are they a problem?
Visually yes, they hurt to the sight ;-)
But unless somebody uses -std or -ansi, by default GCC
ignores trigraphs.
--
Software is like sex, it's better when it's bug free.
prev parent reply other threads:[~2004-01-27 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 23:44 2.4.22-bk30 and C trigraphs bugs Xose Vazquez Perez
2004-01-19 23:38 ` Randy.Dunlap
2004-01-27 16:21 ` Xose Vazquez Perez [this message]
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=40169019.5040002@wanadoo.es \
--to=xose@wanadoo.es \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.