From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Alef PPC code generation problem
Date: Tue, 2 Apr 2002 13:50:13 +0100 [thread overview]
Message-ID: <20020402125359.E209F19988@mail.cse.psu.edu> (raw)
>>values. I wonder at which stage of code generation the faulty
>>conversion code is applied? It isn't to
>> quad = e - 4.0 * f;
yes, it is, though: it's the conversion from double to int that is wrong.
it might not generate the set/used warnings--i don't know about that--but
that code in the Alef code generator is wrong to start with.
it assigns to one int (when it should be a double) then loads from another.
it's all my fault, of course, since i wrote it, but i suspect it was left that
way by accident, when i was part way through. unlike qc (where i got it right)
i never used Alef and thus qal much for floating-point work, and i never subsequently noticed.
next reply other threads:[~2002-04-02 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 12:50 forsyth [this message]
2002-04-02 13:03 ` Lucio De Re
2002-04-02 14:36 ` Lucio De Re
-- strict thread matches above, loose matches on Subject: below --
2002-04-02 12:11 forsyth
2002-04-02 12:26 ` Lucio De Re
2002-04-02 12:42 ` Lucio De Re
2002-04-02 11:41 Lucio De Re
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=20020402125359.E209F19988@mail.cse.psu.edu \
--to=forsyth@vitanuova.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).