From: Keith Seitz <keiths@redhat.com>
To: Abhijit Halder <abhijit.k.halder@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [PR 9514] Fixing parse error for "pointer to a function pointer"
Date: Tue, 18 Oct 2011 20:14:00 -0000 [thread overview]
Message-ID: <4E9DD3FC.1060407@redhat.com> (raw)
In-Reply-To: <CAOhZP9wSdVs8AbsjpKNpnFkPLV8ixOQ_JF7LmgoTOpSV_E9JRQ@mail.gmail.com>
On 10/17/2011 03:59 AM, Abhijit Halder wrote:
>> +FAIL: gdb.base/code-expr.exp: (int ** @code)
>> +FAIL: gdb.base/cvexpr.exp: (int ** const)
>>
> With latest CVS code the patch has no regression:
I still see those as regressions (gdb 7.3.50.20111018-cvs):
$ diff -p testsuite/gdb.sum.0 testsuite/gdb.sum | grep "int \*\*"
PASS: gdb.base/code-expr.exp: (@code int **)
! PASS: gdb.base/code-expr.exp: (int ** @code)
PASS: gdb.base/code-expr.exp: (@code int **)
! FAIL: gdb.base/code-expr.exp: (int ** @code)
PASS: gdb.base/cvexpr.exp: (const int **)
! PASS: gdb.base/cvexpr.exp: (int ** const)
PASS: gdb.base/cvexpr.exp: (const int **)
! FAIL: gdb.base/cvexpr.exp: (int ** const)
Do I have an outdated version of the patch?
diff --git a/gdb/c-exp.y b/gdb/c-exp.y
index b850179..60004f3 100644
--- a/gdb/c-exp.y
+++ b/gdb/c-exp.y
@@ -944,6 +944,8 @@ abs_decl: '*'
{ push_type (tp_pointer); $$ = 0; }
| '*' abs_decl
{ push_type (tp_pointer); $$ = $2; }
+ | abs_decl '*'
+ { push_type (tp_pointer); $$ = $1; }
| '&'
{ push_type (tp_reference); $$ = 0; }
| '&' abs_decl
Am I missing something else?
Keith
next prev parent reply other threads:[~2011-10-18 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 10:44 Abhijit Halder
2011-09-29 10:51 ` Abhijit Halder
2011-09-29 11:13 ` Pedro Alves
2011-09-29 11:49 ` Abhijit Halder
2011-10-03 16:46 ` Tom Tromey
2011-10-06 21:09 ` Keith Seitz
2011-10-17 11:16 ` Abhijit Halder
2011-10-18 20:14 ` Keith Seitz [this message]
2011-10-18 20:51 ` Tom Tromey
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=4E9DD3FC.1060407@redhat.com \
--to=keiths@redhat.com \
--cc=abhijit.k.halder@gmail.com \
--cc=gdb-patches@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: link
Be 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