From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Alef PPC code generation problem
Date: Tue, 2 Apr 2002 13:11:20 +0100 [thread overview]
Message-ID: <20020402121506.9816C19995@mail.cse.psu.edu> (raw)
>>What bothers me, in addition to the failed code generation, is the
>>fact that the type upgrade (the right word escapes me presently)
>>for integer constant 13 is generated as object code. Surely it
>>_is_ possible for the compiler to detect the value and its purpose
>>earlier and convert it at compile rather than at run time? I am
i'm confused. in the example you sent,
t = 13*i;
neither qal nor qc generates a type upgrade for constant 13;
it generates an integer multiplication of 13 and i (as shifts and adds, but that's almost
beside the point), and then converts the result, which is correct.
the code generated for the fp conversion by qc looks right to me.
the code generated by qal (it turns out) has never been correct,
which is consistent with the source code in qal's code.c looking
wrong too.
next reply other threads:[~2002-04-02 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 12:11 forsyth [this message]
2002-04-02 12:26 ` Lucio De Re
2002-04-02 12:42 ` Lucio De Re
-- strict thread matches above, loose matches on Subject: below --
2002-04-02 12:50 forsyth
2002-04-02 13:03 ` Lucio De Re
2002-04-02 14:36 ` 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=20020402121506.9816C19995@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).