public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
	gcc-patches@gcc.gnu.org,
	    Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
	    Ian Lance Taylor <iant@google.com>,
	Steve Ellcey <sje@cup.hp.com>,
	    Richard Earnshaw <richard.earnshaw@arm.com>,
	    Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>,
	    Nick Clifton <nickc@redhat.com>, Douglas Rupp <rupp@gnat.com>,
	    Tristan Gingold <gingold@adacore.com>,
	Mike Stump <mikestump@comcast.net>,
	    Kaz Kojima <kkojima@gcc.gnu.org>,
	David Edelsohn <dje.gcc@gmail.com>,
	    Sterling Augustine <augustine.sterling@gmail.com>,
	    Arnaud Charlet <charlet@adacore.com>,
	java-patches@gcc.gnu.org,
	    Nicola Pero <nicola.pero@meta-innovation.com>,
	libstdc++@gcc.gnu.org,
	    Richard Sandiford <rdsandiford@googlemail.com>
Subject: Re: [build] Move unwinder to toplevel libgcc
Date: Wed, 29 Jun 2011 10:42:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1106291037290.22294@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4E0AEEF0.7080406@gnu.org>

On Wed, 29 Jun 2011, Paolo Bonzini wrote:

> On 06/20/2011 02:24 PM, Rainer Orth wrote:
> > * The only unwinder-related macro I haven't moved is
> >    LIBGCC2_UNWIND_ATTRIBUTE.  It is only defined gcc/config/mips/mips.h.
> >    I suppose we would need a libgcc equivalent of tm.h for that,
> >    something I didn't want to attack at this point.
> 
> Something like the attached?

This patch appears to create a *second* file called libgcc_tm.h, so there 
is one created in gcc/ and one in libgcc/, which seems incredibly 
confusing.  By all means move the libgcc_tm.h logic to libgcc/ (though 
tm.h will need to continue to include libgcc_tm.h for the target, until 
the transition away from tm.h target macros in target code is complete and 
code includes libgcc_tm.h directly instead), but don't have two headers 
with the same name in different build directories.

I interpreted Rainer's comment as meaning that a 
libgcc/config/mips/mips-lib.h (or similar) file would need to be created 
and inserted in the right place in libgcc_tm_file for the large number of 
targets presently putting mips.h in tm_file.

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2011-06-29 10:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <yddfwn4pu5u.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
2011-06-20 15:11 ` Joseph S. Myers
2011-06-20 15:21   ` Rainer Orth
2011-06-20 15:28     ` Joseph S. Myers
2011-07-04 18:10   ` CFT: " Rainer Orth
2011-06-29  9:23 ` [build] " Paolo Bonzini
2011-06-29  9:33   ` Rainer Orth
2011-06-29 10:42   ` Joseph S. Myers [this message]
2011-06-29 11:29     ` Paolo Bonzini
2011-06-29 11:33       ` Rainer Orth
2011-06-29 11:31     ` 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=Pine.LNX.4.64.1106291037290.22294@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=augustine.sterling@gmail.com \
    --cc=bonzini@gnu.org \
    --cc=charlet@adacore.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gingold@adacore.com \
    --cc=iant@google.com \
    --cc=java-patches@gcc.gnu.org \
    --cc=kkojima@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=mikestump@comcast.net \
    --cc=nickc@redhat.com \
    --cc=nicola.pero@meta-innovation.com \
    --cc=ramana.radhakrishnan@arm.com \
    --cc=rdsandiford@googlemail.com \
    --cc=richard.earnshaw@arm.com \
    --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).