From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gcc-patches@gcc.gnu.org, Paolo Bonzini <bonzini@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: Mon, 20 Jun 2011 15:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1106201523080.16125@digraph.polyomino.org.uk> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2011-06-20 15:28 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 [this message]
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
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.1106201523080.16125@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).