- On Jun 11, 2020, at 4:26 PM, Joseph Myers jos...@codesourcery.com wrote:
> On Thu, 11 Jun 2020, Mathieu Desnoyers wrote:
>
>> I managed to get a repository up and running for librseq, and have integrated
>> the rseq.2 man page with comments from Michael Kerrisk here:
>>
>>
- On Jun 18, 2020, at 8:22 AM, Szabolcs Nagy szabolcs.n...@arm.com wrote:
> The 06/11/2020 20:26, Joseph Myers wrote:
>> On Thu, 11 Jun 2020, Mathieu Desnoyers wrote:
>> > I managed to get a repository up and running for librseq, and have
>> > integrated
>> > the rseq.2 man page with
The 06/11/2020 20:26, Joseph Myers wrote:
> On Thu, 11 Jun 2020, Mathieu Desnoyers wrote:
> > I managed to get a repository up and running for librseq, and have
> > integrated
> > the rseq.2 man page with comments from Michael Kerrisk here:
> >
> >
On Thu, 11 Jun 2020, Mathieu Desnoyers wrote:
> I managed to get a repository up and running for librseq, and have integrated
> the rseq.2 man page with comments from Michael Kerrisk here:
>
> https://git.kernel.org/pub/scm/libs/librseq/librseq.git/tree/doc/man/rseq.2
>
> Is that a suitable URL
- On Jun 4, 2020, at 1:46 PM, Joseph Myers jos...@codesourcery.com wrote:
> On Thu, 4 Jun 2020, Mathieu Desnoyers via Libc-alpha wrote:
>
>> That external piece of documentation would be part of the Linux man-pages
>> project, maintained by Michael Kerrisk. I have submitted a few revisions
On Thu, 4 Jun 2020, Mathieu Desnoyers via Libc-alpha wrote:
> That external piece of documentation would be part of the Linux man-pages
> project, maintained by Michael Kerrisk. I have submitted a few revisions
> of the rseq(2) man page, but have been waiting for Michael to reply for more
> than
- On Jun 3, 2020, at 1:22 PM, Joseph Myers jos...@codesourcery.com wrote:
> On Wed, 3 Jun 2020, Florian Weimer via Libc-alpha wrote:
>
>> I'm still waiting for feedback from other maintainers whether the level
>> of documentation and testing is appropriate.
>
> Looking at the documentation
On Wed, 3 Jun 2020, Florian Weimer via Libc-alpha wrote:
> I'm still waiting for feedback from other maintainers whether the level
> of documentation and testing is appropriate.
Looking at the documentation in the manual, it doesn't look like it has
enough information for someone to use this
- On Jun 3, 2020, at 8:31 AM, Florian Weimer fwei...@redhat.com wrote:
> * Mathieu Desnoyers:
>
>> - On Jun 3, 2020, at 8:05 AM, Florian Weimer fwei...@redhat.com wrote:
>>
>>> * Mathieu Desnoyers:
>>>
+#ifdef __cplusplus
+# if __cplusplus >= 201103L
+# define
* Mathieu Desnoyers:
> - On Jun 3, 2020, at 8:05 AM, Florian Weimer fwei...@redhat.com wrote:
>
>> * Mathieu Desnoyers:
>>
>>> +#ifdef __cplusplus
>>> +# if __cplusplus >= 201103L
>>> +# define __rseq_static_assert(expr, diagnostic) static_assert (expr,
>>> diagnostic)
>>> +# define
- On Jun 3, 2020, at 8:05 AM, Florian Weimer fwei...@redhat.com wrote:
> * Mathieu Desnoyers:
>
>> +#ifdef __cplusplus
>> +# if __cplusplus >= 201103L
>> +# define __rseq_static_assert(expr, diagnostic) static_assert (expr,
>> diagnostic)
>> +# define __rseq_alignof(type)
* Mathieu Desnoyers:
> +#ifdef __cplusplus
> +# if __cplusplus >= 201103L
> +# define __rseq_static_assert(expr, diagnostic) static_assert (expr,
> diagnostic)
> +# define __rseq_alignof(type) alignof (type)
> +# define __rseq_alignas(x) alignas (x)
>
12 matches
Mail list logo