All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Anthony PERARD <anthony.perard@vates.tech>,
	Michal Orzel <michal.orzel@amd.com>,
	Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Bertrand Marquis <Bertrand.Marquis@arm.com>
Subject: Re: [PATCH] xen: always consider '/' as a division in assembly
Date: Tue, 10 Feb 2026 17:15:00 +0100	[thread overview]
Message-ID: <5d656a16-467e-4603-b5c6-e388303ecd38@suse.com> (raw)
In-Reply-To: <aYtYKlcoVAFvn8jh@Mac.lan>

On 10.02.2026 17:09, Roger Pau Monné wrote:
> On Tue, Feb 10, 2026 at 03:57:17PM +0000, Bertrand Marquis wrote:
>> Hi Roger
>>
>>> On 10 Feb 2026, at 16:55, Roger Pau Monné <roger.pau@citrix.com> wrote:
>>>
>>> On Tue, Feb 10, 2026 at 03:44:33PM +0000, Bertrand Marquis wrote:
>>>> Hi Roger,
>>>>
>>>>> On 10 Feb 2026, at 16:11, Roger Pau Monne <roger.pau@citrix.com> wrote:
>>>>>
>>>>> GNU assembler will consider '/' as the start of comment marker on some
>>>>> platforms.  This is incorrect with Xen's usage, which does use '/' in
>>>>> assembly files as a mathematical operator.
>>>>>
>>>>> The behavior of the assembler can be altered by passing the --divide
>>>>> option; unconditionally pass this option when available to force the
>>>>> expected behavior.
>>>>
>>>> This is solving the issue and I can build for arm with what and further
>>>> for x86 on mac os but it fails on check-endbr.sh:
>>>>
>>>> /bin/sh ../tools/check-endbr.sh xen-syms
>>>> stat: illegal option -- c
>>>
>>> Yeah, I know.  I've fixed the stat issue, but there's a further one
>>> about an illegal bit sequence in grep.  I'm looking into that.
>>
>> LC_ALL=C grep is fixing that one on my side
> 
> I haven't tested that one yet, but yes, might be a way to solve.
> Would you like to send the fix for grep?
> 
>> with that and stat -c replaced with wc -c < xx I can fully compile x86 on Mac os.
> 
> Yeah, the problem with using wc is that you have to read the file.  I
> prefer $(($(du <file> |cut -w -f1) << 9)) because that avoids reading
> the actual data to count.

But shifting by hardcoded 9 doesn't look very portable. The size not being
exact may be okay for the purposes here, but wouldn't it then be better to
use (standardized) ls output?

Jan


  reply	other threads:[~2026-02-10 16:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 15:11 [PATCH] xen: always consider '/' as a division in assembly Roger Pau Monne
2026-02-10 15:27 ` Jan Beulich
2026-02-10 15:53   ` Roger Pau Monné
2026-02-10 16:09     ` Jan Beulich
2026-02-10 15:44 ` Bertrand Marquis
2026-02-10 15:55   ` Roger Pau Monné
2026-02-10 15:57     ` Bertrand Marquis
2026-02-10 16:09       ` Roger Pau Monné
2026-02-10 16:15         ` Jan Beulich [this message]
2026-02-10 16:19           ` Bertrand Marquis
2026-02-10 16:20         ` Bertrand Marquis

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=5d656a16-467e-4603-b5c6-e388303ecd38@suse.com \
    --to=jbeulich@suse.com \
    --cc=Bertrand.Marquis@arm.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.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.