From: Timothy J.Wood <tjw@omnigroup.com>
To: Robert Dewar <dewar@gnat.com>
Cc: Luchezar Belev <l_belev@yahoo.com>, gcc@gcc.gnu.org
Subject: Re: why not consfold sin(const)
Date: Sun, 19 Sep 2004 20:53:00 -0000 [thread overview]
Message-ID: <CA3F3A47-0A75-11D9-8036-000D93361BA8@omnigroup.com> (raw)
In-Reply-To: <414DDB4F.3030600@gnat.com>
On Sep 19, 2004, at 12:17 PM, Robert Dewar wrote:
> Not at all, it is far more complex to implement, since you need a very
> accurate set of target independent elementary function routines (you
> can't just go calling these routines from the compiler and using the
> host functions!)
How about defining a ctor for that .o file that calls the target's
elementary function at run time and puts it a global created by the
compiler?
This has some arguably less than ideal side effects (the global would
need to be in writable memory), but it seems to me that this is not
"impossible" as a previous message claimed.
-tim
next prev parent reply other threads:[~2004-09-19 19:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 16:02 Luchezar Belev
2004-09-19 18:00 ` Robert Dewar
2004-09-19 19:17 ` Luchezar Belev
2004-09-19 19:31 ` Robert Dewar
2004-09-19 19:55 ` Luchezar Belev
2004-09-19 20:25 ` Robert Dewar
2004-09-19 20:34 ` Luchezar Belev
2004-09-19 20:56 ` Zack Weinberg
2004-09-20 8:15 ` Kai Henningsen
2004-09-19 21:12 ` Robert Dewar
2004-09-19 20:53 ` Timothy J.Wood [this message]
2004-09-19 22:41 ` Robert Dewar
2004-09-20 0:31 ` Timothy J.Wood
2004-09-20 4:27 ` Robert Dewar
2004-09-20 5:44 ` Dale Johannesen
2004-09-20 19:43 ` Toon Moene
2004-09-20 20:34 ` Kaveh R. Ghazi
2004-09-20 23:31 ` Robert Dewar
2004-09-21 0:13 ` Scott Robert Ladd
2004-09-21 5:18 ` Steven Bosscher
2004-09-21 5:55 ` Scott Robert Ladd
2004-09-23 11:35 Bradley Lucier
2004-09-23 23:04 ` Toon Moene
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=CA3F3A47-0A75-11D9-8036-000D93361BA8@omnigroup.com \
--to=tjw@omnigroup.com \
--cc=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=l_belev@yahoo.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).