This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: [build] Move unwinder to toplevel libgcc
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>
- Cc: gcc-patches at gcc dot gnu dot org, Paolo Bonzini <bonzini at gnu dot org>, Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>, Ian Lance Taylor <iant at google dot com>, Steve Ellcey <sje at cup dot hp dot com>, Richard Earnshaw <richard dot earnshaw at arm dot com>, Ramana Radhakrishnan <ramana dot radhakrishnan at arm dot com>, Nick Clifton <nickc at redhat dot com>, Douglas Rupp <rupp at gnat dot com>, Tristan Gingold <gingold at adacore dot com>, Mike Stump <mikestump at comcast dot net>, Kaz Kojima <kkojima at gcc dot gnu dot org>, David Edelsohn <dje dot gcc at gmail dot com>, Sterling Augustine <augustine dot sterling at gmail dot com>, Arnaud Charlet <charlet at adacore dot com>, java-patches at gcc dot gnu dot org, Nicola Pero <nicola dot pero at meta-innovation dot com>, libstdc++ at gcc dot gnu dot org, Richard Sandiford <rdsandiford at googlemail dot com>
- Date: Mon, 20 Jun 2011 15:27:52 +0000 (UTC)
- Subject: Re: [build] Move unwinder to toplevel libgcc
- References: <yddfwn4pu5u.fsf@manam.CeBiTec.Uni-Bielefeld.DE> <Pine.LNX.4.64.1106201503490.16125@digraph.polyomino.org.uk> <yddhb7kmsvr.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
On Mon, 20 Jun 2011, Rainer Orth wrote:
> Certainly: your wiki entry gives a good overview. For the moment, I'll
> probably concentrate on the build side of things, though. I may attack
> gthr* stuff and fp-bit.[ch] next, both of which I can at least partially
> test on my targets.
fp-bit.[ch] has the interesting issue of FLOAT_BIT_ORDER_MISMATCH and
FLOAT_WORD_ORDER_MISMATCH being defined by makefile rules when it ought to
be possible to deduce that information from macros predefined by the
compiler. (See what I said in
<http://gcc.gnu.org/ml/gcc-patches/2010-11/msg02262.html> about the
meanings of those macros.)
dfp-bit.* and fixed-bit.* can probably move along with fp-bit.* (or
before, or after), and I don't think there are any complicated issues
around those files.
--
Joseph S. Myers
joseph@codesourcery.com