On Tue, 17 Sep 2019 at 17:54, Kyrill Tkachov
<kyrylo.tkac...@foss.arm.com> wrote:
>
>
> On 9/17/19 4:52 PM, Christophe Lyon wrote:
>
> On Tue, 17 Sep 2019 at 17:40, Kyrill Tkachov
> <kyrylo.tkac...@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?
>
>
> 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>
>
>
> Please use <code> markup for the triplet.
>
> Ok with that change.
>

Sorry for missing that.

Committed, thanks.

Christophe

> Thanks,
>
> Kyrill
>
>
>
> Thanks
>
> > Thanks,
> > Kyrill

Reply via email to