Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Aktemur, Tankut Baris via Gdb-patches" <gdb-patches@sourceware.org>
To: Simon Marchi <simark@simark.ca>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [gdb-10-branch] opcodes/csky: return the default disassembler when there is no bfd
Date: Thu, 22 Oct 2020 15:23:03 +0000	[thread overview]
Message-ID: <SN6PR11MB289399B11E0038ACFABD7921C41D0@SN6PR11MB2893.namprd11.prod.outlook.com> (raw)
In-Reply-To: <6493685c-65fa-21c7-831d-c93ee60e54ea@simark.ca>

On Thursday, October 22, 2020 5:00 PM, Simon Marchi wrote:
> On 2020-10-22 8:39 a.m., Aktemur, Tankut Baris via Gdb-patches wrote:
> > Hi,
> >
> > The commit
> >
> >   commit c568ac5ff708eebf6ef424e5863d3dbd874a3f62
> >   Author: Andrew Burgess <andrew.burgess@embecosm.com>
> >   Date:   Wed Sep 16 10:12:39 2020 +0100
> >     opcodes/csky: return the default disassembler when there is no bfd
> >
> > fixes many gdb.base/all-architectures-2.exp test cases.  I propose applying
> > it to gdb-10-branch, too.
> >
> > -Baris
> 
> I just gave it a try and saw the failures on the gdb-10-branch.  I agree, please
> go ahead and push it to the release branch.
> 
> Simon

Cherry-picked and pushed to gdb-10-branch.

Thanks
-Baris


Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

      reply	other threads:[~2020-10-22 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 12:39 Aktemur, Tankut Baris via Gdb-patches
2020-10-22 15:00 ` Simon Marchi
2020-10-22 15:23   ` Aktemur, Tankut Baris via Gdb-patches [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=SN6PR11MB289399B11E0038ACFABD7921C41D0@SN6PR11MB2893.namprd11.prod.outlook.com \
    --to=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --cc=tankut.baris.aktemur@intel.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