public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/14186] const volatile is ignored for TYPE_INSTANCE Date: Wed, 20 Jun 2012 14:56:00 -0000 [thread overview] Message-ID: <bug-14186-4717-Mzb8CjWsJz@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14186-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14186 --- Comment #2 from Tom Tromey <tromey at redhat dot com> 2012-06-20 14:55:38 UTC --- Created attachment 6461 --> http://sourceware.org/bugzilla/attachment.cgi?id=6461 start of a patch Here's the start of a patch. It has some unnecessary stuff in it, since I was hacking around a bit. But some parts should be ok, like the c-exp.y change. The TYPE_INSTANCE code seems very suspect to me. The parser production just uses 'exp' -- but this means all kinds of weird things can be parsed here. (On further reflection I wish I hadn't allowed this extension...) Also the code in eval.c does not use cleanups, so it can leak memory on errors. The fundamental problem I hit is that rank_one_type does not consider cv-qualifiers. So, even after getting the qualifiers all the way through, we still get the wrong answer; and I didn't want to try fixing this problem yet. The cv-qualifier problem could be hacked around in compare_parameters, but that seemed too hackish for me. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
prev parent reply other threads:[~2012-06-20 14:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-30 22:22 [Bug c++/14186] New: " jan.kratochvil at redhat dot com 2012-06-19 20:42 ` [Bug c++/14186] " tromey at redhat dot com 2012-06-20 14:56 ` tromey at redhat dot com [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-14186-4717-Mzb8CjWsJz@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).