Correct vocp / vsocp prefix handling #11835
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've become suspicious of vbfy's prefix handling, but haven't tested it yet.Indeed, vbfy does this too. This explains much weird prefix behavior.Previously I had tested prefix handling on vscl, and it behaved strangely when used with t. Now it seems obvious that regnum swizzle was fixed, and probably explains why constants seemed to behave strange.
Also added vsbz/vlgb based on tests (they are pretty straight forward.) Didn't really test prefixes with them, though.
-[Unknown]