On Tue, 10 Mar 2009, Reini Urban wrote:
> 2009/3/10 Andy Dougherty <[email protected]>:
> > I don't know exactly where in the code this issue is coming up, so I don't
> > have any informed opinion about how best to change it. I have tried
> > reading the relevant tickets, but I can't find specific information on
> > *where* this problem is occuring.
> Where is is occurring? In every (char*)cursor+=4, fetching integers, strings,
> ops on sparc64 with cc we got bus alarms.
But where, exactly, is the current code doing (char *) cursor += 4?
Can you point to a file and line number? One specific example would be
helpful. Also, what, exactly, was the sequence of events that led to that
file and line number? What was the command? What was the input file?
None of that information is in the tickets that I saw.
> Now with -xmemalign=4s we've hidden that. But with native-sized data the
> ptr advance will be much faster, a simple cursor++.
(On a separate note, I hope you noticed my comment elsewhere that the
current code to automatically set -xmemalign=4s doesn't work.)
--
Andy Dougherty [email protected]
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
