From: "H.J. Lu" <hjl.tools@gmail.com>
To: Daniel Jacobowitz <dan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Add support for <struct> and <flags> in target descriptions
Date: Mon, 01 Mar 2010 03:06:00 -0000 [thread overview]
Message-ID: <6dc9ffc81002281906p48f4d672ydc95d4c354944d96@mail.gmail.com> (raw)
In-Reply-To: <20100301024557.GU9493@caradoc.them.org>
On Sun, Feb 28, 2010 at 6:45 PM, Daniel Jacobowitz <dan@codesourcery.com> wrote:
> On Sun, Feb 28, 2010 at 04:56:50PM -0800, H.J. Lu wrote:
>> This patch makes it to work. However, there is no equivalent of
>>
>> append_flags_type_flag (type, 1, NULL);
>
> Is this to separate unknown bits (which should be displayed) from
> don't-care bits (which are hidden)?
>
I believe so.
--
H.J.
prev parent reply other threads:[~2010-03-01 3:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 16:45 Daniel Jacobowitz
2010-02-22 19:32 ` Eli Zaretskii
2010-03-01 0:15 ` H.J. Lu
2010-03-01 0:57 ` H.J. Lu
2010-03-01 2:20 ` H.J. Lu
2010-03-01 17:20 ` Daniel Jacobowitz
2010-03-01 17:26 ` H.J. Lu
2010-03-01 2:46 ` Daniel Jacobowitz
2010-03-01 3:06 ` H.J. Lu [this message]
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=6dc9ffc81002281906p48f4d672ydc95d4c354944d96@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=dan@codesourcery.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