Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Shahab Vahedi <Shahab.Vahedi@synopsys.com>
To: Luis Machado <luis.machado@linaro.org>,
	Shahab Vahedi	<shahab.vahedi@gmail.com>,
	Christian Biesinger <cbiesinger@google.com>
Cc: Shahab Vahedi <Shahab.Vahedi@synopsys.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>,
	Francois Bedard <Francois.Bedard@synopsys.com>,
	Andrew Burgess <andrew.burgess@embecosm.com>
Subject: Re: [Regression] [PATCH] Do not print empty-group regs when printing general ones
Date: Wed, 04 Mar 2020 15:21:00 -0000	[thread overview]
Message-ID: <7fe1214a-cf7e-2f02-5f9d-92368d3aedbe@synopsys.com> (raw)
In-Reply-To: <33535485-cd54-6817-6e09-7f9de835766e@linaro.org>

Hi Luis,

On 3/4/20 2:16 PM, Luis Machado wrote:
> Should we revert this for now then, and address this problem with an upcoming patch?

Since this breaks the backward compatibility, I agree. Thank you for looking into this.


Cheers,
-- 
Shahab

  reply	other threads:[~2020-03-04 15:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 17:29 Shahab Vahedi
2020-01-20 23:04 ` Andrew Burgess
     [not found] ` <CH2PR12MB3847E492663E7997CFAB1741A6070@CH2PR12MB3847.namprd12.prod.outlook.com>
2020-02-28 13:08   ` [Regression] " Luis Machado
2020-02-28 13:22     ` Christian Biesinger via gdb-patches
     [not found]       ` <9c256b27-4a00-8830-46e2-934922e39cc2@linaro.org>
2020-02-28 13:36         ` Shahab Vahedi
2020-02-28 13:51           ` Luis Machado
2020-02-28 14:08             ` Shahab Vahedi
2020-02-28 14:11               ` Christian Biesinger via gdb-patches
2020-02-28 14:15                 ` Shahab Vahedi
2020-03-04 13:17                   ` Luis Machado
2020-03-04 15:21                     ` Shahab Vahedi [this message]
2020-03-04 16:14                       ` Luis Machado

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=7fe1214a-cf7e-2f02-5f9d-92368d3aedbe@synopsys.com \
    --to=shahab.vahedi@synopsys.com \
    --cc=Claudiu.Zissulescu@synopsys.com \
    --cc=Francois.Bedard@synopsys.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.org \
    --cc=shahab.vahedi@gmail.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