[Ppc64le] bug fixes

[alhad-deshpande]

This PR fixes below things:

1. g_assert mentioned in github issue 71080
2. Test case failures occurring on CICD pipeling due to incorrect instruction length of tailcall.
3. Corrections in instruction lengths for all opcodes in which new memory patch thunking has been impemented.

[ghost]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[carlossanlop]

@alhad-deshpande RC1 changes need a fix in main first. Was this done already? If not, please close this PR, send a PR to main first, then you can backport it with the help of the bot (ping me and I can help you).

[carlossanlop]

Oh I see the mainPR got merged. But this backport did not get automatically created by the maestro bot.

@akoeplinger@lewing can you please manually review this PR, since it's not a direct backport?

[carlossanlop]

There were failures in runtime-community. Please help confirm if they are related to this change.

[akoeplinger]

The failures are unrelated.

[carlossanlop]

Thanks for the sign-off @akoeplinger. Now I just need approval from @lewing.

I am pausing merges right now, in favor of getting the 7-rc1->7 PR merged without any more changes (the bot autocommits anything merged to rc1, and restarts the CI).

[lewing]

Lgtm

[carlossanlop]

The 7.0-rc1 -> 7.0 PR was merged, so now we're unblocked to merge this.
Approved and signed-off.
CI failures are unrelated.
Ready to merge.

[alhad-deshpande]

@carlossanlop@lewing@akoeplinger
Thanks for merging this PR into RC1 branch. But I dont see similar PR 74058 raised against main yet merged. So I think RC1 has these changes which are not yet in main.

The PR 73616 was for memory thunking and those changes are already there in RC1 branch.

Can you please merge PR 74058 into main so that RC1 branch is not ahead of main?

[akoeplinger]

@alhad-deshpande I merged #74058, thanks!

[alhad-deshpande]

@rzikm@akoeplinger
Did not understood why issue PR 74484 got tagged. Is this got tagged mistakenly?

[akoeplinger]

@alhad-deshpande yeah it was inadvertently mentioned in the PR description of that PR, no worries.

[alhad-deshpande]

@akoeplinger
Thanks for the confirmation.

[rzikm]

@rzikm@akoeplinger Did not understood why issue PR 74484 got tagged. Is this got tagged mistakenly?

Yes, I mistakenly created the PR against different base and it tagged lots of people for review and lots of PRs 🤦