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

[Observation] HRTI 'E' has undefined behaviour when mark is not present #13

Open
FalsePattern opened this issue Oct 16, 2022 · 0 comments

Comments

@FalsePattern
Copy link

The E 'Erase mark' operation removes an already existing timer mark with the current IP's ID.

However, it is not defined whether it should reflect, or behave as no-op when such a mark was not created already using M beforehand.

In my subjective opinion, no-op fallthrough makes the most sense given that the end result would be the same in both cases (T reflecting), however, E reflecting with an empty mark would have a higher consistency with the behaviour of other instructions that reflect on failure.

The safest way to go about using HRTI in this case would be to make sure that E is never called before M (or twice after M), or by having a reflection-ignoring construct around E (for instance: 3j>z#E when entering at the 3 with a delta to the right).

(this issue is just a minor observation for anyone who is looking to use this specific fingerprint in their code and not a request for clarification)

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

1 participant