From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: gcc@gcc.gnu.org
Subject: Coldfire V4E addition to gcc
Date: Wed, 05 Dec 2001 10:23:00 -0000 [thread overview]
Message-ID: <200112051822.fB5IMVx20055@hyper.wm.sps.mot.com> (raw)
I'm in the midst of adding in Coldfire v4e support to gcc-2.95.3, and
I'm wondering if it isn't time to reconfigure which variant of
floating point is used. Sonce I'm adding in the ColdFire FPU, this
would bring the variants to four:
1) TARGET_68881 - is an FPU attached, which may be a '881.
2) TARGET_FPA - is a Sun FPA attached.
3) TARGET_68040_ONLY - subset/superset of 68881.
4) TARGET_FPU_V4E - is a ColdFire v4e FPU attached.
The first three variants are used in the machine description code,
header files, and C code to control the instructions generated.
What I'd like to do is to split TARGET_68881 into two parts,
TARGET_FPU to indicate that *any* FPU is attached, and TARGET_68881 to
indicate that *only* a 68881 is attached.
Then code such as:
(define_expand "addsf3"
[(set (match_operand:SF 0 "general_operand" "")
(plus:SF (match_operand:SF 1 "general_operand" "")
(match_operand:SF 2 "general_operand" "")))]
"TARGET_68881 || TARGET_FPA"
"")
changes to:
(define_expand "addsf3"
[(set (match_operand:SF 0 "general_operand" "")
(plus:SF (match_operand:SF 1 "general_operand" "")
(match_operand:SF 2 "general_operand" "")))]
"TARGET_FPU"
"")
instead of:
(define_expand "addsf3"
[(set (match_operand:SF 0 "general_operand" "")
(plus:SF (match_operand:SF 1 "general_operand" "")
(match_operand:SF 2 "general_operand" "")))]
"TARGET_68881 || TARGET_FPA || TARGET_FPU_V4E"
"")
I also understand that I'll have to think of how to deal with the
TARGET_68040_ONLY flag, of which the V4e supports a subset.
Comments anybody?
--
Peter Barada Peter.Barada@motorola.com
Wizard 781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola) 781-270-0193 (fax)
reply other threads:[~2001-12-05 18:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200112051822.fB5IMVx20055@hyper.wm.sps.mot.com \
--to=pbarada@mail.wm.sps.mot.com \
--cc=gcc@gcc.gnu.org \
/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).