|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ View Advanced ]
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Reproducibility |
Date Submitted |
Last Update |
|
0003804 |
[buildroot] Architecture Specific |
minor |
always |
06-16-08 03:40 |
06-16-08 03:40 |
|
|
Reporter |
tklas |
View Status |
public |
|
|
Assigned To |
buildroot |
|
Priority |
normal |
Resolution |
open |
|
|
Status |
assigned |
|
Product Version |
|
|
|
Summary |
0003804: GCC default ABI (EABI/OABI) on ARM depens on "GNU target suffix" |
|
Description |
When "GNU target suffix" (BR2_GNU_TARGET_SUFFIX) is set to linux-*gnueabi, GCC uses EABI as default, elsewhere it uses OABI. So when BR2_ARM_EABI is selected and BR2_GNU_TARGET_SUFFIX is not *gnueabi, some code is compiled with EABI and some with OABI. Compilation is succesfull, but applications may crash or do some mysterious things.
This problem shoud be documented and BR2_ARM_EABI & BR2_GNU_TARGET_SUFFIX combination should be checked before build.
|
|
Additional Information |
For example:
Most of uClibc is compiled with EABI, but the syscall numbers (sysnum.h) is generated for OABI. So the library calls OABI syscalls with EABI-formated arguments. Some of the resulting calls are broken and may cause unpredictable behavior.
|
|
|
Attached Files |
|
|
|
Relationships 
