public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tamar Christina <Tamar.Christina@arm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"brobecker@adacore.com" <brobecker@adacore.com>
Cc: nd <nd@arm.com>
Subject: RE: Backport of patch to gdb 8.0 branch.
Date: Thu, 17 May 2018 13:23:00 -0000	[thread overview]
Message-ID: <HE1PR08MB0540E6EAB54BC6F4619C8B16FF910@HE1PR08MB0540.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <HE1PR08MB05406AFA84C5CEB1A5E58DCEFF930@HE1PR08MB0540.eurprd08.prod.outlook.com>

Hi Joel,

I'm looking to backport this change to fix builds with debug trace on the gdb-8.0 branch.

It's been backported to the binutils-2.30 branch already.

Kind Regards,
Tamar

> -----Original Message-----
> From: gdb-patches-owner@sourceware.org <gdb-patches-
> owner@sourceware.org> On Behalf Of Tamar Christina
> Sent: Tuesday, May 15, 2018 18:00
> To: gdb-patches@sourceware.org
> Cc: nd <nd@arm.com>
> Subject: Backport of patch to gdb 8.0 branch.
> 
> Hi All,
> 
> I'm looking for a backport of
> https://sourceware.org/git/gitweb.cgi?p=binutils-
> gdb.git;a=commit;h=957f6b39cab6cac0e4c54e650c7f75109544ac1d
> to the gdb-8.0-branch. The patch allows building with full debug trace
> enabled on AArch64.
> 
> Ok for gdb-8.0-branch?
> 
> Thanks,
> Tamar

  reply	other threads:[~2018-05-17 10:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <HE1PR08MB0540BEEB7FDED47D0FE9D6DCFF930@HE1PR08MB0540.eurprd08.prod.outlook.com>
2018-05-16 13:54 ` Tamar Christina
2018-05-17 13:23   ` Tamar Christina [this message]
2018-05-17 19:39   ` Joel Brobecker
2018-05-18 10:57     ` Tamar Christina
2018-05-18 18:50       ` Joel Brobecker

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=HE1PR08MB0540E6EAB54BC6F4619C8B16FF910@HE1PR08MB0540.eurprd08.prod.outlook.com \
    --to=tamar.christina@arm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).