search for: pr36542

...ute__((target("arm,arch=cortex-a53"))) void h() { i(); } With -mcpu=cortex-m0 and get ARM code within an object claiming to be Thumb only with no errors or warnings, with no chance of a linker detecting a mismatch either. I think that part of this is the same problem that is observed in PR36542 the ARMAsmBackend that is responsible for widening the tail call to a Thumb2 branch is created with ARMv4T which doesn't support Thumb1. There has been a recent change that threads through the existing SubtargetInfo instead of recreating it from the triple alone. It is worth mentioning that the...

...entioned cleanup patch that unmasked this issue, I'd like to thank you for putting in the time to delve into things. The patches in question were: * https://reviews.llvm.org/rL321707 * https://reviews.llvm.org/rL321692 > I think that part of this is the same problem that is observed in > PR36542 the ARMAsmBackend that is responsible for widening the tail > call to a Thumb2 branch is created with ARMv4T which doesn't support > Thumb1. There has been a recent change that threads through the > existing SubtargetInfo instead of recreating it from the triple alone. > It is worth...

On 3/15/2018 9:43 AM, Peter Smith via llvm-dev wrote: > Hello everyone, this is most likely Arm specific, but could affect > other targets where there is a somewhat complex relationship between > the triple and mcpu option. > > At present when clang is used as a linker driver for the gold-plugin > and when using and an explicit -mcpu is not given to clang, then clang > will

Hello everyone, this is most likely Arm specific, but could affect other targets where there is a somewhat complex relationship between the triple and mcpu option. At present when clang is used as a linker driver for the gold-plugin and when using and an explicit -mcpu is not given to clang, then clang will always generate a -Wl,-plugin-opt=mcpu=<default CPU> where the default CPU is based