From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs-26 threads problem [win64] Date: Sat, 14 Oct 2017 15:18:40 +0300 Message-ID: <83infhj527.fsf@gnu.org> References: <83h8v7r02e.fsf@gnu.org> <83vajnotik.fsf@gnu.org> <83r2ubosnd.fsf@gnu.org> <83fuaqpzaq.fsf@gnu.org> <837ew2pxx9.fsf@gnu.org> <83efq6khh3.fsf@gnu.org> <8ad9b8d2-1c9e-2db0-f166-58d08ea8321a@cs.ucla.edu> <837evyjkej.fsf@gnu.org> <6d41986e-2134-76df-ca37-2f394f1fa81e@cs.ucla.edu> <83shemi1ab.fsf@gnu.org> <1c1e89b4-74d6-cdd5-3251-0848f5cd9d87@cs.ucla.edu> <83mv4uhvdo.fsf@gnu.org> <8760bi7yog.fsf@linux-m68k.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1507983569 6686 195.159.176.226 (14 Oct 2017 12:19:29 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 14 Oct 2017 12:19:29 +0000 (UTC) Cc: eggert@cs.ucla.edu, fabrice.popineau@gmail.com, emacs-devel@gnu.org To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 14 14:19:23 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e3LPU-0000eV-7I for ged-emacs-devel@m.gmane.org; Sat, 14 Oct 2017 14:19:20 +0200 Original-Received: from localhost ([::1]:53907 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3LPb-0002G6-Cw for ged-emacs-devel@m.gmane.org; Sat, 14 Oct 2017 08:19:27 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51598) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3LOz-0002Fp-AQ for emacs-devel@gnu.org; Sat, 14 Oct 2017 08:18:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e3LOw-0005Of-MJ for emacs-devel@gnu.org; Sat, 14 Oct 2017 08:18:49 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:44640) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3LOw-0005Ob-Ip; Sat, 14 Oct 2017 08:18:46 -0400 Original-Received: from [176.228.60.248] (port=3714 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1e3LOv-0007sP-I3; Sat, 14 Oct 2017 08:18:46 -0400 In-reply-to: <8760bi7yog.fsf@linux-m68k.org> (message from Andreas Schwab on Sat, 14 Oct 2017 13:31:59 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:219511 Archived-At: > From: Andreas Schwab > Cc: eggert@cs.ucla.edu, fabrice.popineau@gmail.com, emacs-devel@gnu.org > 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?