All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org,
	Julien Grall <julien.grall@linaro.org>,
	stefano.stabellini@citrix.com, tim@xen.org
Subject: Re: [PATCH v2 for 4.5] arm32: fix build after 063188f4b3
Date: Tue, 14 Oct 2014 14:18:03 +0100	[thread overview]
Message-ID: <1413292683.10417.56.camel@citrix.com> (raw)
In-Reply-To: <543D3D9F020000780003EBF4@mail.emea.novell.com>

On Tue, 2014-10-14 at 14:13 +0100, Jan Beulich wrote:
> >>> On 14.10.14 at 15:06, <julien.grall@linaro.org> wrote:
> > On 10/14/2014 01:57 PM, Ian Campbell wrote:
> >> On Tue, 2014-10-14 at 13:43 +0100, Julien Grall wrote:
> >>> On 10/14/2014 10:15 AM, Ian Campbell wrote:
> >>>> On Mon, 2014-10-13 at 16:29 +0100, Julien Grall wrote:
> >>>>> +int do_smc(register_t function_id, ...);
> >>>>
> >>>> Are you sure that the variadic function calling convention is the same
> >>>> as for a regular function call? I'm not entirely clear having read
> >>>> AAPCS, it says they are marshalled according to "the standard base". 
> >>>
> >>> All the parameters fits in a register, so the compiler will effectively
> >>> use the first registers to pass arguments.
> >> 
> >> Does it? Even with variadic functions? It's not unheard of for an ABI to
> >> fallback to pushing things onto the stack for such cases, since it works
> >> out far easier in stdargs.h.
> > 
> > You are right, it looks like it's compiler depend how variadic function
> > will be called.
> 
> Now that should never happen - there ought to be an ABI that all
> compilers abide by.

Agreed.

Ian.

  reply	other threads:[~2014-10-14 13:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13 15:29 [PATCH v2 for 4.5] arm32: fix build after 063188f4b3 Julien Grall
2014-10-13 15:39 ` Julien Grall
2014-10-13 15:49 ` Jan Beulich
2014-10-13 16:05   ` Julien Grall
2014-10-13 15:51 ` Jan Beulich
2014-10-13 16:05   ` Julien Grall
2014-10-13 16:06 ` Stefano Stabellini
2014-10-13 16:49   ` Julien Grall
2014-10-13 17:01     ` Stefano Stabellini
2014-10-13 17:05       ` Julien Grall
2014-10-14  9:15 ` Ian Campbell
2014-10-14 12:43   ` Julien Grall
2014-10-14 12:57     ` Ian Campbell
2014-10-14 13:06       ` Julien Grall
2014-10-14 13:13         ` Jan Beulich
2014-10-14 13:18           ` Ian Campbell [this message]
2014-10-14 19:09           ` Tim Deegan
2014-10-15  7:31             ` Ian Campbell
  -- strict thread matches above, loose matches on Subject: below --
2014-10-14 15:52 Julien Grall
2014-10-14 16:29 ` Jan Beulich
2014-10-14 16:31   ` Julien Grall

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=1413292683.10417.56.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@citrix.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.