public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net> To: gcc-gnats@gcc.gnu.org Subject: c/5791: '\a' is interpreted as 'a' Date: Thu, 28 Feb 2002 09:56:00 -0000 [thread overview] Message-ID: <87elj6j777.fsf@pixie.eng.ascend.com> (raw) >Number: 5791 >Category: c >Synopsis: '\a' is interpreted as 'a' >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Thu Feb 28 01:26:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Jim Meyering >Release: 3.2 20020227 (experimental) >Organization: >Environment: System: Linux never 2.4.17 #3 SMP Tue Dec 29 21:27:44 CET 2001 i686 unknown Architecture: i686 <machine, os, target, libraries (multiple lines)> host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: /mirror/d/gcc/configure --disable-nls --prefix=/p/p/gcc-2002-02-28.01h10 >Description: '\a' is interpreted as 'a' >How-To-Repeat: $ cat k.c f () { switch (1) { case '\a': case 'a': return; } } $ gcc k.c k.c: In function `f': k.c:1: duplicate case value k.c:1: previously used here [Exit 1] >Fix: 2002-02-28 Jim Meyering <meyering@lucent.com> * cpplex.c (cpp_parse_escape): Restore mistakenly-removed code: \a still means TARGET_BELL. --- cpplex.c.~1.190.~ Thu Feb 28 02:06:24 2002 +++ cpplex.c Thu Feb 28 10:10:35 2002 @@ -1721,6 +1721,7 @@ cpp_parse_escape (pfile, pstr, limit, ma case 'a': if (CPP_WTRADITIONAL (pfile)) cpp_warning (pfile, "the meaning of '\\a' is different in traditional C"); + c = TARGET_BELL; break; case 'e': case 'E': >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-02-28 9:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-28 9:56 Jim Meyering [this message] 2002-02-28 12:06 neil
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=87elj6j777.fsf@pixie.eng.ascend.com \ --to=jim@meyering.net \ --cc=gcc-gnats@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: linkBe 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).