All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] xsave/xrstor compilation error
Date: Thu, 24 Oct 2013 17:40:01 +0100	[thread overview]
Message-ID: <52694D61.7090902@siemens.com> (raw)
In-Reply-To: <5269414F.6020806@xenomai.org>

On 2013-10-24 16:48, Gilles Chanteperdrix wrote:
> On 10/24/2013 12:06 PM, Jan Kiszka wrote:
>> We
>> can, of course, replace the instructions with their obcodes (like the
>> kernel does), just makes the code more ugly.
> 
> Jan, please do this, even if it makes the code more ugly, it makes sense
> for the 2.6.3 release to continue working with the tools it already
> supported. No question for -forge, but we try hard to keep ABI
> compatibility so that users can upgrade xenomai without even recompiling
> their application, it does not make sense to suddenly stop working with
> a toolchain which always worked before.

In fact, we already have legacy gas support: all these new instructions
are wrapped with CONFIG_AS_AVX, and only if that is set we use the new
assembler instructions. Given that this CONFIG has to be set based on
some test, something seems to go wrong in the kernel build over there.
But that's outside of the Xenomai scope. I'm currently trying to find
out if there was some related kernel issue back then.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2013-10-24 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24  8:40 [Xenomai] xsave/xrstor compilation error Jean-Baptiste Tredez
2013-10-24 10:06 ` Jan Kiszka
2013-10-24 15:48   ` Gilles Chanteperdrix
2013-10-24 16:40     ` Jan Kiszka [this message]
2013-10-24 17:26       ` Jan Kiszka
2013-10-25  7:47         ` Jean-Baptiste Tredez

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=52694D61.7090902@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.