[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1511499747.3843.9.camel@synopsys.com>
Date: Fri, 24 Nov 2017 05:02:28 +0000
From: Alexey Brodkin <Alexey.Brodkin@...opsys.com>
To: "sudipm.mukherjee@...il.com" <sudipm.mukherjee@...il.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Vineet.Gupta1@...opsys.com" <Vineet.Gupta1@...opsys.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>
Subject: Re: [PATCH] frv: fix build failure
Hi Sudip,
On Thu, 2017-11-23 at 23:01 +0000, Sudip Mukherjee wrote:
> Hi Alexey,
>
> On Thu, Nov 23, 2017 at 05:17:19PM +0000, Alexey Brodkin wrote:
> >
> > Hi Sudip,
> >
> > On Tue, 2017-11-21 at 22:10 +0000, Sudip Mukherjee wrote:
> > >
> > > The frv defconfig build is failing with the error:
> > > lib/mpi/mpih-div.o: In function `mpihelp_divrem':
> > > mpih-div.c:(.text+0x30c): undefined reference to `abort'
> > >
> > > The function 'abort' was never defined for the frv architecture.
> > > Create 'abort' as is done in other arch like 'arm' and 'unicore32'.
> > >
> > > Signed-off-by: Sudip Mukherjee <sudipm.mukherjee@...il.com>
> > > ---
> >
> > I'm seeing the same issue building for ARC from today's Linus' tree.
> > Maybe it worth implementing abort() as a weak function for every arch/platform
> > that doesn't have it explicitly defined? Otherwise we'll end-up with
> > useless code duplication.
>
> Do you mean define it for every arch or define it in a common place so
> that all arch can use it?
Essentially I'd prefer to have just 1 instance of this function.
In fact I'd even remove existing implementations in ARM, Unicore32 and M32R
and have a generic implementation as this function obviously has nothing arch-specific.
> I did a quick try with the attached patch on two different arch, one of
> them (m32r) has the 'abort' defined and the other (frv) was failing due
> to lack of abort, and they both built without any warnings or errors.
Well maybe add call to panic() there as well as it is done for ARM, unicore32 and M32R?
> But I am not sure if 'kernel/exit.c' is the right place for it.
> Any suggestion?
I guess it should be indeed something in "kernel/" and maybe your existing choice
of "kernel/exit.c" is not bad. Just send a patch to LKML and you'll get much better
guidance on that I guess :)
Anyways thanks for looking at this one.
-Alexey
Powered by blists - more mailing lists