Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Martin Galvan <martin.galvan@tallertechnologies.com>
Cc: gdb-patches <gdb-patches@sourceware.org>,
	Tom Tromey <tom@tromey.com>,
	       Daniel Gutson <daniel.gutson@tallertechnologies.com>
Subject: Re: [PATCH] c_value_print: Revert 'val' to a reference for TYPE_CODE_STRUCT
Date: Wed, 27 Apr 2016 13:39:00 -0000	[thread overview]
Message-ID: <5720C0F6.9060806@redhat.com> (raw)
In-Reply-To: <CAOKbPbY_NuRyB_HJsLHLJjXT_UsSWFJxwuVpdxxUnLFxkBvSLQ@mail.gmail.com>

On 04/27/2016 02:21 PM, Martin Galvan wrote:
> On Wed, Apr 27, 2016 at 7:01 AM, Pedro Alves <palves@redhat.com> wrote:
>> What's the motivation behind this?  Does it change anything user visible?
> 
> AFAIK not directly, but I'm going to need it for the synthetic reference bug
> fix.

I see. 

> Since this is an isolated change I thought I could send it for
> review now.

Since you didn't mention whether the change had any user-visible
impact, I was left wondering if we could add a testcase to
the testsuite that exposes the need for the change.  From the original
log it kind of sounded like it would be possible.

It's better to be explicit in such cases, and say something like,
"this has no effect currently, so can be seen as a small code
cleanup, but once we do X, we'll print the wrong thing", or some such,
and mention that this causes no testsuite regressions, in the 
email/commit log.

The code change is OK.

Thanks,
Pedro Alves


  reply	other threads:[~2016-04-27 13:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 21:48 Martin Galvan
2016-04-27 10:01 ` Pedro Alves
2016-04-27 13:22   ` Martin Galvan
2016-04-27 13:39     ` Pedro Alves [this message]
2016-04-27 15:10       ` Martin Galvan

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=5720C0F6.9060806@redhat.com \
    --to=palves@redhat.com \
    --cc=daniel.gutson@tallertechnologies.com \
    --cc=gdb-patches@sourceware.org \
    --cc=martin.galvan@tallertechnologies.com \
    --cc=tom@tromey.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