-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Cary R. wrote:
> While working on pr1869769 (real comparisons in cont. assign.) I have run
> into a number of slightly related problems. The major one I have left is
> that real constants Cr<xxx> are not handled very well. The code generator
> prints them with a plain %lg which limits the precision of the value
> passed to the run time. Is there a system agnostic way to find the maximum
> precision so we can pass that to %g?
Better would be to use the same sign-mantissa-exponent form as
is generated for the %loadi/wr instruction to get a real value.
This format is also clearly documented, along with ways to carry
the various zeros, infinities and NaNs.
> The other half of the problem is that when the real number prints with an
> exponent the runtime crashes. This is because a '+' is not considered a
> valid character in a Cr<xxx> constant and after fixing that it complains
> about an invalid name which I am assuming is the '+' again. Should I just
> add '+' as need to fix things or should I submit this as a separate bug
> report for a more thorough analysis?
This is an issue in the lexor. I started creating an IDENTIFIER
rule in the lexor.lex that is specially for matching Cr<...> and
its internal complexities. Just fix that.
- --
Steve Williams "The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
http://www.icarus.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD4DBQFHjNR2rPt1Sc2b3ikRAnyPAJjiLTdOK7YkS6li+XyzKgPy4sDHAJ9cMyP7
ZQVrNoL1wOPZ8LLT/xj97g==
=5zkE
-----END PGP SIGNATURE-----
|
