arm-none-eabi-gcc was crashed while building float point related code

Bug #1969997 reported by Dmytro Kryvyi
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GNU Arm Embedded Toolchain
New
Undecided
Unassigned

Bug Description

Hello,

I'm using recent ARM none eabi tools to build my project:

```
bios@bios-pro:~$ arm-none-eabi-gcc --version
arm-none-eabi-gcc (GNU Toolchain for the Arm Architecture 11.2-2022.02 (arm-11.14)) 11.2.1 20220111
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```

And it falls while building the float point related code:
```
float * a = ...
*a = (123.32F * (float)foo());

Struct initializing:
mystr_t str = { .a = 1, .my_float = 123.4F };
```

With following output:
```
Internal compiler error: Illegal instruction
   51 | .adc_units_per_kg = 1000.0F };
      | ^
0x1521b50 diagnostic_impl(rich_location*, diagnostic_metadata const*, int, char const*, __va_list_tag (*) [1], diagnostic_t)
 ???:0
0x15227d6 internal_error(char const*, ...)
 ???:0
0xb7838f crash_signal(int)
 ???:0
0x171b592 __gmpn_mul_basecase
 ???:0
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://bugs.linaro.org/> for instructions.

Internal compiler error: Illegal instruction
  156 | (*pFloatVoltage) = (((float)adc_voltage) / 1000.0f);
      | ^
0x1521b50 diagnostic_impl(rich_location*, diagnostic_metadata const*, int, char const*, __va_list_tag (*) [1], diagnostic_t)
 ???:0
0x15227d6 internal_error(char const*, ...)
 ???:0
0xb7838f crash_signal(int)
 ???:0
0x171b592 __gmpn_mul_basecase
 ???:0
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://bugs.linaro.org/> for instructions.

```

Revision history for this message
Carlos GP (carlosgalvezp) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.