-
Notifications
You must be signed in to change notification settings - Fork 7
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
Type of operations #45
Comments
I believe that could be tested, yes. |
@ymherklotz I assume the following is a wrong syntax:
and should be:
I assume therefore that since in our tests there won't be any casting, floating point constant will always be followed by an In other words, we can safely remove the last character in a floating point constant assignment. The following would therefore be invalid:
and should be:
|
Correct, decimal values without the f should be treated as doubles. |
Another question @tobhil98 Can we assume no hex assignment will be used for floating points? Otherwise if we have something like |
Yeah, I would say hex values should be treated as integers, but I'm not entirely sure. |
Yeah I would agree, I doubt hex representation will be used to initialise floats and doubles. |
I was wondering if something like
int main()
{
double a = 13.7;
while (a < 5.9){
a = a - 1.1;
}
}
would be tested. I am asking because this means that the assembly generated for the comparison can only be determined by looking at the type of the variable within it i.e. a which is a double. This means that we need to do a double precision comparison. From god-bolt there doesn't seem to be any casting involved here just a double precision version of a while loop. Thanks!
The text was updated successfully, but these errors were encountered: