Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zce-branch : c.mva01s07 zce extension not working #9

Open
sarkuuk opened this issue Jan 26, 2022 · 2 comments
Open

zce-branch : c.mva01s07 zce extension not working #9

sarkuuk opened this issue Jan 26, 2022 · 2 comments

Comments

@sarkuuk
Copy link

sarkuuk commented Jan 26, 2022

Hi,

We are writing couple of programs for zce extensions and testing in this branch below on latest commit.
Repo: plctlab/plct-spike/
Branch: plct-zce-dev

And we are facing an issue with below double move commands.

  1. c.mva01s07 s0, s0;

    Expectation is double move should happen, # mv a0, s0; mv a1, s0
    Zce spike simulation observation : s0 content not moving to a0 and a1

  2. c.mva01s07 s0, s1;

    Expectation is double move should happen, # mv a0, s0; mv a1, s1
    Zce spike simulation observation : a0 and a1 seem not getting updated with s0 and s1

Could you please look into this? I can give more details if you need.
Thank you very much.

Regards,
Sarika

@liweiwei90
Copy link
Collaborator

Thanks for your issue. I have tried to fix the errors in extracting the truly reg index from sreg1/sreg2. You can try again on the latest version.

@sarkuuk
Copy link
Author

sarkuuk commented Jan 27, 2022

Thank you very much, I will check the same on latest.

I would like to inform another issue too.

For beqi/bnei instructions, the immediate value the register is being compared to, doesnt come correctly in the trace.
For example : beqi t1, 1,offset as per assembly, in spike simulation functionally its correct(branching to right pc+offset value), but trace prints wrong immediate values which get compared with the register. Same with bnei.
Could you please check?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants