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

Fix reflection test failure on 32bit #19885

Merged
merged 1 commit into from Jan 6, 2017
Merged

Fix reflection test failure on 32bit #19885

merged 1 commit into from Jan 6, 2017

Conversation

Keno
Copy link
Member

@Keno Keno commented Jan 6, 2017

The bug here is that one of the pointers gets zero extended (isymb->first),
while the other (Fptr) gets sign extended, so comparing the two breaks down.
The simplest way to fix, is just to use the appropriate integer size for the
platform we're on.

Fixes #19803.

The bug here is that one of the pointers gets zero extended (isymb->first),
while the other (Fptr) gets sign extended, so comparing the two breaks down.
The simplest way to fix, is just to use the appropriate integer size for the
platform we're on.
@tkelman tkelman merged commit 4a6bbb8 into master Jan 6, 2017
@tkelman tkelman deleted the kf/fixreflection branch January 6, 2017 10:56
@tkelman
Copy link
Contributor

tkelman commented Jan 6, 2017

So why is it we weren't hitting this as an issue until recently?

@Keno
Copy link
Member Author

Keno commented Jan 6, 2017

Well, the bug only shows up if you have two jumps into the same function (and the address of the generated code is in the upper 2GB of address space), so it depends on the generated code, and perhaps even the way the OS decides to allocate memory.

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.

None yet

2 participants