All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Xenomai <xenomai@xenomai.org>, Greg Gallagher <greg@embeddedgreg.com>
Subject: Re: Arm userland not building with gcc-9 and later
Date: Sun, 08 Aug 2021 19:55:49 +0200	[thread overview]
Message-ID: <87mtpr4y8q.fsf@xenomai.org> (raw)
In-Reply-To: <4b29def3-7900-7be2-a66b-e2e3482c9476@siemens.com>


Jan Kiszka <jan.kiszka@siemens.com> writes:

> On 08.08.21 19:21, Philippe Gerum wrote:
>> 
>> Jan Kiszka <jan.kiszka@siemens.com> writes:
>> 
>>> On 07.08.21 19:00, Philippe Gerum wrote:
>>>>
>>>> Jan Kiszka <jan.kiszka@siemens.com> writes:
>>>>
>>>>> Hi all,
>>>>>
>>>>> just wanted to debug the RTnet issues we now see in CI on arm and arm64.
>>>>> I picked arm as first target, but that apparently starts to break with
>>>>> gcc-9 or newer (tried 9.2 and 10.2):
>>>>>
>>>>> make[5]: Entering directory '/xenomai/lib/cobalt/arch/arm'
>>>>>   CC       libarch_la-features.lo
>>>>> features.c: In function 'cobalt_arch_check_features':
>>>>> features.c:82:1: error: r7 cannot be used in 'asm' here
>>>>>    82 | }
>>>>>       | ^
>>>>>
>>>>> That seems to be related to passing the syscall number via r7 on ARM. Is
>>>>> our ABI soon no longer compilable, or can we fix this?
>>>>>
>>>>
>>>> Just tried to reproduce this issue with the latest stable (10.3-2021.07)
>>>> from ARM [1], and a fairly recent linaro snapshot (11.0.1-2021.03) [2],
>>>> to no avail. I tried with --enable-debug=symbols, --disable-debug,
>>>> --enable-debug=full, no issue so far.
>>>>
>>>> Can you please share you configure settings?
>>>
>>> I'm on ARM gcc 10.3-2021.07 as well. Debian's gcc from bullseye show 
>>> this, too.
>>>
>>> ./configure --host=arm-none-linux-gnueabihf --enable-debug=full
>>>
>>> on master. And that results in
>>>
>>>   CC       libarch_la-features.lo
>>> ../../../../../lib/cobalt/arch/arm/features.c: In function ‘cobalt_arch_check_features’:
>>> ../../../../../lib/cobalt/arch/arm/features.c:82:1: error: r7 cannot be used in ‘asm’ here
>>>    82 | }
>>>       | ^
>>>
>> 
>> Confirmed, found it. next is fine with this compiler, which is the
>> version I tested. However, building stable and master does break.
>> 
>
> Yeah, I've already pushed the two related fixes into next for testing.
> Can still be changed if we find a better solution.
>

Ack.

-- 
Philippe.


  reply	other threads:[~2021-08-08 17:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06 13:00 Arm userland not building with gcc-9 and later Jan Kiszka
2021-08-06 13:09 ` Philippe Gerum
2021-08-06 13:14   ` Jan Kiszka
2021-08-06 13:34     ` Philippe Gerum
2021-08-06 16:16       ` Jan Kiszka
2021-08-06 17:12         ` Jan Kiszka
2021-08-07 17:00 ` Philippe Gerum
2021-08-08 16:55   ` Jan Kiszka
2021-08-08 17:21     ` Philippe Gerum
2021-08-08 17:30       ` Jan Kiszka
2021-08-08 17:55         ` Philippe Gerum [this message]
2021-08-09 12:00 ` Jan Kiszka

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=87mtpr4y8q.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=greg@embeddedgreg.com \
    --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.