🚀 go-pugleaf

In article <2439@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:
>There may be some alignment bugs in Perl; Theodore Ts'o's posting
>indicates that there seemed to be such bugs when he brought it up on a
>DECStation, and such bugs would be likely to show up on SPARC-based
>machines as well.  The bug that started this thread ain't one of them,
>though.  The cause of said bug has been identified, so please, no more
>speculation on its cause....

In fact, once the patches I've posted are applied (the most important
of which fixed a array overrun which trashed malloc control blocks),
There's only one problem that I know of which might possibly be related
to alignment restrictions:   

<tytso@hodge>   {~/watchmaker/mipssrc/perl/t}
101% op.sort
1..3
Fixed up unaligned data access for pid 2332 (perl) at pc 0x418b0c
Fixed up unaligned data access for pid 2332 (perl) at pc 0x418b24
Fixed up unaligned data access for pid 2332 (perl) at pc 0x418b2c
not ok 1
ok 2
Segmentation violation (core dumped)

(the "Fixed up unaligned...." message is printed by the Ultrix Kernel)

All of the other regression tests pass on the PMAX, so I doubt most of
the reported bugs are alignment-based, given that everything else
works on a MIPS architecture.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Theodore Ts'o				bloom-beacon!mit-athena!tytso
3 Ames St., Cambridge, MA 02139		tytso@athena.mit.edu
   Everybody's playing the game, but nobody's rules are the same!