From: Luis Machado <lgustavo@codesourcery.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix mi "-var-create" regression
Date: Thu, 11 Oct 2012 22:10:00 -0000 [thread overview]
Message-ID: <507743DF.1020907@codesourcery.com> (raw)
In-Reply-To: <m3lifcbrq6.fsf@redhat.com>
On 10/11/2012 06:53 PM, Sergio Durigan Junior wrote:
> On Wednesday, October 10 2012, Luis Gustavo wrote:
>
>> Hi,
>
> Hey Luis :-)
Hey!
> 1) I believe you could remove some of the parentheses in the `if'
> above. Something like:
>
> if ((TYPE_CODE (result) == TYPE_CODE_PTR
> || TYPE_CODE (result) == TYPE_CODE_REF)
> && TYPE_TARGET_TYPE (result) != NULL
> && TYPE_CODE (TYPE_TARGET_TYPE (result)) != TYPE_CODE_VOID)
>
> would have the same effect, right?
Ah, of course. Thanks for noticing that.
>
> 2) Would it be possible to provide a testcase for this issue? Not sure
> if it's really needed, but I guess it won't hurt :-). Of course, if
> some maintainer thinks it's useless, then please disconsider the idea
> right away.
I thought about this for a while, and the best testing mechanism seems
to be just turning the "print object" option on by default and running
the entire testsuite, otherwise this test will be very specific to the
-var-create mechanism.
value_actual_type is called from 3 different places IIRC.
If we're thinking about a regression coverage test, then i agree that a
test is appropriate in this case, so we can be sure it will never happen
again.
Luis
next prev parent reply other threads:[~2012-10-11 22:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 20:05 Luis Gustavo
2012-10-11 21:53 ` Sergio Durigan Junior
2012-10-11 22:10 ` Luis Machado [this message]
2012-10-17 17:29 ` Tom Tromey
2012-10-12 19:57 ` Marc Khouzam
2012-10-14 17:18 ` Joel Brobecker
2012-10-15 12:21 ` Luis Machado
2012-10-18 1:13 ` Tom Tromey
2012-10-19 13:14 ` Luis Machado
2012-10-28 22:44 ` Luis Machado
2012-10-30 20:36 ` Tom Tromey
2012-11-14 19:21 ` Luis Machado
2012-11-15 16:44 ` Marc Khouzam
2012-11-15 17:48 ` Joel Brobecker
2012-11-15 18:47 ` Tom Tromey
2012-11-15 20:54 ` Marc Khouzam
2012-11-15 21:13 ` Tom Tromey
2012-11-15 23:28 ` Luis Machado
2012-11-16 0:50 ` Marc Khouzam
2012-11-16 2:10 ` Luis Machado
2012-11-29 20:11 ` Andreas Schwab
2012-11-29 21:07 ` Joel Brobecker
2012-11-30 2:13 ` Luis Machado
2012-12-07 2:48 ` Joel Brobecker
2012-12-07 2:51 ` Luis Machado
2012-12-26 12:31 ` Luis Machado
2013-01-03 3:46 ` Joel Brobecker
2013-01-03 12:30 ` Luis Machado
2013-01-03 12:38 ` 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=507743DF.1020907@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@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