public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Introduce and use disassembly_flags
Date: Mon, 20 Feb 2017 20:40:00 -0000	[thread overview]
Message-ID: <8334f0f6-d478-662d-ec7f-546bc37b3199@codesourcery.com> (raw)
In-Reply-To: <7e414de440d77d9a11aac61eabcb9481@polymtl.ca>

On 02/20/2017 02:37 PM, Simon Marchi wrote:
> On 2017-02-20 15:22, Luis Machado wrote:
>> On 02/18/2017 01:23 PM, Simon Marchi wrote:
>>> On 2017-02-13 15:02, Luis Machado wrote:
>>>> Also, should we consider converting DISASSEMBLY_SOURCE_DEPRECATED or
>>>> should we let it go? It was introduced in 2015.
>>>
>>> What do you mean by "converting"?
>>
>> Since it is deprecated, do we need to convert/carry it over to the
>> enum definitions? If not, it could be dropped.
>>
>> I haven't looked much into this, so i'm not sure if we're still
>> considering it acceptable to use this deprecated flag.
>
> This flag corresponds to the /m modifier of the disas command, which
> itself has been deprecated in 7.11.  As long as we don't remove the
> modifier, we can't remove the flag.

Fair enough. Thanks for the info.

  reply	other threads:[~2017-02-20 20:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-11  3:12 Simon Marchi
2017-02-12 22:35 ` Yao Qi
2017-02-18 19:20   ` Simon Marchi
2017-02-18 19:30     ` Yao Qi
2017-02-13 20:03 ` Luis Machado
2017-02-18 19:23   ` Simon Marchi
2017-02-20 20:23     ` Luis Machado
2017-02-20 20:37       ` Simon Marchi
2017-02-20 20:40         ` Luis Machado [this message]
2017-02-15 11:15 ` Pedro Alves
2017-02-18 19:27   ` Simon Marchi

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=8334f0f6-d478-662d-ec7f-546bc37b3199@codesourcery.com \
    --to=lgustavo@codesourcery.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).