From: "Marc Poulhiès" <poulhies@adacore.com>
To: Alex Coplan <alex.coplan@arm.com>
Cc: gcc-patches@gcc.gnu.org, Daniel King <dmking@adacore.com>
Subject: Re: [COMMITTED] ada: Add CHERI intrinsic bindings and helper functions.
Date: Thu, 22 Jun 2023 10:18:48 +0200 [thread overview]
Message-ID: <87352j3nh3.fsf@adacore.com> (raw)
In-Reply-To: <ZJIKVCDtxoJf+nK7@arm.com>
Hi Alex,
> On 20/06/2023 15:47, Marc Poulhiès wrote:
>> Hi,
>>
>> >> The package Interfaces.CHERI provides intrinsic bindings and
>> >> helper functions to allow software to query, create, and
>> >> manipulate CHERI capabilities.
>> >
>> > I'm curious what the motivation for these intrinsic wrappers is, given that
>> > GCC trunk doesn't currently support them. Out of interest, can you share what
>> > the use case for these is?
>>
>> We share the same Ada frontend with different GCC compilers and
>> contribute it in GCC's master branch.
>>
>> You're correct that this particular change is not useful (yet) with
>> master, but we are testing/using it with a CHERI-aware GCC.
>
> Interesting, I was only curious because we (Arm) are maintaining a branch with CHERI
> and Morello support in the ARM/morello vendor branch:
> https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/vendors/ARM/heads/morello
>
> is this a different CHERI GCC port that you're referring to?
No, we have used your morello branch as the starting point for our port
which consists in having the latest Ada frontend/runtime work there.
Marc
prev parent reply other threads:[~2023-06-22 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 7:47 Marc Poulhiès
2023-06-20 13:00 ` Alex Coplan
2023-06-20 13:47 ` Marc Poulhiès
2023-06-20 20:21 ` Alex Coplan
2023-06-22 8:18 ` Marc Poulhiès [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=87352j3nh3.fsf@adacore.com \
--to=poulhies@adacore.com \
--cc=alex.coplan@arm.com \
--cc=dmking@adacore.com \
--cc=gcc-patches@gcc.gnu.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 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).