From: Paolo Bonzini <bonzini@gnu.org>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gcc-patches@gcc.gnu.org, Ian Lance Taylor <iant@google.com>,
Ben Elliston <bje@gnu.org>
Subject: Re: [build] Move dfp-bit support to toplevel libgcc
Date: Thu, 07 Jul 2011 10:42:00 -0000 [thread overview]
Message-ID: <4E158C76.1090503@gnu.org> (raw)
In-Reply-To: <yddsjqifkrw.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
On 07/07/2011 12:27 PM, Rainer Orth wrote:
> one might as
> well argue that they are generic and belong into libgcc itself.
Agreed.
> i[34567]86-*-linux* | i[34567]86-*-kfreebsd*-gnu | i[34567]86-*-knetbsd*-gnu | i[34567]86-*-gnu* | i[34567]86-*-kopensolaris*-gnu)
> extra_parts="$extra_parts crtprec32.o crtprec64.o crtprec80.o crtfastmath.o"
> - tmake_file="${tmake_file} i386/t-crtpc i386/t-crtfm"
> + tmake_file="${tmake_file} i386/t-crtpc i386/t-crtfm t-dfprules"
> md_unwind_header=i386/linux-unwind.h
> ;;
> x86_64-*-linux* | x86_64-*-kfreebsd*-gnu | x86_64-*-knetbsd*-gnu)
> extra_parts="$extra_parts crtprec32.o crtprec64.o crtprec80.o crtfastmath.o"
> - tmake_file="${tmake_file} i386/t-crtpc i386/t-crtfm"
> + tmake_file="${tmake_file} i386/t-crtpc i386/t-crtfm t-dfprules"
> md_unwind_header=i386/linux-unwind.h
> ;;
This conflicts with the Hurd/k*BSD patch.
Patch is okay if you take care of committing both, but please wait 48
hours or so, and please post the updated patch with config/dfp-bit.c
moved to dfp-bit.c (config/t-dfprules should stay there).
Paolo
next prev parent reply other threads:[~2011-07-07 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 10:34 Rainer Orth
2011-07-07 10:42 ` Paolo Bonzini [this message]
2011-07-07 10:51 ` Rainer Orth
2011-07-08 11:32 ` Rainer Orth
2011-07-12 8:06 ` Thomas Schwinge
2011-07-12 15:00 ` 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=4E158C76.1090503@gnu.org \
--to=bonzini@gnu.org \
--cc=bje@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).