public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Fu, Chao-Ying" <fu@mips.com>
To: <gcc-patches@gcc.gnu.org>
Cc: "Thekkath, Radhika" <radhika@mips.com>,
	"Stephens, Nigel" <nigel@mips.com>,
	        "Mark Mitchell" <mark@codesourcery.com>
Subject: [patch] Fixed-point patch 9/10
Date: Thu, 02 Aug 2007 00:25:00 -0000	[thread overview]
Message-ID: <3CB54817FDF733459B230DD27C690CEC03EE8EFB@Exchange.mips.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]

Hi,

  Here is the patch #9.  Please review it.  Thanks!

> 1. Merge in machine modes to support signed and unsigned
> fract and accum modes.  Handle scalar and vector modes.
DONE!
> 2. Merge in fixed-value.h and fixed-value.c to handle fixed-point values.
(fixed-value.diff)
> 3. Merge in TREE structures for fixed-point types and constants.
(tree.diff)
> 4. Merge in C front-end changes to parse _Sat, _Fract and _Accum.
(c-parser.diff)
> 5. Merge in RTL structures for fixed-point constants and operators.
(rtl.diff)
> 6. Merge in libcpp to parse fixed-point constants.
(cpp.diff)
> 7. Merge in changes to support "case" of FIXED_POINT_TYPE, FIXED_CST,
> and CONST_FIXED in .c and .h files.
(changes.diff)
> 8. Merge in the MIPS backend that supports fixed-point instructions.
(mips.diff)
> 9. Merge in configure/build system changes for the runtime library.
(libgcc.diff)
> 10. Merge in testsuite (from gcc.dg/fixed-point) that only run
> when the compiler is configured to enable fixed-point.

Regards,
Chao-ying


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.

[-- Attachment #2: libgcc.diff.gz --]
[-- Type: application/x-gzip, Size: 21691 bytes --]

             reply	other threads:[~2007-08-02  0:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02  0:25 Fu, Chao-Ying [this message]
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
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=3CB54817FDF733459B230DD27C690CEC03EE8EFB@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 \
    /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).