From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Emacs-26 threads problem [win64] Date: Sat, 14 Oct 2017 15:51:21 -0700 Organization: UCLA Computer Science Department Message-ID: <0eb00b68-7ff9-1a07-b756-8cf6219faf93@cs.ucla.edu> 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> <83infhj527.fsf@gnu.org> <871sm59a3n.fsf@linux-m68k.org> <83fualj0bu.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1508021544 29994 195.159.176.226 (14 Oct 2017 22:52:24 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 14 Oct 2017 22:52:24 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 Cc: fabrice.popineau@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii , Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 15 00:52:19 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 1e3VI2-000704-Qk for ged-emacs-devel@m.gmane.org; Sun, 15 Oct 2017 00:52:18 +0200 Original-Received: from localhost ([::1]:55400 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3VIA-0003HZ-3Z for ged-emacs-devel@m.gmane.org; Sat, 14 Oct 2017 18:52:26 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38910) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3VHL-0003Gr-5C for emacs-devel@gnu.org; Sat, 14 Oct 2017 18:51:35 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e3VHK-0006M0-Hh for emacs-devel@gnu.org; Sat, 14 Oct 2017 18:51:35 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:50444) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1e3VHG-0006JU-1n; Sat, 14 Oct 2017 18:51:30 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id EFD35160E54; Sat, 14 Oct 2017 15:51:26 -0700 (PDT) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id TEofY2h5C51f; Sat, 14 Oct 2017 15:51:26 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 3FE13160E58; Sat, 14 Oct 2017 15:51:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 2qbtKQR0HMN7; Sat, 14 Oct 2017 15:51:26 -0700 (PDT) Original-Received: from [192.168.1.9] (unknown [47.154.18.85]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id D29B2160E54; Sat, 14 Oct 2017 15:51:25 -0700 (PDT) In-Reply-To: <83fualj0bu.fsf@gnu.org> Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 131.179.128.68 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:219534 Archived-At: Eli Zaretskii wrote: > You are saying that some member of struct thread_state, probably > m_getcjmp, has a 16-byte alignment, at least in the 64-bit Windows > build. GCC sees that, and therefore deduces that the entire struct > must be 16-byte aligned, so it feels free to emit movaps in > conjunction with the m_stack_bottom member, which is at offset 64 > (decimal) from the struct base, and therefore should also be 16-byte > aligned. Is that correct? Yes.