From: "Fu, Chao-Ying" <fu@mips.com>
To: "Mark Mitchell" <mark@codesourcery.com>,
"Richard Sandiford" <richard@codesourcery.com>,
<gcc-patches@gcc.gnu.org>
Cc: "Thekkath, Radhika" <radhika@mips.com>,
"Stephens, Nigel" <nigel@mips.com>
Subject: RE: [patch] Fixed-point patch 9/10
Date: Tue, 11 Sep 2007 19:48:00 -0000 [thread overview]
Message-ID: <3CB54817FDF733459B230DD27C690CEC03EE8F31@Exchange.mips.com> (raw)
In-Reply-To: <3CB54817FDF733459B230DD27C690CEC03EE8EFB@Exchange.mips.com>
Hi,
>
> gcc/ChangeLog
> 2007-08-01 Chao-ying Fu <fu@mips.com>
>
> * config/fixed-bit.h: New file.
> * config/fixed-bit.c: New file.
> * doc/libgcc.texi (Fixed-point fractional library
> routines): New node.
>
> libgcc/ChangeLog
> 2007-08-01 Chao-ying Fu <fu@mips.com>
>
> * fixed-obj.mk: New file to support fine-grain
> fixed-point functions.
> * Makefile.in (fixed_point): Define.
> Check if fixed_point is yes to build support functions.
> * configure.ac: Check for fixed_point support.
> * configure: Regenerated.
>
Is there any status update for this patch (9/10)?
http://gcc.gnu.org/ml/gcc-patches/2007-08/msg00099.html
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:
Ex:
+# Generate permutations of generic function name and mode
+$(foreach name,$(fixed-func-names),\
+ $(foreach mode,$(fixed-fract-modes),\
+ $(eval $(call fixed-arith,$(name),$(mode)))))
This "make version" issue will affect all MIPS targets, because
fixed-point is enabled by default for MIPS.
Can we ask people to move to "GNU make 3.81"?
Or do you have any suggestion?
Thanks a lot!
Regards,
Chao-ying
next prev parent reply other threads:[~2007-09-11 18:41 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 [this message]
2007-09-12 7:00 ` Mark Mitchell
2007-09-12 14:19 ` Joseph S. Myers
2007-09-12 19:15 ` Fu, Chao-Ying
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=3CB54817FDF733459B230DD27C690CEC03EE8F31@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).