From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Florian Bezdeka <florian.bezdeka@siemens.com>,
xenomai@lists.linux.dev,
Clara Kowalsky <clara.kowalsky@siemens.com>
Subject: Re: Removal of arm OABI support possible?
Date: Tue, 08 Aug 2023 15:40:34 +0200 [thread overview]
Message-ID: <87leel646o.fsf@xenomai.org> (raw)
In-Reply-To: <6c3240eb-896b-403b-3a36-d85fe24f8b5c@siemens.com>
Jan Kiszka <jan.kiszka@siemens.com> writes:
> On 07.08.23 15:29, Florian Bezdeka wrote:
>> Hi all,
>>
>> Clara is currently trying to enable compat support for arm64. That will
>> allow us to run arm(hf) applications on arm64 kernels like we do it for
>> i386 applications on x86_64 kernels.
>>
>> We fixed the Xenomai arm specific register layout in a way that is
>> compatible to arm64. That looks promising as the testsuite (smokey) can
>> already be executed successfully in such a compat environment.
>>
>> The changes we made affect the EABI only and we left the OABI interface
>> untouched and expect it to be broken right now. We can't really test it
>> here...
>>
>> Is there still the need for OABI support in Xenomai? OABI is marked as
>> obsolete since gcc > 4.6.4 (~2013) and Debian stopped shipping oabi
>> toolchains long time ago. Would it be accepted if we simply drop the
>> OABI support of Xenomai?
>
> From Xenomai 3 perspective, it would be fine to finally drop that with
> the 3.3 release - patch(es) welcome.
>
> Not sure, though, how the situation of Xenomai 4 / EVL is in this regard
> - Philippe?
>
Having support for OABI was not even considered wrt neither EVL nor
Dovetail (would require specific syscall handling which is not there),
so it is safe to drop it entirely from any current Xenomai 3 codebase.
--
Philippe.
prev parent reply other threads:[~2023-08-08 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 13:29 Removal of arm OABI support possible? Florian Bezdeka
2023-08-08 12:30 ` Jan Kiszka
2023-08-08 13:32 ` Florian Bezdeka
2023-08-08 13:40 ` Philippe Gerum [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=87leel646o.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=clara.kowalsky@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).