From: Jan Beulich <jbeulich@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Bertrand Marquis <Bertrand.Marquis@arm.com>,
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>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] xen: always consider '/' as a division in assembly
Date: Tue, 10 Feb 2026 17:09:29 +0100 [thread overview]
Message-ID: <d9b768cd-6454-4fab-a0bb-e2543c68402a@suse.com> (raw)
In-Reply-To: <aYtUkeoX273I8ABq@Mac.lan>
On 10.02.2026 16:53, Roger Pau Monné wrote:
> On Tue, Feb 10, 2026 at 04:27:33PM +0100, Jan Beulich wrote:
>> On 10.02.2026 16:11, Roger Pau Monne wrote:
>>> Pass --divide when when available to signal '/' is
>>> +# always used as an operator in assembly.
>>> +$(call cc-option-add,CFLAGS,CC,-Wa$$(comma)--divide)
>>
>> I don't think this should be done here: --divide is an x86-specific
>> option.
>
> Oh, that wasn't clear from the output of as. I can make it
> x86-specific then. However, is there any chance of this behavior
> escaping outside of x86, and hence would we like to ensure this
> behavior on all possible arches?
>
> Or is it possible that other arches re-use the --divide option for
> some other functionality?
It is equally possible for that to happen (if some target needs to
support '/' as a comment char) as it is for such a target to then use
an entirely different command line option. Furthermore, --divide may
mean something else on another arch.
Jan
next prev parent reply other threads:[~2026-02-10 16:09 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 [this message]
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
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=d9b768cd-6454-4fab-a0bb-e2543c68402a@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.