From: Ken Werner <ken@linux.vnet.ibm.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] initial OpenCL C language support
Date: Tue, 26 Oct 2010 13:05:00 -0000 [thread overview]
Message-ID: <201010261505.07587.ken@linux.vnet.ibm.com> (raw)
In-Reply-To: <m3mxq1q4bd.fsf@fleche.redhat.com>
On Tuesday, October 26, 2010 12:45:58 am Tom Tromey wrote:
> >>>>> "Ken" == Ken Werner <ken@linux.vnet.ibm.com> writes:
> Ken> This patch implements initial GDB support for the OpenCL C
> Ken> Programming Language. Since OpenCL is based on C99 I tried to reuse
> Ken> GDBs C infrastructure where possible (expression parser, printing
> Ken> routines, etc).
>
> I have been skimming this patch a bit and I think it is very good.
>
> I don't have time to fully review it right now, as I'm at the GCC
> Summit.
Thanks for having a look at the patch.
Have fun on the summit! : )
> > But I did notice one thing:
>
> Ken> +/* Expression evaluator for the OpenCL. Most operations are
> delegated to Ken> + evaluate_subexp_standard; see that function for a
> description of the Ken> + arguments. */
> Ken> +static struct value *
> Ken> +evaluate_subexp_opencl (struct type *expect_type, struct expression
> *exp, Ken> + int *pos, enum noside noside)
> [...]
> Ken> + return evaluate_subexp_standard (expect_type, exp, pos, noside);
>
> I think this ought to call the C-specific evaluate_subexp_c.
> You'll need to at least make this non-static, maybe even rename it.
>
> I believe that without this some forms of string constants will not work
> properly.
My understanding is that the only additional functionality of
evaluate_subexp_c is to provide wide character support which is not available
in OpenCL C. Of course calling evaluate_subexp_c won't hurt since
evaluate_subexp_standard gets called in most cases but I don't see where the
OpenCL support could benefit from doing so. Do you have an example?
Regards
Ken
next prev parent reply other threads:[~2010-10-26 13:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 17:21 Ken Werner
2010-10-25 22:41 ` Tom Tromey
2010-10-26 13:05 ` Ken Werner [this message]
2010-10-26 13:44 ` Tom Tromey
2010-10-26 16:02 ` Ken Werner
2010-10-26 17:49 ` Eli Zaretskii
2010-10-26 19:58 ` Joel Brobecker
2010-10-26 20:03 ` Joel Brobecker
2010-10-27 13:36 ` Ken Werner
2010-11-02 19:23 ` Joel Brobecker
2010-11-03 13:03 ` Ken Werner
2010-11-03 15:27 ` Joel Brobecker
2010-11-04 15:39 ` Ken Werner
2010-11-04 17:48 ` Eli Zaretskii
2010-11-05 14:21 ` Ken Werner
2010-11-05 14:39 ` Ken Werner
2010-10-27 19:04 ` Jan Kratochvil
2010-10-27 19:21 ` Pedro Alves
2010-10-27 21:01 ` Ken Werner
2010-11-02 16:52 ` [doc RFA] Switch to GCC coding style [Re: [patch] initial OpenCL C language support] Jan Kratochvil
2010-11-02 17:04 ` Doug Evans
2010-11-02 17:23 ` Jan Kratochvil
2010-11-02 17:29 ` Doug Evans
2010-11-02 19:21 ` Eli Zaretskii
2010-11-02 19:29 ` Joel Brobecker
2010-11-08 12:50 ` Jan Kratochvil
2010-11-08 16:11 ` Joel Brobecker
2010-11-08 16:38 ` Mark Kettenis
2010-11-08 16:43 ` Joel Brobecker
2010-11-08 16:54 ` Pedro Alves
2010-11-08 18:36 ` Joel Brobecker
2010-11-02 18:01 ` Joel Brobecker
2010-11-02 18:10 ` [doc RFA] Switch to GCC coding style Jan Kratochvil
2010-11-02 18:20 ` Doug Evans
2010-11-02 18:58 ` Joel Brobecker
2010-11-02 19:19 ` Doug Evans
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=201010261505.07587.ken@linux.vnet.ibm.com \
--to=ken@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).