Floating point cost on embedded systems in Embedded C - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Floating point vs integer addition timing

Consider the following embedded C code snippet that adds two numbers. What is the expected output on a typical microcontroller without hardware floating point support?

Embedded C

#include <stdio.h>
#include <time.h>

int main() {
    clock_t start, end;
    volatile float a = 1.5f, b = 2.5f, c;
    volatile int x = 1, y = 2, z;
    start = clock();
    for (int i = 0; i < 1000000; i++) {
        c = a + b;
    }
    end = clock();
    double float_time = (double)(end - start) / CLOCKS_PER_SEC;

    start = clock();
    for (int i = 0; i < 1000000; i++) {
        z = x + y;
    }
    end = clock();
    double int_time = (double)(end - start) / CLOCKS_PER_SEC;

    printf("Float add time: %.3f\nInt add time: %.3f\n", float_time, int_time);
    return 0;
}

A Both operations cause a runtime error

B Float add time is about the same as Int add time

C Int add time is significantly higher than Float add time

D Float add time is significantly higher than Int add time

💡 Hint

Think about how microcontrollers handle floating point operations without special hardware.

On embedded systems without floating point hardware, floating point operations are done in software and are slower than integer operations done directly by the CPU.

🧠 Conceptual

intermediate

Why floating point operations are costly on embedded systems

Which of the following best explains why floating point operations are more costly on many embedded systems?

A Embedded systems have limited memory, so floating point numbers cannot be stored

B Most embedded CPUs lack hardware floating point units, so floating point math is done in software

C Embedded systems use only integer math by design and do not support floating point

D Floating point operations require special power supply voltages not available on embedded boards

💡 Hint

Consider the hardware capabilities of typical microcontrollers.

Many embedded CPUs do not have a floating point unit (FPU), so floating point math is emulated in software, which is slower than integer math done directly by the CPU.

🔧 Debug

advanced

Identifying floating point performance bottleneck

Given the following embedded C code, which line is most likely causing a performance bottleneck on a microcontroller without an FPU?

Embedded C

void process_data(float *data, int size) {
    float sum = 0.0f;
    for (int i = 0; i < size; i++) {
        sum += data[i];
    }
    // Use sum for something
}

A float sum = 0.0f;

B for (int i = 0; i < size; i++) {

C sum += data[i];

D // Use sum for something

💡 Hint

Look for the line that does floating point math inside a loop.

The line sum += data[i]; performs floating point addition repeatedly, which is slow on CPUs without hardware floating point support.

📝 Syntax

advanced

Floating point literal syntax in embedded C

Which of the following floating point literals is correctly written in embedded C?

A float x = 1.0f;

B float x = 1,0;

C float x = 1.0;

D float x = 1.f.0;

💡 Hint

Remember the suffix for single precision float literals in C.

In C, 1.0f is a float literal. 1.0 is double by default. Commas and multiple dots are invalid.

🚀 Application

expert

Reducing floating point cost in embedded systems

You want to optimize an embedded system program that uses many floating point calculations but runs slowly. Which approach will most effectively reduce floating point cost?

A Replace floating point variables with fixed-point integer math and scale values appropriately

B Increase the clock speed of the microcontroller to speed up floating point operations

C Use double precision floating point instead of single precision for accuracy

D Add more floating point variables to distribute the load

💡 Hint

Think about how to avoid slow floating point math on hardware without an FPU.

Fixed-point math uses integers to represent fractional numbers, avoiding slow software floating point emulation and improving performance on embedded systems without FPUs.

Practice

1. Why are floating point operations generally avoided on embedded systems?

easy

A. They require less memory than integer operations.

B. They consume more time and power compared to integer operations.

C. They always produce inaccurate results.

D. They are easier to implement than integer operations.

Solution

1. Step 1: Understand floating point vs integer operations

   Floating point operations involve more complex calculations than integer operations.

2. Step 2: Consider embedded system constraints

   Embedded systems have limited processing power and battery life, so slower and power-hungry operations are costly.

3. Final Answer:

   They consume more time and power compared to integer operations. -> Option B

4. Quick Check:

   Floating point cost = More time and power [OK]

Hint: Floating point = slower and power hungry on embedded [OK]

Common Mistakes:

• Thinking floating point uses less memory
• Assuming floating point is always more accurate
• Believing floating point operations are faster

2. Which of the following is the correct way to declare a floating point variable in embedded C?

easy

A. float temperature = 23.5;

B. int temperature = 23.5;

C. double temperature = '23.5';

D. float temperature = '23,5';

Solution

1. Step 1: Check variable type and value format

   Floating point variables use the keyword 'float' and values use dot (.) as decimal separator.

2. Step 2: Validate syntax correctness

   float temperature = 23.5; uses float and a correct decimal number with dot, so it is correct.

3. Final Answer:

   float temperature = 23.5; -> Option A

4. Quick Check:

   float with dot decimal = correct syntax [OK]

Hint: Use float keyword and dot decimal for floats [OK]

Common Mistakes:

• Using int for decimal numbers
• Using quotes around numbers
• Using comma instead of dot for decimals

3. What is the main drawback of this embedded C code snippet?

float a = 1.5f;
float b = 2.5f;
float c = a * b;
printf("%f", c);

medium

A. It uses floating point multiplication which is slower on embedded systems.

B. It will print an integer instead of a float.

C. It will cause a syntax error due to missing semicolons.

D. It uses incorrect format specifier in printf.

Solution

1. Step 1: Analyze the code operations

   The code multiplies two float variables and prints the result using %f, which is correct syntax.

2. Step 2: Consider embedded system performance

   Floating point multiplication is slower and consumes more power on embedded systems compared to integer operations.

3. Final Answer:

   It uses floating point multiplication which is slower on embedded systems. -> Option A

4. Quick Check:

   Floating point multiply = slower on embedded [OK]

Hint: Floating point math is slower than integer math [OK]

Common Mistakes:

• Thinking code has syntax errors
• Confusing format specifiers
• Assuming output is integer

4. Identify the error in this embedded C code snippet:

float x = 3.0;
int y = 2;
float z = x / y;
printf("%d", z);

medium

A. Variable z should be declared as int.

B. Division between float and int is not allowed.

C. Using %d to print a float variable causes incorrect output.

D. Missing semicolon after variable declarations.

Solution

1. Step 1: Check variable types and operations

   Variable z is float, result of float divided by int, which is valid and results in float.

2. Step 2: Check printf format specifier

   Using %d expects an int, but z is float, so output will be incorrect or undefined.

3. Final Answer:

   Using %d to print a float variable causes incorrect output. -> Option C

4. Quick Check:

   Printf %d with float = wrong output [OK]

Hint: Match printf format to variable type [OK]

Common Mistakes:

• Thinking division of float and int is invalid
• Assuming variable type declaration is wrong
• Ignoring printf format specifier importance

5. You want to optimize an embedded system program that calculates average sensor readings. Which approach best reduces floating point cost while keeping accuracy?

hard

A. Replace all floats with doubles for better precision.

B. Convert sensor readings to strings and parse them later.

C. Use floating point operations directly for all calculations.

D. Use integer arithmetic by scaling sensor values and divide after summing.

Solution

1. Step 1: Understand floating point cost and accuracy needs

   Floating point operations are costly; using integers scaled by a factor preserves accuracy and reduces cost.

2. Step 2: Evaluate options for optimization

   Use integer arithmetic by scaling sensor values and divide after summing. uses integer math with scaling, which is efficient and accurate. Replace all floats with doubles for better precision. increases cost. Use floating point operations directly for all calculations. ignores cost. Convert sensor readings to strings and parse them later. is inefficient and unnecessary.

3. Final Answer:

   Use integer arithmetic by scaling sensor values and divide after summing. -> Option D

4. Quick Check:

   Scale integers to avoid floats = efficient and accurate [OK]

Hint: Scale integers to avoid floats for efficiency [OK]

Common Mistakes:

• Assuming doubles are always better
• Ignoring floating point cost
• Using string conversions unnecessarily