On Fri, Jan 15, 2021 at 10:20:14AM -0700, Jonathan Corbet wrote:
> On Fri, 15 Jan 2021 17:12:51 +
> Mark Brown wrote:
>
> > On Fri, Jan 15, 2021 at 04:47:18PM +, Mark Rutland wrote:
> > > On Fri, Jan 15, 2021 at 02:24:46PM +, Mark Brown wrote:
> >
> > > > +3. Considerations
> >
On Fri, 15 Jan 2021 17:12:51 +
Mark Brown wrote:
> On Fri, Jan 15, 2021 at 04:47:18PM +, Mark Rutland wrote:
> > On Fri, Jan 15, 2021 at 02:24:46PM +, Mark Brown wrote:
>
> > > +3. Considerations
> > > + 3.1 Identifying successful termination
>
> > It looks like we for
On Fri, Jan 15, 2021 at 04:47:18PM +, Mark Rutland wrote:
> On Fri, Jan 15, 2021 at 02:24:46PM +, Mark Brown wrote:
> > +3. Considerations
> > + 3.1 Identifying successful termination
> It looks like we forgot to update this with the addition of the new
> section 3, so this need
Hi Mark,
On Fri, Jan 15, 2021 at 02:24:46PM +, Mark Brown wrote:
> +.. Table of Contents:
> +
> +1. Introduction
> +2. Requirements
> +3. Considerations
> + 3.1 Identifying successful termination
> + 3.2 Identifying unwindable code
> + 3.3 Unwinding across interru
On Fri, Jan 15, 2021 at 02:24:46PM +, Mark Brown wrote:
> From: Mark Rutland
>
> Add documentation for reliable stacktrace. This is intended to describe
> the semantics and to be an aid for implementing architecture support for
> HAVE_RELIABLE_STACKTRACE.
>
> Unwinding is a subtle area, and
5 matches
Mail list logo