[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs-26 threads problem [win64]
From: |
Eli Zaretskii |
Subject: |
Re: Emacs-26 threads problem [win64] |
Date: |
Sat, 14 Oct 2017 15:18:40 +0300 |
> From: Andreas Schwab <address@hidden>
> Cc: address@hidden, address@hidden, address@hidden
> Date: Sat, 14 Oct 2017 13:31:59 +0200
>
> Actually the most obvious candiate is m_getcjmp.
Which is again later in the struct than the member which caused the
segfault.
But the important question is IMO: why did GCC emit the movaps
instruction? why did it assume that struct thread_state must be
16-byte aligned? What am I missing here?
- Re: Emacs-26 threads problem [win64], (continued)
- Re: Emacs-26 threads problem [win64], Paul Eggert, 2017/10/13
- Re: Emacs-26 threads problem [win64], Eli Zaretskii, 2017/10/14
- Re: Emacs-26 threads problem [win64], Paul Eggert, 2017/10/14
- Re: Emacs-26 threads problem [win64], Eli Zaretskii, 2017/10/14
- Re: Emacs-26 threads problem [win64], Paul Eggert, 2017/10/14
- Re: Emacs-26 threads problem [win64], Andreas Schwab, 2017/10/14
- Re: Emacs-26 threads problem [win64], Eli Zaretskii, 2017/10/14
- Re: Emacs-26 threads problem [win64], Andreas Schwab, 2017/10/14
- Re: Emacs-26 threads problem [win64],
Eli Zaretskii <=
- Re: Emacs-26 threads problem [win64], Andreas Schwab, 2017/10/14
- Re: Emacs-26 threads problem [win64], Eli Zaretskii, 2017/10/14
- Re: Emacs-26 threads problem [win64], Paul Eggert, 2017/10/14
- Re: Emacs-26 threads problem [win64], Eli Zaretskii, 2017/10/15
- Re: Emacs-26 threads problem [win64], Andreas Schwab, 2017/10/15
- Re: Emacs-26 threads problem [win64], Eli Zaretskii, 2017/10/15
- Re: Emacs-26 threads problem [win64], Stefan Monnier, 2017/10/15
- Re: Emacs-26 threads problem [win64], Eli Zaretskii, 2017/10/15
- Re: Emacs-26 threads problem [win64], Andreas Schwab, 2017/10/15
- Re: Emacs-26 threads problem [win64], Andreas Schwab, 2017/10/14