You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ubuntu 16 i686: case value cannot be narrowed to type '__fsword_t' (aka 'int') ; result of comparison, 'uintptr_t' (aka 'unsigned int') is always false
#5663
Apologies for the late response here @advancedwebdeveloper : most of the folks working on OMR don't do much with 32-bit systems and we seem to have lost most of our active port library contributors :( .
32-bit builds using the recommended (ancient) compilers seem to work just fine (now that we've removed a misconfigured machine from the build list). But not so much on the system/build compiler you're using, apparently.
The first problem is because the file system type for CIFS_MAGIC_NUMBER (0xFF534D42) is an unsigned value but the field of the struct that holds the type is a signed type on your system, for whatever reason. The type of that field is an internal type, so I don't want to use it. The best solutions I could find for this problem are either to cast the field to an unsigned int or to cast the constant to a signed int. The fix I'll propose is to cast the constant to signed int as having the least impact.
The second problem is just a type mismatch. On your platform uintptr_t doesn't evaluate to unsigned long long. The values need to be cast to ADDRESS which, on 32-bit, needs to go through uintptr_t anyway, but for the comparison we should be using the raw unsigned long long value returned by strtoull().
I'll put a pull request together and see how people feel about it. I've confirmed that these two changes build just fine inside a 32-bit ubuntu docker container, but since I could not reproduce the original problem it would be helpful if @advancedwebdeveloper could help us validate the patch to make sure we've caught the problems.
Hi.
Build failed on
with
and
.
My generator is configured for
So I got these errors:
The text was updated successfully, but these errors were encountered: