On Mon, Feb 8, 2021 at 11:56 AM Josh Poimboeuf <[email protected]> wrote: > > On Fri, Feb 05, 2021 at 08:24:03AM -0600, Josh Poimboeuf wrote: > > The ORC unwinder attempts to fall back to frame pointers when ORC data > > is missing for a given instruction. It sets state->error, but then > > tries to keep going as a best-effort type of thing. That may result in > > further warnings if the unwinder gets lost. > > > > Until we have some way to register generated code with the unwinder, > > missing ORC will be expected, and occasionally going off the rails will > > also be expected. So don't warn about it. > > > > Signed-off-by: Josh Poimboeuf <[email protected]> > > Cc: [email protected]
I was the one who asked for this to be backported, since it solved the warnings for me. Tested-by: Ivan Babrou <[email protected]>
