This should make solaris 'as' happy. There will be an assembler warning, but
it's harmless.
diff -r1.3 sun4Generic.pm
78c78
< return Parrot::Jit->Assemble("ld [\%o0], \%o0\njmpl \%o0, \%g0\n");
---
> return Parrot::Jit->Assemble("ld [\%o0], \%o0\njmpl \%o0, \%g0\nnop\n");
151c151
<
On Wed, 30 Jan 2002, Jason Gloudon wrote:
>On Wed, Jan 30, 2002 at 03:27:18PM -0500, Andy Dougherty wrote:
>> objdump. Is anyone with a Solaris system familiar enough with jit
>> internals to have a go at adapting it to use dis instead of GNU objdump?
>
>The difference was pretty minimal. It sho
On Wed, Jan 30, 2002 at 03:27:18PM -0500, Andy Dougherty wrote:
> On Solaris, it looks like JIT will now be enabled if the user has also
> installed GNU objdump. However, there is (often) already a disassembler
> in /usr/ccs/bin/dis. It's output is similar, but not identical to,
> objdump. Is a
At 3:27 PM -0500 1/30/02, Andy Dougherty wrote:
>On Solaris, it looks like JIT will now be enabled if the user has also
>installed GNU objdump. However, there is (often) already a disassembler
>in /usr/ccs/bin/dis. It's output is similar, but not identical to,
>objdump. Is anyone with a Solaris
On Solaris, it looks like JIT will now be enabled if the user has also
installed GNU objdump. However, there is (often) already a disassembler
in /usr/ccs/bin/dis. It's output is similar, but not identical to,
objdump. Is anyone with a Solaris system familiar enough with jit
internals to have a
