Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>, Jiong Wang <jiong.wang@foss.arm.com>
Cc: GDB <gdb-patches@sourceware.org>,
	Binutils <binutils@sourceware.org>,
	       "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
Subject: Re: [1/9][RFC][DWARF] Reserve three DW_OP numbers in vendor extension space
Date: Tue, 03 Jan 2017 15:21:00 -0000	[thread overview]
Message-ID: <49b458a3-861b-cfcb-8c9f-7e49641b5fcc@redhat.com> (raw)
In-Reply-To: <CAH=s-PMQLX0iAthpTBCA+tcaFT=pf=5cMt30erAc_83Qj0DHkg@mail.gmail.com>

Hi Guys,

>>   As this patch has got approve from GCC, is it OK to install into
>> binutils-gdb master?
>>
>>   My understanding is "include/dwarf2.def" is shared between GDB and
>> Binutils.
> 
> "include/dwarf2.def" in binutils-gdb is a copy from gcc, as the comments in
> the top explain "This file is part of GCC.".  Since the patch was approved in
> GCC, you need to commit the patch to GCC repository, and sync
> "include/dwarf2.def" from GCC repo to binutils-gdb repo.  The last sync
> is done by Nick https://sourceware.org/ml/binutils/2015-09/msg00330.html

I have now sync'ed the binutils copy with the current master copy in the gcc
repository.

Jiong - if you want to apply your patch to both the gcc and binutils repository,
then this is OK with me.

Cheers
  Nick


  reply	other threads:[~2017-01-03 15:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c9da17a6-c3de-4466-c023-4e4ddbe38efb@foss.arm.com>
2016-11-11 18:22 ` Jiong Wang
2016-11-11 19:39   ` Jakub Jelinek
2016-11-15 16:00     ` Jiong Wang
2016-11-15 16:18       ` Jakub Jelinek
2016-11-15 16:48         ` Jiong Wang
2016-11-15 19:25           ` Richard Earnshaw (lists)
2016-11-16 10:00             ` Jiong Wang
     [not found]               ` <1479304496.14569.256.camel@redhat.com>
2016-11-16 14:02                 ` Jakub Jelinek
2016-11-30 11:15                   ` Jiong Wang
2016-11-30 18:25                     ` Yao Qi
2016-12-12 13:40                     ` [Ping~][1/9][RFC][DWARF] " Jiong Wang
2016-12-19 13:59                       ` [Ping^2][1/9][RFC][DWARF] " Jiong Wang
2016-12-28 18:21                         ` [Ping^3][1/9][RFC][DWARF] " Jiong Wang
2016-12-28 19:54                     ` [1/9][RFC][DWARF] " Cary Coutant
2017-01-03  9:32                       ` Jiong Wang
2017-01-03 10:10                       ` Jiong Wang
2017-01-03 10:57                         ` Yao Qi
2017-01-03 15:21                           ` Nick Clifton [this message]
2017-01-03 17:47                             ` Yao Qi
2016-11-30 21:44                   ` Cary Coutant
2016-12-01 10:42                     ` Richard Earnshaw (lists)
2016-12-01 11:09                       ` Jiong Wang
2016-11-15 16:51         ` Jiong Wang
2016-12-28 19:48     ` Cary Coutant

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=49b458a3-861b-cfcb-8c9f-7e49641b5fcc@redhat.com \
    --to=nickc@redhat.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jiong.wang@foss.arm.com \
    --cc=qiyaoltc@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