public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dblaikie at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/55641] New: debug info for the type of a reference declared with a typedef has spurious 'const' Date: Mon, 10 Dec 2012 16:29:00 -0000 [thread overview] Message-ID: <bug-55641-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55641 Bug #: 55641 Summary: debug info for the type of a reference declared with a typedef has spurious 'const' Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug AssignedTo: unassigned@gcc.gnu.org ReportedBy: dblaikie@gmail.com Example code: typedef int &foo; int x; foo f(x); under gdb run "whatis f" and the answer is "const foo" when it should be plain "foo" (if you skip the typedef the answer is correctly "int&" not "int& const" or any similarly strange mismatch) Found in the GDB 7.5 test suite ( gdb.python/lib-types.exp ) - this is positively tested for, but so far as I can imagine that's by accident, not intent.
next reply other threads:[~2012-12-10 16:29 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-10 16:29 dblaikie at gmail dot com [this message] 2012-12-10 16:30 ` [Bug debug/55641] " dblaikie at gmail dot com 2012-12-10 17:24 ` redi at gcc dot gnu.org 2012-12-10 17:43 ` redi at gcc dot gnu.org 2012-12-10 18:32 ` dblaikie at gmail dot com 2014-02-25 11:41 ` mark at gcc dot gnu.org 2014-02-25 11:45 ` mark at gcc dot gnu.org 2014-04-24 5:57 ` pinskia at gcc dot gnu.org 2014-08-06 16:14 ` tromey at gcc dot gnu.org 2014-09-22 9:06 ` mpolacek at gcc dot gnu.org 2022-01-31 21:00 ` pinskia at gcc dot gnu.org
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-55641-4@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).