On Wed, May 15, 2019 at 7:54 PM 'Nick Desaulniers' via Clang Built Linux clang-built-linux@googlegroups.com wrote:
On Tue, May 14, 2019 at 11:35 PM Arnd Bergmann arnd@arndb.de wrote:
multi_v7_defconfig is the one that matters most, since that is supposed to work on all modern hardware. Aside from that, I would always prioritize bugs that affect multiple configurations.
How do I tell whether they affect multiple configurations? Some have names like multi_*; are there others?
There is usually one defconfig per SoC family, and some SoCs are more common than others, but it's hard to come up with a list of "important" ones.
Looks like most of the below are suffering from a similar problem that I understand pretty well and will send patches later this week.
Right. What is actually going on here?
Those are compiler helper routines that you'd find in libgcc (these are distinct from compiler builtins; maybe there's a more correct name than "compiler helper routines"). It's not possible to tell the compiler not to emit libcalls to these. You see these frequently for 64b operations on 32b hosts. Typically, these are copied from libgcc into the kernel. See the sources under arch/arm/lib/ for a few examples.
Yes, I know what these functions are, but from what I can tell, the link failure is for functions that are actually part of the kernel (__aeabi_idivmod, __aeabi_uidivmod), and exported from armksyms.c, so they should not cause the link failure.
Arnd