From: "Fu, Chao-Ying" <fu@mips.com>
To: "Mark Mitchell" <mark@codesourcery.com>, <gcc-patches@gcc.gnu.org>
Cc: "Richard Sandiford" <richard@codesourcery.com>,
"Thekkath, Radhika" <radhika@mips.com>,
"Stephens, Nigel" <nigel@mips.com>
Subject: RE: [patch] Fixed-point patch 9/10
Date: Sat, 15 Sep 2007 02:15:00 -0000 [thread overview]
Message-ID: <3CB54817FDF733459B230DD27C690CEC03EE8F37@Exchange.mips.com> (raw)
In-Reply-To: <3CB54817FDF733459B230DD27C690CEC03EE8F33@Exchange.mips.com>
[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]
Hi,
> > 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!
>
We change Makefile.in for GNU Make 3.79.1. Please check the updated patch.
We add an external shell script to generate the necessary lists to build
fixed-point functions. Is this updated patch ok? Thanks a lot!
Regards,
Chao-ying
gcc/ChangeLog
2007-09-14 Chao-ying Fu <fu@mips.com>
Nigel Stephens <nigel@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-09-14 Chao-ying Fu <fu@mips.com>
Nigel Stephens <nigel@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.
* gen-fixed.sh: New file to generate lists of fixed-point labels,
funcs, modes, from, to.
[-- Attachment #2: libgcc.diff.gz --]
[-- Type: application/x-gzip, Size: 22966 bytes --]
next prev parent reply other threads:[~2007-09-14 21:34 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
2007-09-15 2:15 ` Fu, Chao-Ying [this message]
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=3CB54817FDF733459B230DD27C690CEC03EE8F37@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).