On Sun, Nov 24, 2002 at 07:02:11PM -0500, David Robins wrote:
> Actually it looks like the problem is in assemble.pl's sub constant_table;
> even though $PConfig{numvalsize} is 12, $PConfig{packtype_n} is 'd' and
> pack('d',$n) uses 8 bytes. This is after hacking NUMVAL_SIZE to 12,
> though, whic
On Sun, 24 Nov 2002, Dan Sugalski wrote:
> At 9:20 AM -0500 11/24/02, Andy Dougherty wrote:
> >On Sat, 23 Nov 2002, David Robins wrote:
> >> When's the long double "KNOWN ISSUE" going to be fixed? What's the work
> >It's (at least partly) a packfile alignment thing. I think if you look in
> >t
At 9:20 AM -0500 11/24/02, Andy Dougherty wrote:
On Sat, 23 Nov 2002, David Robins wrote:
When's the long double "KNOWN ISSUE" going to be fixed? What's the work
around, just to build a perl with NV==double? I've looked around, can't
find anything about it except in KNOWN_ISSUES (only match
On Sat, 23 Nov 2002, David Robins wrote:
> When's the long double "KNOWN ISSUE" going to be fixed? What's the work
> around, just to build a perl with NV==double? I've looked around, can't
> find anything about it except in KNOWN_ISSUES (only match in RT is
> "Parrot_sprintf-related stuff"). Sc
When's the long double "KNOWN ISSUE" going to be fixed? What's the work
around, just to build a perl with NV==double? I've looked around, can't
find anything about it except in KNOWN_ISSUES (only match in RT is
"Parrot_sprintf-related stuff"). Scan of the archives turns up nothing.
Thanks,
Dav
