All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] [RFC] Consolidated exception prologue/epiloge for x86 and ARM
Date: Fri, 27 Feb 2015 22:24:39 +0100	[thread overview]
Message-ID: <20150227212439.GQ434@hermes.click-hack.org> (raw)
In-Reply-To: <20150227212130.GP434@hermes.click-hack.org>

On Fri, Feb 27, 2015 at 10:21:30PM +0100, Gilles Chanteperdrix wrote:
> On Fri, Feb 27, 2015 at 09:37:45PM +0100, Jan Kiszka wrote:
> > On 2015-02-27 21:27, Gilles Chanteperdrix wrote:
> > > On Fri, Feb 27, 2015 at 09:12:14PM +0100, Jan Kiszka wrote:
> > >> Hi,
> > >>
> > >> just pushed a first implementation of the general model that I proposed
> > >> for exception handling. You can find it at
> > >>
> > >> http://git.xenomai.org/ipipe-jki.git/log/?h=queues/trap-rework
> > > 
> > > Also, the clean way to pass virtual + physical flags is to use
> > > arch_mangle_bits. Using two longs (potentially 128 bits then) is
> > > completely useless since one of the longs simply has one significant
> > > bit.
> > 
> > The costs of mangling is higher than using two regs for passing that
> > data as-is, both binary and LOC-wise (tried it). Plus the code is more
> > readable.
> 
> That is false on ARM. On ARM gcc does not pass structs by values in
> registers. The values get passed on stack.

Sorry, misread the assembler. They are passed by registers, however
the registers get uselessly saved on stack, then restored to other
registers. 

struct foo {
	int x;
	int y;
};

int f(struct foo f)
{
	return f.x + f.y;
}

Gives, with -Os:
00000000 <f>:
   0:   b082            sub     sp, #8
   2:   ab02            add     r3, sp, #8
   4:   e903 0003       stmdb   r3, {r0, r1}
   8:   e89d 0009       ldmia.w sp, {r0, r3}
   c:   4418            add     r0, r3
   e:   b002            add     sp, #8
  10:   4770            bx      lr

-- 
					    Gilles.


  reply	other threads:[~2015-02-27 21:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 20:12 [Xenomai] [RFC] Consolidated exception prologue/epiloge for x86 and ARM Jan Kiszka
2015-02-27 20:24 ` Gilles Chanteperdrix
2015-02-27 20:37   ` Jan Kiszka
2015-02-27 20:39     ` Gilles Chanteperdrix
2015-02-27 20:47     ` Jan Kiszka
2015-02-27 20:50       ` Gilles Chanteperdrix
2015-03-02 17:40         ` Jan Kiszka
2015-03-02 17:42           ` Gilles Chanteperdrix
2015-02-27 20:27 ` Gilles Chanteperdrix
2015-02-27 20:37   ` Jan Kiszka
2015-02-27 21:21     ` Gilles Chanteperdrix
2015-02-27 21:24       ` Gilles Chanteperdrix [this message]
2015-03-02 17:39         ` Jan Kiszka
2015-03-02 17:41           ` Gilles Chanteperdrix
2015-03-02 17:45             ` Jan Kiszka
2015-03-02 17:47               ` Gilles Chanteperdrix
2015-03-02 17:49                 ` Jan Kiszka
2015-03-02 17:53                   ` Gilles Chanteperdrix
2015-03-02 18:53           ` Philippe Gerum
2015-03-02 19:17             ` Jan Kiszka
2015-03-02 20:31               ` Jan Kiszka
2015-03-03 14:26                 ` Philippe Gerum
2015-03-03 14:34                   ` Philippe Gerum
2015-03-03  8:31               ` Philippe Gerum

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=20150227212439.GQ434@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@xenomai.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.