From: Finn Thain <fthain@telegraphics.com.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
LKML <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org
Subject: Re: m68k allmodconfig build errors
Date: Fri, 27 Jul 2018 14:44:17 +1000 (AEST) [thread overview]
Message-ID: <alpine.LNX.2.21.1807271428300.65@nippy.intranet> (raw)
In-Reply-To: <761399f0-0b10-716c-1e80-cfb19c06e455@infradead.org>
On Thu, 26 Jul 2018, Randy Dunlap wrote:
> >
> > The untested patch below may work. It seems that it may be relevant to
> > both arc and m68k:
>
>
> I got back to looking at the build errors. I agree with Andreas that
> all of the fields in question are null-terminated, so Finn's patch looks
> good to me.
>
>
That patch is insufficient:
ERROR: "strcmp" [fs/hfsplus/hfsplus.ko] undefined!
And I haven't even attempted "make ARCH=m68k ... allyesconfig" let alone
"make ARCH=arc ... allyesconfig".
And we have to anticipate an ongoing game of whack-a-mole here, as new
library calls get added to linux and new optimizations get added to gcc.
The real problem here seems to be a compiler bug: converting strncmp to
strcmp is bogus. Some implicit assumptions in that code transformation:
1. that strcmp is equivalient to strncmp in this case
2. that strcmp is faster than strncmp in this case
3. that strcmp is actually available to the linker
Why doesn't gcc convert strncmp to __builtin_strcmp? That would require
fewer assumptions, and it would actually link, and we wouldn't have to
keep patching things...
--
next prev parent reply other threads:[~2018-07-27 4:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 22:39 Randy Dunlap
2018-07-20 5:17 ` Finn Thain
2018-07-24 1:49 ` Randy Dunlap
2018-07-20 7:20 ` Andreas Schwab
2018-07-24 1:52 ` Randy Dunlap
2018-07-24 4:49 ` Finn Thain
2018-07-26 19:29 ` Randy Dunlap
2018-07-27 4:44 ` Finn Thain [this message]
2018-07-27 8:40 ` Andreas Schwab
2018-07-27 12:51 ` Finn Thain
2018-07-24 17:35 ` Andreas Schwab
2018-09-26 7:44 ` Geert Uytterhoeven
2018-09-26 16:09 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.21.1807271428300.65@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=rdunlap@infradead.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®