From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: YunQiang Su <wzssyqa@gmail.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
linux-mips <linux-mips@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: build failure of malta_qemu_32r6_defconfig
Date: Fri, 9 Apr 2021 14:16:37 +0200 [thread overview]
Message-ID: <20210409121637.GA13010@alpha.franken.de> (raw)
In-Reply-To: <CAKcpw6VrbA2+mq42=0FjE7Y9e6OM-Q9WxvYPWtAF4t0hRWKB1A@mail.gmail.com>
On Thu, Apr 08, 2021 at 09:42:11AM +0800, YunQiang Su wrote:
> Sudip Mukherjee <sudipm.mukherjee@gmail.com> 于2021年4月8日周四 上午2:26写道：
> >
> > Hi Thomas,
> >
> > I was building v5.10.28 with malta_qemu_32r6_defconfig and noticed that
> > it fails to build, so tried next-20210407 to see if it has been fixed.
> > But linux-next also has the issue with gcc-10.
> >
> > The error is:
> >
> > ./arch/mips/include/asm/vdso/gettimeofday.h: In function '__vdso_clock_gettime':
> > ./arch/mips/include/asm/vdso/gettimeofday.h:103:2: error: the register 'lo' cannot be clobbered in 'asm' for the current target
> > 103 | asm volatile(
> > | ^~~
>
> this operation try to save lo and hi register, while they are not
> exisiting on r6.
> We are working on figure out a patch for it.
looks like there is already a patch in patchwork, which just needs
a workup:
https://patchwork.kernel.org/project/linux-mips/patch/20200801154401.4177009-1-romain.naour@gmail.com/
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2021-04-09 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 18:26 build failure of malta_qemu_32r6_defconfig Sudip Mukherjee
2021-04-08 1:42 ` YunQiang Su
2021-04-09 12:16 ` Thomas Bogendoerfer [this message]
2021-04-17 23:01 ` Sudip Mukherjee
2021-04-20 8:34 ` Thomas Bogendoerfer
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=20210409121637.GA13010@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=wzssyqa@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).