diff options
| author | Tomasz Maciej Nowak <tomek_n@o2.pl> | 2020-03-18 19:04:12 +0100 |
|---|---|---|
| committer | Hauke Mehrtens <hauke@hauke-m.de> | 2020-04-18 00:18:13 +0200 |
| commit | 67ed408af20c3b24725f051596028345497219d8 (patch) | |
| tree | d4b5b85b99efcb896c78fc099174576ad3e3f0d8 /tools | |
| parent | dee8fcfe9f84b584073ca28349c3c04634650744 (diff) | |
| download | upstream-67ed408af20c3b24725f051596028345497219d8.tar.gz upstream-67ed408af20c3b24725f051596028345497219d8.tar.bz2 upstream-67ed408af20c3b24725f051596028345497219d8.zip | |
mvebu: cortexa9: correct cpu subtype
Armada 370 processors have only 16 double-precision registers. The
change introduced by 8dcc1087602e ("toolchain: ARM: Fix toolchain
compilation for gcc 8.x") switched accidentally the toolchain for mvebu
cortexa9 subtarget to cpu type with 32 double-precision registers. This
stems from gcc defaults which assume "vfpv3-d32" if only "vfpv3" as mfpu
is specified. That change resulted in unusable image, in which kernel
will kill userspace as soon as it causing "Illegal instruction".
Ref: https://forum.openwrt.org/t/gcc-was-broken-on-mvebu-armada-370-device-after-commit-on-2019-03-25/43272
Fixes: 8dcc1087602e ("toolchain: ARM: Fix toolchain compilation for
gcc 8.x")
Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
(cherry picked from commit 2d61f8821c7cf99354e904139226c132554ba180)
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions