public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bradley-k-gnu dot e2d0b7 at bradley dot csail dot mit dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/29934] New: duplicate typedef produces error message containing a bad character. Date: Tue, 21 Nov 2006 20:15:00 -0000 [thread overview] Message-ID: <bug-29934-13601@http.gcc.gnu.org/bugzilla/> (raw) Start with this code ---- cut here to start foo.c ---- typedef typedef struct abc ABC; ---- cut here to end foo.c ---- Note the duplicate typedef. This program contains an error. When I do gcc foo.c -c I get foo.c:1 error: duplicate <ahat> Where <ahat> is really some sort of funny character that looks like an "a" with an accent above it. I am guessing that the format statement is malformed or that the string is uninitialized. It should probably say foo.c: 1 error: duplicate typedef I am using gcc-4.1.1-30 from fedora core 6. gcc -v says gcc version 4.1.1 20061011 (Red Hat 4.1.1-30) This is on an AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ running Gnu/Linux. -- Summary: duplicate typedef produces error message containing a bad character. Product: gcc Version: 4.1.1 Status: UNCONFIRMED Severity: minor Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: bradley-k-gnu dot e2d0b7 at bradley dot csail dot mit dot edu GCC target triplet: x86_64-redhat-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29934
next reply other threads:[~2006-11-21 20:15 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-21 20:15 bradley-k-gnu dot e2d0b7 at bradley dot csail dot mit dot edu [this message] 2006-11-21 20:17 ` [Bug c/29934] " pinskia at gcc dot gnu dot org 2006-11-21 20:26 ` bradley-k-gnu dot e2d0b7 at bradley dot csail dot mit dot edu
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=bug-29934-13601@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).