Given the following code fragment:

/*
The C standard library header <limits.h> provides macros that define
the range of each integer type [including the character types]
*/
#include <limits.h>
signed char x = SCHAR_MAX;

write the exact value resulting from the evaluation of expression sizeof(x) when compiled using -bit GCC compiler.

Given the following code fragment:

/*
The C standard library header <float.h> provides macros that define the
range and accuracy of the float, double, and long double types.
Macros FLT_MAX, DBL_MAX, and LDBL_MAX provide the largest finite value that
can be represented by types float, double, and long double, respectively.
*/
#include <float.h>
long double x = LDBL_MAX;

write the exact value resulting from the evaluation of expression sizeof(x) when compiled using -bit GCC compiler.

Given the following code fragment:

/*
The C standard library header <float.h> provides macros that define the
range and accuracy of the float, double, and long double types.
Macros FLT_MAX, DBL_MAX, and LDBL_MAX provide the largest finite value that
can be represented by types float, double, and long double, respectively.
*/
#include <float.h>
float x = FLT_MAX;

write the exact value resulting from the evaluation of expression sizeof(x) when compiled using -bit GCC compiler.

Write the exact text printed to the standard output stream by the following code fragment. If the code fragment cannot be compiled, write [for compile-time error]. If the code fragment generates undefined behavior, write [for undefined behavior]. Otherwise, write the output printed to standard output.

double z[4];
/* some other code here */
z[0] = 5.5;
z[1] = -z[0];
// C standard library function fabs declared in <math.h> returns the absolute value of a floating-point value
z[2] = z[3] = fabs(z[1]);
z[4] = z[0]+z[1]+z[2];
printf("%f", z[4]);

Brief side-note on undefined behavior: The C standard says that statements such as c = (b = a + 2) - (a = 1); and c = (b = a + 2) - (a = 1); cause undefined behavior [because we don't know whether the left or right operand of operator - is evaluated first]. When a program ventures into the realm of undefined behavior, all bets are off. The program may behave differently when compiled with different compilers. But that's not the only thing that can happen. The program may not compile in the first place, if it compiles it may not run, and if it does run, it may crash, behave erratically, or produce meaningless results. In other words, undefined behavior should be avoided like the plague.

Given the following code fragment:

/*
The C standard library header <limits.h> provides macros that define
the range of each integer type [including the character types]
*/
#include <limits.h>
unsigned short int x = USHRT_MAX;

write the exact value resulting from the evaluation of expression sizeof(x) when compiled using -bit GCC compiler.

Given the following code fragment:

/*
The C standard library header <float.h> provides macros that define the
range and accuracy of the float, double, and long double types.
Macros FLT_MAX, DBL_MAX, and LDBL_MAX provide the largest finite value that
can be represented by types float, double, and long double, respectively.
*/
#include <float.h>
double x = DBL_MAX;

write the exact value resulting from the evaluation of expression sizeof(x) when compiled using -bit GCC compiler.

Suppose you've defined an array named grades of  elements, each element of type int, and two of its elements are grades[1] and grades[4]. You know that ____________.

Does the following array definition compile?

int x[5] = {1};

Given the following code fragment:

/*
The C standard library header <limits.h> provides macros that define
the range of each integer type [including the character types]
*/
#include <limits.h>
signed int x = INT_MAX;

write the exact value resulting from the evaluation of expression sizeof(x) when compiled using -bit GCC compiler.

Each element in an array must have the same _________________ as the others.