From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4 1/2] Add back gdb_pretty_print_insn
Date: Thu, 02 Feb 2017 00:00:00 -0000 [thread overview]
Message-ID: <4766907f-6456-5acc-0b4e-9876d65c0a9c@redhat.com> (raw)
In-Reply-To: <4930d51bf36a1182279d972150bce661@polymtl.ca>
On 02/01/2017 06:25 PM, Simon Marchi wrote:
> I'll just mention it so we hopefully don't duplicate work, looking at
> your patch has prompted me to start a patch adding a "disassembly_flags"
> enum type.
>
> https://github.com/simark/binutils-gdb/tree/disas-flags
Nice, thanks.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-02-02 0:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 0:30 [PATCH v4 0/2] Eliminate cleanups & make ui_file a C++ class hierarchy Pedro Alves
2017-02-01 0:30 ` [PATCH v4 1/2] Add back gdb_pretty_print_insn Pedro Alves
2017-02-01 17:01 ` Luis Machado
2017-02-01 18:10 ` Simon Marchi
2017-02-01 18:26 ` Simon Marchi
2017-02-02 0:00 ` Pedro Alves [this message]
2017-02-01 20:02 ` Pedro Alves
2017-02-01 20:31 ` Pedro Alves
2017-02-01 23:50 ` Pedro Alves
2017-02-02 1:20 ` Simon Marchi
2017-02-02 11:37 ` [pushed] Reuse buffers across gdb_pretty_print_insn calls (Re: [PATCH v4 1/2] Add back gdb_pretty_print_insn) Pedro Alves
2017-02-01 0:31 ` [PATCH v4 2/2] Eliminate make_cleanup_ui_file_delete / make ui_file a class hierarchy Pedro Alves
2017-02-01 17:37 ` Luis Machado
2017-02-01 22:49 ` Pedro Alves
2017-02-01 23:24 ` Luis Machado
2017-02-02 0:02 ` Pedro Alves
2017-02-27 19:43 ` Edjunior Barbosa Machado
2017-03-07 14:02 ` 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=4766907f-6456-5acc-0b4e-9876d65c0a9c@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).