develooper Front page | perl.perl6.internals | Postings from September 2005

Re: GMC release -- Punt

Thread Previous | Thread Next
From:
Andy Dougherty
Date:
September 6, 2005 10:18
Subject:
Re: GMC release -- Punt
Message ID:
Pine.SOC.4.62.0509061204180.26135@maxwell.phys.lafayette.edu
On Sat, 3 Sep 2005, Nattfodd wrote:

> thanks for the investigation, I'll look closely to it. It was reported 
> to fail on AMD64 too but we did not try setting GMC_ALIGN to 16. Also be 
> warned that I am very far from an alignment master, so I may have done 
> things wrong in my small hack.

At first glance, I'd guess that it's safest to have all of the *_ALIGN 
items in the parrot/*.h headers in agreement with each other.  
Unfortunately, it's not at all clear from the source what's expected to be 
aligned with what, so there's some blind guessing going on here. However, 
if you are moving blocks around and the target location has the same 
alignment constraint as the original, then you really should be fine, and 
the problems I've encountered may be due to something else.

In any case, I was mainly just doing some portability testing -- it 
doesn't look unworkable.

However, there's a far more important issue before worrying too much more 
about alignment issues, namely, is this a good direction for Parrot to go 
in terms of memory management?  That's a much higher level design issue,
and I'm not the right one to comment on it.

-- 
    Andy Dougherty		doughera@lafayette.edu

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About