public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [CFT][PATCH 0/6] Move dwarf2 cfi creation to a new pass
Date: Fri, 08 Jul 2011 02:32:00 -0000	[thread overview]
Message-ID: <4E164E38.9030206@redhat.com> (raw)
In-Reply-To: <4E14EC99.40607@codesourcery.com>

On 07/06/2011 04:15 PM, Bernd Schmidt wrote:
> Ok for the bits that aren't from me anyway, once you're satisfied it's
> sufficiently tested.

I committed this series.

I tested x86_64, ia64, and ppc64-linux; Iain tested i686-darwin9;
and you tested arm-linux.  Excluding vax, that covered all the
targets that required changes before this series went in.

Hopefully I'll have another series soon that includes your change
to cfg-like propagation.


r~

  parent reply	other threads:[~2011-07-08  0:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-03 20:03 Richard Henderson
2011-07-03 20:03 ` [PATCH 2/6] dwarf2out: Move insn scanning out of final.c Richard Henderson
2011-07-03 20:03 ` [PATCH 5/6] dwarf2: Extract cfi creation to a new pass Richard Henderson
2011-07-03 20:03 ` [PATCH 3/6] dwarf2out: Emit NOTE_INSN_CFI_* both with and without cfi-asm Richard Henderson
2011-07-03 20:03 ` [PATCH 4/6] dwarf2out: Convert fde_table to a VEC Richard Henderson
2011-07-03 20:03 ` [PATCH 6/6] Dump NOTE_INSN_CFI notes Richard Henderson
2011-07-03 20:04 ` [PATCH 1/6] dwarf2out: Split CFI construction routines into a new file Richard Henderson
2011-07-06 23:23 ` [CFT][PATCH 0/6] Move dwarf2 cfi creation to a new pass Bernd Schmidt
2011-07-07  8:10   ` Iain Sandoe
2011-07-08  2:32   ` Richard Henderson [this message]
2011-07-07 21:51 ` Bernd Schmidt

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=4E164E38.9030206@redhat.com \
    --to=rth@redhat.com \
    --cc=bernds@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    /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).