Skip to content

Conversation

@sudo-apt-abdullah
Copy link
Contributor

@sudo-apt-abdullah sudo-apt-abdullah commented Aug 21, 2025

Closes #995 which depends on #944.

Copy link
Collaborator

@ThinkOpenly ThinkOpenly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One minor request that actually has nothing to do with your specific changes. Otherwise, looks good. :-)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you add:

base: 64

to this file?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I've added this in ssamoswap.d.yaml file. One more question, am I supposed to add new files for C.SSPOPCHK and C.SSPUSH under the Zicfiss extension?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are present as sspopchk.x1.yaml and similar, although they is not really correct. I have PR #872 that needs attention which fixes these, but I haven't finished getting it to pass CI yet. (And haven't had a chance to do so recently.) You can proceed as you already have.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In that PR, I can see that you merged sspopchk.x1.yaml & sspopchk.x5.yaml into single file sspopchk.yaml and sspush.x1.yaml & sspush.x5.yaml into file sspush.yaml, but can't see 16 bit version of sspush and sspopchk. Do we need to create separate files for that or I'm missing something?

You can proceed as you already have.
You mean I should pick the changes from there, right?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I conflated the two. Yes, we do need C.SSPOPCHK and C.SSPUSH. Note that they're a little weird because their encoding overrides some C.MOP encodings.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I'll give it some time to understand and then will try to write those files as well.

@sudo-apt-abdullah
Copy link
Contributor Author

@ThinkOpenly, please have a look at your convinience, thanks!

@ThinkOpenly
Copy link
Collaborator

There are some CI failures. Are you able to look at those?

@sudo-apt-abdullah
Copy link
Contributor Author

There are some CI failures. Are you able to look at those?

It couldn't find CSR[Xenvcfg].SSE which I've added in PR #995. So, it depends on #995 that depends on #891 :)

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

Successfully merging this pull request may close these issues.

Implemention of Shadow stack instructions

2 participants