xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Roman Shaposhnik <roman@zededa.com>
To: Julien Grall <julien.grall.oss@gmail.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	 Stefano Stabellini <sstabellini@kernel.org>,
	Stefano Stabellini <stefano.stabellini@xilinx.com>
Subject: Re: Xen 4.14 build failing on aarch64 with GCC 10.2.1
Date: Mon, 15 Mar 2021 19:23:43 -0700	[thread overview]
Message-ID: <CAMmSBy-u8-=r20UimHdUvFDjcegraK+v=v5QhvhrtNk4j4TGDg@mail.gmail.com> (raw)
In-Reply-To: <CAJ=z9a1_BrnCzqdZ6xoc1VwTM8V0jr1B_rv=28fW5VSe2rwG4Q@mail.gmail.com>

On Wed, Mar 10, 2021 at 3:15 PM Julien Grall <julien.grall.oss@gmail.com> wrote:
>
> On Wed, 10 Mar 2021 at 21:15, Roman Shaposhnik <roman@zededa.com> wrote:
> >
> > Hi!
>
> Hi,
>
> >
> > just came across this failure on aarch64:
> >
> > ld: prelink.o: in function `_spin_lock_cb':
> > 19187(.text+0x1f26c): undefined reference to `__aarch64_ldadd4_acq_rel'
> > 19188ld: prelink.o: in function `_spin_lock':
> > 19189(.text+0x1f2ec): undefined reference to `__aarch64_ldadd4_acq_rel'
> > 19190ld: prelink.o: in function `_spin_lock_irq':
> > 19191(.text+0x1f35c): undefined reference to `__aarch64_ldadd4_acq_rel'
> > 19192ld: prelink.o: in function `_spin_lock_irqsave':
> > 19193(.text+0x1f3d4): undefined reference to `__aarch64_ldadd4_acq_rel'
> > 19194ld: prelink.o: in function `_spin_lock_recursive':
> > 19195(.text+0x1f6b0): undefined reference to `__aarch64_ldadd4_acq_rel'
> >
> > This, of course, goes away if I build Xen with:
> >    CFLAGS=-mno-outline-atomics
> >
> > However, at this point I'm curious if this is going to get addressed in Xen
> > proper or not.
>
> This has already been fixed and backported to Xen 4.14 (included in
> 4.14.1). Are you using the latest 4.14 branch?

Aaaand that appears to works as intended -- sorry for the noise -- I
thought I was using the latest, but apparently not.

Thanks,
Roman.


      reply	other threads:[~2021-03-16  2:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 21:15 Xen 4.14 build failing on aarch64 with GCC 10.2.1 Roman Shaposhnik
2021-03-10 23:14 ` Julien Grall
2021-03-16  2:23   ` Roman Shaposhnik [this message]

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='CAMmSBy-u8-=r20UimHdUvFDjcegraK+v=v5QhvhrtNk4j4TGDg@mail.gmail.com' \
    --to=roman@zededa.com \
    --cc=julien.grall.oss@gmail.com \
    --cc=sstabellini@kernel.org \
    --cc=stefano.stabellini@xilinx.com \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).