public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53863] misleading error message for redefinitions Date: Fri, 16 Jul 2021 14:50:50 +0000 [thread overview] Message-ID: <bug-53863-4-uqPpATWDIt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53863-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53863 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2021-07-16 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- Current trunk says this: 53863.C:2:12: error: 'a' conflicts with a previous declaration 2 | enum { a = 1 }; | ^ 53863.C:1:8: note: previous declaration '<unnamed enum> a' 1 | enum { a = 1 }; | ^ The caret on the error seems wrong, as it points to the initializer not the enumerator. The note is correct.
prev parent reply other threads:[~2021-07-16 14:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-05 10:21 [Bug c++/53863] New: " akim.demaille at gmail dot com 2012-07-05 10:46 ` [Bug c++/53863] " redi at gcc dot gnu.org 2021-07-16 14:50 ` redi at gcc dot gnu.org [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=bug-53863-4-uqPpATWDIt@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).