Melvin Smith:
# I have a patch almost complete that makes Parrot handle
# bytecode files across platforms (does endian and wordsize
# transform), but there is one glaring non-portability, and
# that is that we are storing floating point constants in native format.
#
# We need to discuss how we
Mike Lambert wrote:
> Wow. Tinderbox gave us fall and spring in a few hour period. Nice. Here's
> a patch to help make us make it to summer again.
Steve actually pointed out that this style of code was not safe, but I still
managed to miss that one.
> -(char *)cur_buffer += pool->unit_si
I have a patch almost complete that makes Parrot handle bytecode
files across platforms (does endian and wordsize transform), but there is
one glaring non-portability, and that is that we are storing floating point
constants in native format.
We need to discuss how we want to portably store these
> Commit completed. One thing I find handy when patching is to run a CVS
> update, make distclean, and rebuild/retest on my local platform. This
> helps catch misapplied and incomplete patches.
Wow. Tinderbox gave us fall and spring in a few hour period. Nice. Here's
a patch to help make us make
Jeff wrote:
>
> Daniel Grunblatt wrote:
> >
> > On Sat, 4 May 2002, Steve Fink wrote:
> >
> > > Applied, with one change: the alignments of the three pools are now
> > > #defined.
> > >
> >
> > I believe your commit was incomplete.
Commit completed. One thing I find handy when patching is to run
Daniel Grunblatt wrote:
>
> On Sat, 4 May 2002, Steve Fink wrote:
>
> > Applied, with one change: the alignments of the three pools are now
> > #defined.
> >
>
> I believe your commit was incomplete.
I'd have to agree. Some of the code appears to use 'last_PMC_Arena',
which isn't defined yet i
On Sat, 4 May 2002, Steve Fink wrote:
> Applied, with one change: the alignments of the three pools are now
> #defined.
>
I believe your commit was incomplete.
Applied, with one change: the alignments of the three pools are now
#defined.
Currently, we only have one non-green machine on the tinderbox. Thanks
Robert!
The remaining burning box is galatic-tcc. Below patch might fix the
problem, but I can't be sure. It seems to compile fine here under MSVC,
but I'm not sure if it's a "correct" patch to fix the tcc problem or if
it's j
Steve Fink wrote:
>
> Why use 2-byte alignment on constant strings? Wouldn't it speed up
> memory copies to make them always be 4-byte aligned? (Or
> machine-register-size aligned?)
Changed to 4-byte alignment for now. If there is a specific sizeof(X) you
would prefer, just change it.
> 1. Can y
10 matches
Mail list logo
