From: Kean Johnston <jkj@sco.com>
To: Jim Wilson <wilson@specifixinc.com>
Cc: "Joseph S. Myers" <jsm@polyomino.org.uk>, gcc@gcc.gnu.org
Subject: Re: Promoting floats to doubles?
Date: Wed, 05 May 2004 09:10:00 -0000 [thread overview]
Message-ID: <4098AD32.5050003@sco.com> (raw)
In-Reply-To: <40989367.7000506@specifixinc.com>
> Thinking about this some more, I am starting to think that Joseph is
> right. floorf is a C99 function, so we can't change its prototype, thus
> we need an ABI change rather than a C front end change.
Yup, thats where I am at.
I'm having a spot of bother trying to figure out where to do it
though. I changed PROMOTE_MODE to be:
#define PROMOTE_MODE(MODE,UNSIGNEDP, TYPE) \
do { \
if (((MODE) == HImode && TARGET_PROMOTE_HI_REGS) \
|| (MODE) == QImode && TARGET_PROMOTE_QI_REGS)) \
(MODE) = SImode; \
else if (((MODE) == SFmode)) \
(MODE) = DFmode; \
} while (0)
and added:
#define PROMOTE_FUNCTION_ARGS
#define PROMOTE_FOR_CALL_ONLY
Unfortunately when I compile things this way I get an ICE in
expand_call, at calls.c:3131. Clearly then, this isnt the right
place. I've read quite a bit of gdbint.info and I cant find what
may be the right place to do this sort of thing. I just dont know
the internals well enough so I will pause for advice from you
or Joseph.
Kean
next prev parent reply other threads:[~2004-05-05 9:10 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 [this message]
2004-05-05 22:47 ` Jim Wilson
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=4098AD32.5050003@sco.com \
--to=jkj@sco.com \
--cc=gcc@gcc.gnu.org \
--cc=jsm@polyomino.org.uk \
--cc=wilson@specifixinc.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).