From: Jim Wilson <wilson@specifixinc.com>
To: Kean Johnston <jkj@sco.com>
Cc: "Joseph S. Myers" <jsm@polyomino.org.uk>, gcc@gcc.gnu.org
Subject: Re: Promoting floats to doubles?
Date: Wed, 05 May 2004 22:47:00 -0000 [thread overview]
Message-ID: <1083797272.1082.51.camel@leaf.tuliptree.org> (raw)
In-Reply-To: <4098AD32.5050003@sco.com>
On Wed, 2004-05-05 at 02:00, Kean Johnston wrote:
> #define PROMOTE_MODE(MODE,UNSIGNEDP, TYPE) \
> #define PROMOTE_FUNCTION_ARGS
> #define PROMOTE_FOR_CALL_ONLY
PROMOTE_FOR_CALL_ONLY was removed last week by the way.
The PROMOTE_MODE stuff may not work in your case. Currently, they are
only for integers (char/short/int/long), and they work by adding
SUBREGs. However, SUBREGs can not be used for converting floats to
doubles and vice versa. So the PROMOTE_MODE stuff will just lead to
trouble. You might be able to get it working, but you will have to
rewrite the code a bit. It might be easier to add some new hooks which
are used in the same places but generate conversions instead of adding
subregs.
It is probably easier to do this in the C front end, even if that is the
wrong place to do this. It will be a bit more work to do this in the
middle-end. I don't believe there are any existing hooks for this. I
will you will. have to write some code to get this working in the
middle-end.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2004-05-05 22:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-02 6:32 Kean Johnston
2004-05-03 20:39 ` Jim Wilson
2004-05-04 1:25 ` Kean Johnston
2004-05-04 4:00 ` Jim Wilson
2004-05-04 17:45 ` Kean Johnston
2004-05-04 18:52 ` Joseph S. Myers
2004-05-04 20:44 ` Jim Wilson
2004-05-05 0:06 ` Kean Johnston
2004-05-05 2:18 ` Jim Wilson
2004-05-05 7:10 ` Jim Wilson
2004-05-05 9:10 ` Kean Johnston
2004-05-05 22:47 ` Jim Wilson [this message]
2004-05-05 23:48 ` Kean Johnston
2004-05-04 20:52 ` Jim Wilson
2004-05-05 0:14 ` Kean Johnston
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=1083797272.1082.51.camel@leaf.tuliptree.org \
--to=wilson@specifixinc.com \
--cc=gcc@gcc.gnu.org \
--cc=jkj@sco.com \
--cc=jsm@polyomino.org.uk \
/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).