From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/6] Remove OP_LABELED.
Date: Fri, 02 Nov 2012 16:51:00 -0000 [thread overview]
Message-ID: <5093F9EC.6020502@redhat.com> (raw)
In-Reply-To: <87vcdoosr2.fsf@fleche.redhat.com>
On 11/02/2012 04:48 PM, Tom Tromey wrote:
>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
>
> Pedro> I have no idea if the OP_LABELED implementation was a good basis
> Pedro> for this or not.
>
> We can stick a link to this discussion in the PR, in case somebody wants
> to look.
Yep, that was the plan. I'll take that as confirmation that designated
initializers are not known to be, or should be working through some
other means. :-) Thanks.
--
Pedro Alves
next prev parent reply other threads:[~2012-11-02 16:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 7:47 [PATCH 0/6] Remove unused operator OP_LABELED Yao Qi
2012-11-01 7:47 ` [PATCH 5/6] Indentation Yao Qi
2012-11-01 15:45 ` Tom Tromey
2012-11-01 7:47 ` [PATCH 3/6] Remove 'variantno' Yao Qi
2012-11-01 15:44 ` Tom Tromey
2012-11-01 7:47 ` [PATCH 1/6] Remove OP_LABELED Yao Qi
2012-11-01 15:41 ` Tom Tromey
2012-11-02 16:43 ` Pedro Alves
2012-11-02 16:49 ` Tom Tromey
2012-11-02 16:51 ` Pedro Alves [this message]
2012-11-02 17:09 ` Tom Tromey
2012-11-02 17:25 ` Pedro Alves
2012-11-01 7:47 ` [PATCH 2/6] Update comment of evaluate_struct_tuple Yao Qi
2012-11-01 15:42 ` Tom Tromey
2012-11-01 7:47 ` [PATCH 6/6] Test nested struct assign Yao Qi
2012-11-01 15:47 ` Tom Tromey
2012-11-01 7:47 ` [PATCH 4/6] Remove 'substruct_type' and 'subfieldno' Yao Qi
2012-11-01 15:44 ` Tom Tromey
2012-11-01 15:47 ` [PATCH 0/6] Remove unused operator OP_LABELED Tom Tromey
2012-11-02 0:20 ` [committed]: " Yao Qi
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=5093F9EC.6020502@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
--cc=yao@codesourcery.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