From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Alef PPC code generation problem
Date: Tue, 2 Apr 2002 16:36:52 +0200 [thread overview]
Message-ID: <20020402163651.L6290@cackle.proxima.alt.za> (raw)
In-Reply-To: <20020402125359.E209F19988@mail.cse.psu.edu>; from forsyth@vitanuova.com on Tue, Apr 02, 2002 at 01:50:13PM +0100
On Tue, Apr 02, 2002 at 01:50:13PM +0100, forsyth@vitanuova.com wrote:
> i never used Alef and thus qal much for floating-point work, and i never subsequently noticed.
OK, I have changed merely the type of the created temporary variable
in /sys/src/alef/q/code.c:256 from TINT to TFLOAT:
tmp = stknode(builtype[TFLOAT]);
which seems to have eliminated the warnings without replacing them
with invalid instruction types. Until I find a testbench, this will
have to be deemed untested :-)
++L
next prev parent reply other threads:[~2002-04-02 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 12:50 forsyth
2002-04-02 13:03 ` Lucio De Re
2002-04-02 14:36 ` Lucio De Re [this message]
-- 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=20020402163651.L6290@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).