From: Christophe Lyon <christophe.lyon@linaro.org>
To: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs] gcc-10/changes.html - Document new ARM FDPIC ABI support
Date: Tue, 17 Sep 2019 15:52:00 -0000 [thread overview]
Message-ID: <CAKdteOaLCRegq3nDupF0Rexh_n8+kAwC2Rt5Cm-wwYW5iLbcSA@mail.gmail.com> (raw)
In-Reply-To: <c2c10636-b62d-8d6b-e9bb-ae9abaa2d1ee@foss.arm.com>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On Tue, 17 Sep 2019 at 17:40, Kyrill Tkachov
<kyrylo.tkachov@foss.arm.com> wrote:
>
> Hi Christophe,
>
> On 9/17/19 4:38 PM, Christophe Lyon wrote:
>
> Hi,
>
> As Kyrill suggested, here is a patch to mention the new FDPIC ABI
> support for arm.
> OK?
>
> Thanks,
>
> Christophe
>
>
> fdpic-wwwdocs.patch.txt
>
> Index: changes.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-10/changes.html,v
> retrieving revision 1.14
> diff -r1.14 changes.html
> 139,140c139,145
> < <!-- <h3 id="arm">ARM</h3> -->
> <
> ---
>
> <h3 id="arm">ARM</h3>
> <ul>
> <li>Support for the FDPIC ABI has been added. It uses 64-bit
> function descriptors to represent points to functions, and enables
> code sharing on MMU-less systems.
> </li>
> </ul>
>
>
> I think we'll want to mention how the new functionality is accessed, so can you please mention the required triple and/or command-line options that you expect the users to specify?
Sure, sorry for forgetting about it and for the typo.
How about his?
Thanks
> Thanks,
> Kyrill
[-- Attachment #2: fdpic-wwwdocs.patch.txt --]
[-- Type: text/plain, Size: 568 bytes --]
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-10/changes.html,v
retrieving revision 1.14
diff -r1.14 changes.html
139,140c139,146
< <!-- <h3 id="arm">ARM</h3> -->
<
---
> <h3 id="arm">ARM</h3>
> <ul>
> <li>Support for the FDPIC ABI has been added. It uses 64-bit
> function descriptors to represent pointers to functions, and enables
> code sharing on MMU-less systems. The corresponding target triple is
> arm-uclinuxfdpiceabi, and the C library is uclibc-ng.
> </li>
> </ul>
next prev parent reply other threads:[~2019-09-17 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 15:38 Christophe Lyon
2019-09-17 15:40 ` Kyrill Tkachov
2019-09-17 15:52 ` Christophe Lyon [this message]
2019-09-17 15:54 ` Kyrill Tkachov
2019-09-17 19:26 ` Christophe Lyon
2019-09-17 15:41 ` Richard Earnshaw (lists)
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=CAKdteOaLCRegq3nDupF0Rexh_n8+kAwC2Rt5Cm-wwYW5iLbcSA@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@foss.arm.com \
/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).