public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: sje@cup.hp.com
Cc: Steven Bosscher <stevenb.gcc@gmail.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [ia64] Cleanup unwind info annotations
Date: Fri, 24 Sep 2010 15:03:00 -0000	[thread overview]
Message-ID: <4C9BC918.6050408@redhat.com> (raw)
In-Reply-To: <1285276559.9806.96.camel@hpsje.cup.hp.com>

On 09/23/2010 02:15 PM, Steve Ellcey wrote:
> I'm confused.  Which patch are we talking about here?  Do we think
> things will work on IA64 HP-UX now?  My comments about testing were on
> sources without your patch included, I was just confirming that I could
> build IA64 Linux (without your patch and without any local changes)
> without getting the diff errors that you got during bootstrap.

Just the patch at the top of this thread (gcc.gnu.org is down atm,
or I'd give you a link).  It rearranges the generation of the unwind
info so that there's none of the guesswork that caused failures on
hpux when the TARGET_UNWIND_INFO patch was applied.

I believe that with the unwind-info cleanup patch applied, that the
subsequent TARGET_UNWIND_INFO patch will work on ia64-hpux, yes.


r~

  reply	other threads:[~2010-09-23 22:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22  8:10 Richard Henderson
2010-09-22  8:38 ` Steven Bosscher
2010-09-22 22:12   ` Richard Henderson
2010-09-22 22:56     ` Steve Ellcey
2010-09-24  0:35       ` Richard Henderson
2010-09-24 13:09         ` Richard Henderson
2010-09-24 11:05           ` Steve Ellcey
2010-09-24 15:03             ` Richard Henderson [this message]
2010-09-24 11:56               ` Steve Ellcey
2010-09-25  9:51               ` Steve Ellcey
2010-09-25 14:55                 ` Richard Henderson

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=4C9BC918.6050408@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sje@cup.hp.com \
    --cc=stevenb.gcc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).