From: "Jan Beulich" <JBeulich@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Julien Grall <julien.grall@arm.com>,
nd@arm.com, Stefano Stabellini <stefanos@xilinx.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v4 2/2] xen: use SYMBOL when required
Date: Mon, 07 Jan 2019 00:39:25 -0700 [thread overview]
Message-ID: <5C33022D020000780020A9D1@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1901040853520.800@sstabellini-ThinkPad-X260>
>>> On 04.01.19 at 18:05, <sstabellini@kernel.org> wrote:
> I realize that you are not convinced by these arguments, but let's find
> a way forward. My preference would be to have SYMBOL returning unsigned
> long and do unsigned long comparisons when pointers pointing to
> different objects are involved.
I continue to fail to see how suitable hiding of the connection to the
original symbol from the compiler makes code less standard compliant
when comparing pointers: The compiler simply can't know whether
the underlying object is (in the extreme case) an array spanning the
entire address space.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-01-07 7:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 23:06 [PATCH v4 0/2] misc safety certification fixes Stefano Stabellini
2018-11-12 23:06 ` [PATCH v4 1/2] xen: introduce SYMBOL Stefano Stabellini
2018-11-12 23:06 ` [PATCH v4 2/2] xen: use SYMBOL when required Stefano Stabellini
2018-11-13 12:56 ` Jan Beulich
2018-11-13 13:17 ` Julien Grall
2018-11-13 13:27 ` Jan Beulich
2018-11-13 22:02 ` Stefano Stabellini
2018-11-14 7:44 ` Jan Beulich
2019-01-02 18:20 ` Stefano Stabellini
2019-01-04 8:48 ` Jan Beulich
2019-01-04 17:05 ` Stefano Stabellini
2019-01-07 7:39 ` Jan Beulich [this message]
2019-01-07 18:29 ` Stefano Stabellini
2019-01-08 8:03 ` Jan Beulich
2019-01-08 17:36 ` Stefano Stabellini
2019-01-08 18:08 ` Stefano Stabellini
2019-01-08 18:43 ` Julien Grall
2019-01-09 9:39 ` Jan Beulich
2019-01-09 23:50 ` Stefano Stabellini
2019-01-02 18:20 ` Stefano Stabellini
2019-01-02 21:04 ` Stefano Stabellini
2019-01-03 19:22 ` Stefano Stabellini
2018-12-20 17:26 ` [PATCH v4 0/2] misc safety certification fixes Julien Grall
2018-12-21 9:27 ` Jan Beulich
2018-12-21 10:34 ` Julien Grall
2018-12-21 17:15 ` Stefano Stabellini
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=5C33022D020000780020A9D1@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien.grall@arm.com \
--cc=nd@arm.com \
--cc=sstabellini@kernel.org \
--cc=stefanos@xilinx.com \
--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.