From: Pedro Alves <palves@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [RFC] Fix ptype bug actually exercised in userdef.exp
Date: Wed, 13 Feb 2013 20:35:00 -0000 [thread overview]
Message-ID: <511BF927.4060008@redhat.com> (raw)
In-Reply-To: <20130213203131.30816.4686.stgit@brno.lan>
On 02/13/2013 08:31 PM, Pedro Alves wrote:
> + if (TYPE_CODE (type) == TYPE_CODE_REF)
> + return value_zero (lookup_pointer_type (TYPE_TARGET_TYPE (type)), not_lval);
> + else if (VALUE_LVAL (x) == lval_memory || value_must_coerce_to_target (x))
> + return value_zero (lookup_pointer_type (value_type (x)), not_lval);
> else
Whoops, too long lines. Pretend there's a newline before each of those
"not_lval", like in the present code...
--
Pedro Alves
next prev parent reply other threads:[~2013-02-13 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 20:31 Pedro Alves
2013-02-13 20:35 ` Pedro Alves [this message]
2013-02-13 20:57 ` Tom Tromey
2013-02-14 12:53 ` Pedro Alves
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=511BF927.4060008@redhat.com \
--to=palves@redhat.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