From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Suriyan Ramasami <suriyan.r@gmail.com>, TimDeegan <tim@xen.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] arm32: fix build after 063188f4b3
Date: Fri, 10 Oct 2014 16:26:33 +0100 [thread overview]
Message-ID: <1412954793.27111.53.camel@eu.citrix.com> (raw)
In-Reply-To: <54380F2C020000780003DD9A@mail.emea.novell.com>
On Fri, 2014-10-10 at 15:54 +0100, Jan Beulich wrote:
> >>> On 10.10.14 at 16:17, <Ian.Campbell@eu.citrix.com> wrote:
> > On Fri, 2014-10-10 at 14:58 +0100, Jan Beulich wrote:
> >> static noinline void exynos_smc(register_t function_id, register_t arg0,
> >> register_t arg1, register_t arg2)
> >> {
> >> + register register_t fn_id asm("r0") = function_id;
> >> + register register_t a0 asm("r1") = arg0;
> >> + register register_t a1 asm("r2") = arg1;
> >> + register register_t a2 asm("r3") = arg2;
> >
> > ISTR being told that the arm gcc backend pays this sort of asm("r1")
> > thing no heed (it's x86 specific?). This is how we ended up with the
> > asmeq -- it was what the arm compiler guys (via the arm kernels guys)
> > recommended.
>
> It is formally documented to play by this,
You made me look again and here it is
https://gcc.gnu.org/onlinedocs/gcc/Local-Reg-Vars.html
> so I don't think this is
> x86 specific, and I would strongly suspect any (apparent) violation
> of this to be either a misunderstanding of the guarantees that are
> being made or a bug in the specific compiler version.
I may well be misremembering the older discussions...
Either way, you retained the asmeq bits so even if there are broken
gcc's out there we won't produce broken binaries and your patch is a
clear improvement IMHO.
> > Stefano may remember better (since this was in the context of the Linux
> > hypervisor stub).
> >
> > I suppose you have a compiler which tickles this?
>
> Yes, the gcc 4.9.1 I use for testing the ARM builds.
I'm still on 4.8, I'll grab a 4.9 and use it occasionally...
Ian.
prev parent reply other threads:[~2014-10-10 15:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 13:58 [PATCH] arm32: fix build after 063188f4b3 Jan Beulich
2014-10-10 14:12 ` Julien Grall
2014-10-10 14:51 ` Jan Beulich
2014-10-10 15:55 ` Julien Grall
2014-10-10 16:01 ` Ian Campbell
2014-10-10 16:14 ` Julien Grall
2014-10-10 16:33 ` Ian Campbell
2014-10-10 16:35 ` Ian Campbell
2014-10-10 16:18 ` Jan Beulich
2014-10-10 16:35 ` Julien Grall
2014-10-10 14:17 ` Ian Campbell
2014-10-10 14:32 ` Stefano Stabellini
2014-10-10 14:58 ` Jan Beulich
2014-10-10 17:03 ` Stefano Stabellini
2014-10-13 6:49 ` Jan Beulich
2014-10-13 9:40 ` Stefano Stabellini
2014-10-13 10:34 ` Jan Beulich
2014-10-10 14:54 ` Jan Beulich
2014-10-10 15:26 ` Ian Campbell [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=1412954793.27111.53.camel@eu.citrix.com \
--to=ian.campbell@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=stefano.stabellini@citrix.com \
--cc=suriyan.r@gmail.com \
--cc=tim@xen.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.