-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
"array element types do not match" error with certain literals. #16
Comments
In C, int literals have type int if they can fit in the int32 range, and type long otherwise. That's probably why it's complaining. That being said, your code should work. I'll start working on a fix :) |
Should be all fixed now :) |
I figured, that's why I thought it was odd that Anyway, it is fixed now, thank you very much! :) (Ugh! I just noticed I wrote "31 and 32 bits" in the original comment, d'oh! I meant of course 32 and 33.) |
Let me know if you run into other problems and I'll try to fix them quickly, especially if they're easy to fix. |
Will do! Cheers! That other bug I mentioned in the UVM Wishlist #7 issue turns out not to be related to |
I've been busy the last couple of days, but I sat down this evening to fiddle with fixed point 3D math and discovered something odd while building a table of sin values.
Contents of
t.c
:Result of attempting to compile:
I tried with
0xffffffff
and0x100000000
on the theory that it might have something to do with having literal values of both 31 and 32 bits, respectively, in the same initializer. But with that pair of initial values the program compiles without the error message.The text was updated successfully, but these errors were encountered: