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?
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.
Note: please avoid quoting entire emails in your replies, especially long ones like this, and in replies to a mailing list.
Loud and clear, guys. ;) (Also, I'll bet at least one person on this list is using emacs as a mail client; can't resist emacs jokes)