From: Ken Werner <ken@linux.vnet.ibm.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Daniel Jacobowitz <dan@codesourcery.com>,
Ulrich Weigand <uweigand@de.ibm.com>,
gdb-patches@sourceware.org
Subject: Re: [patch] fix pre-/post- in-/decrement
Date: Tue, 02 Nov 2010 08:23:00 -0000 [thread overview]
Message-ID: <201011020923.34670.ken@linux.vnet.ibm.com> (raw)
In-Reply-To: <201010190938.35120.ken@linux.vnet.ibm.com>
On Tuesday, October 19, 2010 9:38:34 am Ken Werner wrote:
> On Wednesday, October 13, 2010 9:00:28 pm Tom Tromey wrote:
> > Ken> I don't see how to control the type of the result of an operator
> > Ken> there. I'm still quite new to the GDB parsing internals and would
> > Ken> appreciate any insights.
> >
> > It is probably a bit of a pain, since the IR generated by the parser is
> > a bit unusual (as compilers go).
> >
> > However, it seems to me that it would be much friendlier for users to
> > report this as a parse error rather than a runtime error.
> >
> > One option would be to write a C/C++ implementation of the language_defn
> > la_post_parser method, which would look at the expression to see if this
> > constraint is violated.
> >
> > Another option would be to try to implement it in the grammar.
>
> Ok - I see. Thanks for your suggestions. This seems to be something bigger
> and could be implemented as part of a future patch :). I think for now the
> non- language dependent parts of the patch would be sufficient.
> The attached patch only contains the fix for the post in-/decrement
> operators as this is what the vec_unop patch
> (http://sourceware.org/ml/gdb-
> patches/2010-10/msg00031.html) prevents from going upstream.
> Tested on i686-*-linux-gnu with no regressions.
> OK to apply?
Ping. : )
Regards
Ken
next prev parent reply other threads:[~2010-11-02 8:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 12:58 [patch] GNU vector unop support Ken Werner
2010-09-28 16:04 ` Ken Werner
[not found] ` <20100930185634.GC6213@adacore.com>
2010-10-01 17:45 ` [patch] fix pre-/post- in-/decrement Ken Werner
2010-10-04 13:01 ` Ulrich Weigand
2010-10-04 19:47 ` Ken Werner
2010-10-04 20:45 ` Daniel Jacobowitz
2010-10-04 21:58 ` Ulrich Weigand
2010-10-04 22:59 ` Daniel Jacobowitz
2010-10-04 23:25 ` Ulrich Weigand
2010-10-05 1:17 ` Daniel Jacobowitz
2010-10-05 13:28 ` Ulrich Weigand
2010-10-05 13:42 ` Daniel Jacobowitz
2010-10-06 18:59 ` [rfc] Fix value_assign return value (Re: [patch] fix pre-/post- in-/decrement) Ulrich Weigand
2010-10-26 13:42 ` Daniel Jacobowitz
2010-12-01 16:51 ` Ulrich Weigand
2010-10-06 20:55 ` [patch] fix pre-/post- in-/decrement Vladimir Prus
2010-10-07 12:38 ` Ken Werner
2010-10-12 23:00 ` Tom Tromey
2010-10-13 8:45 ` Andreas Schwab
2010-10-13 9:23 ` Ken Werner
2010-10-13 16:07 ` Daniel Jacobowitz
2010-10-13 19:01 ` Tom Tromey
2010-10-19 7:38 ` Ken Werner
2010-11-02 8:23 ` Ken Werner [this message]
2010-11-02 20:31 ` Tom Tromey
2010-11-03 13:52 ` Ken Werner
2010-10-04 20:52 ` [patch] GNU vector unop support Ken Werner
2010-10-06 23:27 ` Joel Brobecker
2010-10-07 16:23 ` Ken Werner
2010-11-03 14:07 ` Ken Werner
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=201011020923.34670.ken@linux.vnet.ibm.com \
--to=ken@linux.vnet.ibm.com \
--cc=brobecker@adacore.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
--cc=uweigand@de.ibm.com \
/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