rpcs3 stuck in an infinite loop about rpcs3 HOT 11 CLOSED

Interesting, thanks for the info! 😄 I wrote on Emunewz some time ago about issues with the PSL1GHT samples: http://www.emunewz.net/forum/showthread.php?tid=149835
Hmm.. I thought that part of rpcs3 was working perfectly. :-/

from rpcs3.

is it possible to make a call stack for the disassembler interface? it will really help with debugging things

from rpcs3.

Nice idea! If DH agrees with this, I will take care of the feature. ;-)

from rpcs3.

@elisha464: You are probably looking for this. I hope you find it useful:
Binary: http://www.mediafire.com/download/j4aneqok4w7fwbd/rpcs3-x86-call-stack.exe

@DHrpcs3:
Patch: http://rghost.net/50340219
I'm not sure if you are going to like the changes made. I had to add an extra line to 2 PPU Instructions bl and blr in order to push and pop respectively the address to a Stack. Then it's written to a text box in a similar manner to WriteRegs(). Tell me if you agree with this. 😄

from rpcs3.

ok, I just realized that a call stack might not be that useful because of mflr and mtlr :(, I'll keep trying though, but its going to be hard

from rpcs3.

I think I found a bug, you tell me
I have this situation
GPR[8] = 0x1
GPR[9] = 0x1f

and I'm trying to do
sld r8, r8, r9

what should be the result of r8?
0x0
or
0x80000000

right now, the emulator gives 0x0

from rpcs3.

fix suggestion
PPUInterpreter.h line 2367

void SLD(u32 ra, u32 rs, u32 rb, bool rc)
{
    RLDICR(ra, rs, CPU.GPR[rb], 63 - CPU.GPR[rb], rc);
    /*const u32 n = CPU.GPR[rb] & 0x3f;
    const u64 r = rotl64(CPU.GPR[rs], n);
    const u64 m = (CPU.GPR[rb] & 0x30) ? 0 : rotate_mask[0][63 - n];

    CPU.GPR[ra] = r & m;

    if(rc) CPU.UpdateCR0<s64>(CPU.GPR[ra]);*/
}

reference

it seems to work, I dont know if it'll break anything or if its not optimized, its just a suggestion

from rpcs3.

@elisha464: Does DHrpcs3@aab6951 fix this issue?

from rpcs3.

yes, it does, finally the video samples of PSL1GHT initialize the rsx thread :), another big step in compatibility, who would have though that one instruction will ruin everything

from rpcs3.

Great! Thank you so much for debugging this! 😄

from rpcs3.

just doing my part :P

from rpcs3.