Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA 1/3] language-specific read_var_value for Ada renamings
Date: Fri, 02 Mar 2012 19:33:00 -0000	[thread overview]
Message-ID: <20120302193332.GD2853@adacore.com> (raw)
In-Reply-To: <1330546034-27156-2-git-send-email-brobecker@adacore.com>

> gdb/ChangeLog:
> 
>         * language.h (struct language_defn): New "method" la_read_var_value.
>         * findvar.c: #include "language.h".
>         (default_read_var_value): Renames read_var_value.  Rewrite
>         function description.
>         (read_var_value): New function.
>         * value.h (default_read_var_value): Add prototype.
>         * ada-lang.c (ada_read_renaming_var_value, ada_read_var_value):
>         New functions.
>         (ada_language_defn): Add entry for la_read_var_value.
>         * c-lang.c, d-lang.c, f-lang.c, jv-lang.c, language.c,
>         * m2-lang.c, objc-lang.c, opencl-lang.c, p-lang.c: Update
>         language_defn structures to add entry for new la_read_var_value
>         field.

Now checked in.


-- 
Joel


  parent reply	other threads:[~2012-03-02 19:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 20:07 Better support for Ada renamings in "info locals" output Joel Brobecker
2012-02-29 20:07 ` [PATCH 3/3] Testcase: "info locals" with Ada renamings Joel Brobecker
2012-03-02 19:34   ` Joel Brobecker
2012-02-29 20:07 ` [RFA 1/3] language-specific read_var_value for " Joel Brobecker
2012-03-01 19:52   ` Tom Tromey
2012-03-01 22:58     ` Joel Brobecker
2012-03-02 14:20       ` Tom Tromey
2012-03-02 19:33   ` Joel Brobecker [this message]
2012-02-29 20:16 ` [commit/Ada 2/3] processId: Do not modify already encoded IDs Joel Brobecker

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=20120302193332.GD2853@adacore.com \
    --to=brobecker@adacore.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