public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Steve Ellcey <sje@cup.hp.com>, Douglas Rupp <rupp@gnat.com>
Subject: Re: CFT: Move unwinder to toplevel libgcc
Date: Tue, 05 Jul 2011 09:35:00 -0000	[thread overview]
Message-ID: <CFF4CC67-6F1B-4B18-933E-EF40B26E62EC@adacore.com> (raw)
In-Reply-To: <yddbox9ncjb.fsf_-_@manam.CeBiTec.Uni-Bielefeld.DE>


On Jul 4, 2011, at 8:09 PM, Rainer Orth wrote:

> "Joseph S. Myers" <joseph@codesourcery.com> writes:
> 
>> On Mon, 20 Jun 2011, Rainer Orth wrote:
>> 
>>> * Move all remaining unwinder-only macros to libgcc: UNW_IVMS_MODE,
>>>  MD_UNW_COMPATIBLE_PERSONALITY_P, MD_FROB_UPDATE_CONTEXT.
>> 
>> I don't see any sign of macros being poisoned in system.h.  For macros 
>> used in target-independent unwinder code - at least MD_FROB_UPDATE_CONTEXT 
>> - that used to be defined in the host tm.h but now no longer should be, I 
>> think poisoning in system.h is appropriate.
> 
> Done in the updated patch below.  Given that the other two are ia64 only
> and not documented in md.texi, I don't think they need to be poisoned.
> 
> Otherwise, the patch is unchanged from the original submission:
> 
> 	[build] Move unwinder to toplevel libgcc
> 	http://gcc.gnu.org/ml/gcc-patches/2011-06/msg01452.html
> 
> Unfortunately, it hasn't seen much comment.  I'm now looking for testers
> especially on platforms with more change and approval of those parts:
> 
> * Several IA-64 targets:
> 
> 	ia64*-*-linux*
>        ia64*-*-hpux*
>        ia64-hp-*vms*

For ia64-hp-vms, consider your patch approved if the parts for ia64 are.
In case of break, I will fix them.

Tristan.

  reply	other threads:[~2011-07-05  9:24 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 12:44 [build] " Rainer Orth
2011-06-20 15:21 ` Joseph S. Myers
2011-06-20 15:23   ` Rainer Orth
2011-06-20 15:37     ` Joseph S. Myers
2011-06-20 15:47       ` Rainer Orth
2011-07-04 18:10   ` CFT: " Rainer Orth
2011-07-05  9:35     ` Tristan Gingold [this message]
2011-07-07 13:11       ` Rainer Orth
2011-07-07 15:53         ` Steve Ellcey
2011-07-08 18:16           ` Rainer Orth
2011-07-07 16:48         ` Steve Ellcey
2011-07-08 18:24           ` Rainer Orth
2011-07-07 17:08         ` Steve Ellcey
2011-07-07 22:55           ` Steve Ellcey
2011-07-08 18:55             ` Rainer Orth
2011-07-08 20:18               ` Steve Ellcey
2011-07-12 17:24               ` Steve Ellcey
2011-07-12 17:40                 ` Rainer Orth
2011-07-12 17:42                   ` Steve Ellcey
2011-07-14  1:47                   ` Steve Ellcey
2011-07-15  9:38                     ` Rainer Orth
2011-07-18 12:07                       ` Rainer Orth
2011-07-18 17:50                         ` Steve Ellcey
2011-07-19 11:43                           ` Rainer Orth
2011-07-20 23:03                             ` Steve Ellcey
2011-07-22 15:36                               ` Rainer Orth
2011-07-22 18:56                                 ` Steve Ellcey
2011-07-22 19:03                                   ` Rainer Orth
2011-07-22 22:20                                     ` Steve Ellcey
2011-07-25 17:07                                       ` Rainer Orth
2011-06-29 10:05 ` [build] " Paolo Bonzini
2011-06-29 10:06   ` Rainer Orth
2011-06-29 11:29   ` Joseph S. Myers
2011-06-29 11:33     ` Paolo Bonzini
2011-06-29 12:40       ` Rainer Orth
2011-06-29 12:17     ` Rainer Orth

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=CFF4CC67-6F1B-4B18-933E-EF40B26E62EC@adacore.com \
    --to=gingold@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    --cc=rupp@gnat.com \
    --cc=sje@cup.hp.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).