Skip to content

possible fix for byval issue#1296

Closed
regehr wants to merge 1 commit intoAliveToolkit:masterfrom
regehr:byval-fix
Closed

possible fix for byval issue#1296
regehr wants to merge 1 commit intoAliveToolkit:masterfrom
regehr:byval-fix

Conversation

@regehr
Copy link
Copy Markdown
Contributor

@regehr regehr commented Mar 17, 2026

ok I'm not at all confident about this patch for #1295, which I noticed had a TODO on it only after reporting

if (!byval_bytes.isZero()) {
uint64_t bytes;
if (!byval_bytes.isUInt(bytes))
return false;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

byval bytes can be a variable. The code needs to support this case or leave the TODO there and return true to avoid false positives. In general this requires doing a memcmp using a lambda (which is not implemented in memory.cpp yet).

@regehr
Copy link
Copy Markdown
Contributor Author

regehr commented Mar 20, 2026

thanks Nuno, let me come back to this later when I have more time

@regehr regehr closed this Mar 20, 2026
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.

2 participants