On Tue, Feb 18, 2025 at 08:23:15PM +0100, Richard Biener wrote:
> > Am 18.02.2025 um 20:07 schrieb Roman Kagan :
> > On Tue, Feb 18, 2025 at 07:17:24PM +0100, Uros Bizjak wrote:
> >>> On Mon, Feb 17, 2025 at 6:19 PM Roman Kagan wrote:
> >>> On Thu, Jan 02, 2025 at 04:32:17PM +0100, Roman Kagan wro
On Tue, Feb 18, 2025 at 8:26 PM Uros Bizjak wrote:
>
> On Tue, Feb 18, 2025 at 8:23 PM Richard Biener wrote:
> >
> >
> >
> > > Am 18.02.2025 um 20:07 schrieb Roman Kagan :
> > >
> > > On Tue, Feb 18, 2025 at 07:17:24PM +0100, Uros Bizjak wrote:
> > >>> On Mon, Feb 17, 2025 at 6:19 PM Roman Kagan
On Tue, Feb 18, 2025 at 8:23 PM Richard Biener wrote:
>
>
>
> > Am 18.02.2025 um 20:07 schrieb Roman Kagan :
> >
> > On Tue, Feb 18, 2025 at 07:17:24PM +0100, Uros Bizjak wrote:
> >>> On Mon, Feb 17, 2025 at 6:19 PM Roman Kagan wrote:
> >>>
> >>> On Thu, Jan 02, 2025 at 04:32:17PM +0100, Roman K
> Am 18.02.2025 um 20:07 schrieb Roman Kagan :
>
> On Tue, Feb 18, 2025 at 07:17:24PM +0100, Uros Bizjak wrote:
>>> On Mon, Feb 17, 2025 at 6:19 PM Roman Kagan wrote:
>>>
>>> On Thu, Jan 02, 2025 at 04:32:17PM +0100, Roman Kagan wrote:
When gcc is built for x86_64-linux-musl target, sta
On Tue, Feb 18, 2025 at 07:17:24PM +0100, Uros Bizjak wrote:
> On Mon, Feb 17, 2025 at 6:19 PM Roman Kagan wrote:
> >
> > On Thu, Jan 02, 2025 at 04:32:17PM +0100, Roman Kagan wrote:
> > > When gcc is built for x86_64-linux-musl target, stack unwinding from
> > > within signal handler stops at the
On Mon, Feb 17, 2025 at 6:19 PM Roman Kagan wrote:
>
> On Thu, Jan 02, 2025 at 04:32:17PM +0100, Roman Kagan wrote:
> > When gcc is built for x86_64-linux-musl target, stack unwinding from
> > within signal handler stops at the innermost signal frame. The reason
> > for this behaviro is that the
On Thu, Jan 02, 2025 at 04:32:17PM +0100, Roman Kagan wrote:
> When gcc is built for x86_64-linux-musl target, stack unwinding from
> within signal handler stops at the innermost signal frame. The reason
> for this behaviro is that the signal trampoline is not accompanied with
> appropiate CFI dir
When gcc is built for x86_64-linux-musl target, stack unwinding from
within signal handler stops at the innermost signal frame. The reason
for this behaviro is that the signal trampoline is not accompanied with
appropiate CFI directives, and the fallback path in libgcc to recognize
it by the code