From: "Fu, Chao-Ying" <fu@mips.com>
To: "Mark Mitchell" <mark@codesourcery.com>
Cc: "Richard Sandiford" <richard@codesourcery.com>,
<gcc-patches@gcc.gnu.org>,
"Thekkath, Radhika" <radhika@mips.com>,
"Stephens, Nigel" <nigel@mips.com>
Subject: RE: [patch] Fixed-point patch 9/10
Date: Wed, 12 Sep 2007 19:15:00 -0000 [thread overview]
Message-ID: <3CB54817FDF733459B230DD27C690CEC03EE8F33@Exchange.mips.com> (raw)
In-Reply-To: <46E7757E.6050804@codesourcery.com>
Mark Mitchell wrote:
> > Is there any status update for this patch (9/10)?
> > http://gcc.gnu.org/ml/gcc-patches/2007-08/msg00099.html
>
> Wow, that's a lot of routines. :-) I'm going to trust you that the
> implementations of the various routines are OK. How many of those
> routines are actually necessary on a MIPS processor that supports
> fixed-point? Do almost all of them get eliminated from libgcc?
MIPS processors can support most of add, sub, mul patterns with or without
saturating. For division, shift, compare, negation, and conversions among
fixed-point, integer, and floating-point types, libgcc routines are needed.
Conversion routines are the biggest portion in libgcc, because
we convert between so many different machine modes to cover
all cases.
>
> I'm a little worried about how much bigger this will make
> libgcc, but if
> it only affects targets configured with fixed-point
> emulation, then I'm
> not so worried. (I suspect that most people will either used a
> fixed-point processor, or will not even turn on the emulation.)
>
> > One issue that we want to mention is that
> > building this fixed-point libgcc library requires GNU make 3.81,
> > due to code in Makefile.in:
>
> Thank you for pointing this out. The make code you've written looks
> very tidy. However, I don't think we can require GNU make
> 3.81 at this
> point. I think it would be reasonable to require that for
> GCC 4.4, but
> I think it's a bit late in the game to require that for 4.3. In any
> case, it's not a decision I can make unilaterally. Is it
> possible to do
> what you need to do with an older version of GNU make? (I can't
> remember what the oldest supported version of GNU make is for GCC.)
>
I will check with Nigel to see if we can change Makefile.in for
GNU Make 3.79.1. Thanks a lot!
Regards,
Chao-ying
next prev parent reply other threads:[~2007-09-12 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 0:25 Fu, Chao-Ying
2007-09-11 19:48 ` Fu, Chao-Ying
2007-09-12 7:00 ` Mark Mitchell
2007-09-12 14:19 ` Joseph S. Myers
2007-09-12 19:15 ` Fu, Chao-Ying [this message]
2007-09-15 2:15 ` Fu, Chao-Ying
2007-09-17 21:37 ` Mark Mitchell
2007-09-17 23:11 ` Fu, Chao-Ying
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=3CB54817FDF733459B230DD27C690CEC03EE8F33@Exchange.mips.com \
--to=fu@mips.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=nigel@mips.com \
--cc=radhika@mips.com \
--cc=richard@codesourcery.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).