Bugfix: unaligned access in MIPS getdents64

[ljucovic]

Checklist

Which kind of PR do you create?

• This PR only contains minor fixes.
• This PR contains major feature update.
• This PR introduces a new function/api for Qiling Framework.

Coding convention?

• The new code conforms to Qiling Framework naming convention.
• The imports are arranged properly.
• Essential comments are added.
• The reference of the new code is pointed out.

Extra tests?

• No extra tests are needed for this PR.
• I have added enough tests for this PR.
• Tests will be added after some discussion and review.

Changelog?

• This PR doesn't need to update Changelog.
• Changelog will be updated after some proper review.
• Changelog has been updated in my PR.

Target branch?

• The target branch is dev branch.

One last thing

• I have read the contribution guide

---

[xwings]

Hi,

Welcome to Qiling Framework.

Your PC need to to merge to dev and not master. thanks

[xwings]

Hi,

The code seems to break the test. I need to revert it. Will you be able to make another PR ?

[ljucovic]

I have run the tests and they pass on my end, should I create a new PR?

[meck-gd]

@xwings Since no changes are required and this PR was not the cause of the breakage, you should be able to just cherry-pick commit 6bc1a3d onto the dev branch again rather than requesting a new PR.

[xwings]

Its better for a new PR and let it run thru the test. let the rest of the team comment it too