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 13:33:07 +0300 Message-ID: <83mv4uhvdo.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> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1507977240 4175 195.159.176.226 (14 Oct 2017 10:34:00 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 14 Oct 2017 10:34:00 +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 12:33:53 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 1e3JlL-00087n-Ao for ged-emacs-devel@m.gmane.org; Sat, 14 Oct 2017 12:33:47 +0200 Original-Received: from localhost ([::1]:53503 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3JlS-0002wM-O2 for ged-emacs-devel@m.gmane.org; Sat, 14 Oct 2017 06:33:54 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34052) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3Jkv-0002w1-Ld for emacs-devel@gnu.org; Sat, 14 Oct 2017 06:33:22 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e3Jko-0008V5-6y for emacs-devel@gnu.org; Sat, 14 Oct 2017 06:33:17 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:43508) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3Jko-0008V0-3L; Sat, 14 Oct 2017 06:33:14 -0400 Original-Received: from [176.228.60.248] (port=3600 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1e3Jkn-0004Ng-Df; Sat, 14 Oct 2017 06:33:13 -0400 In-reply-to: (message from Andreas Schwab on Sat, 14 Oct 2017 11:30:07 +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:219501 Archived-At: > From: Andreas Schwab > Cc: Eli Zaretskii , fabrice.popineau@gmail.com, emacs-devel@gnu.org > Date: Sat, 14 Oct 2017 11:30:07 +0200 > > On Okt 14 2017, Paul Eggert wrote: > > > Eli Zaretskii wrote: > >> What is special about this specific struct that it needs such an > >> alignment? > > > > The answer to this question is MS-Windows specific, and I don't know > > exactly which member of struct thread_state requires 16-byte alignment. I > > just know it's in there somewhere.... > > Obvious candidates are sys_thread_t and sys_cond_t, of course. Can you explain why? E.g., with pthreads, sys_thread_t is pthread_t, which AFAIU is the same width as 'int', in which case it won't force any 16-byte alignment anywhere. Also, all the members which have the sys_thread_t and sys_cond_t types are after the problematic members in the struct offset order, so how can they affect the alignment of the problematic members or of the struct itself? Thanks.