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: Sun, 15 Oct 2017 20:19:28 +0300 Message-ID: <83efq4gwgv.fsf@gnu.org> References: <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> <0eb00b68-7ff9-1a07-b756-8cf6219faf93@cs.ucla.edu> <83mv4sh298.fsf@gnu.org> <874lr0zah1.fsf@linux-m68k.org> <83h8v0gyqv.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1508087994 4513 195.159.176.226 (15 Oct 2017 17:19:54 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 15 Oct 2017 17:19:54 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 15 19:19:46 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 1e3mZh-0007lN-NL for ged-emacs-devel@m.gmane.org; Sun, 15 Oct 2017 19:19:41 +0200 Original-Received: from localhost ([::1]:57920 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3mZl-00015s-TC for ged-emacs-devel@m.gmane.org; Sun, 15 Oct 2017 13:19:45 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41384) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3mZd-00015b-AT for emacs-devel@gnu.org; Sun, 15 Oct 2017 13:19:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e3mZa-0005CO-6H for emacs-devel@gnu.org; Sun, 15 Oct 2017 13:19:37 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39502) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3mZa-0005CG-2S; Sun, 15 Oct 2017 13:19:34 -0400 Original-Received: from [176.228.60.248] (port=1366 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1e3mZY-0003RZ-Vf; Sun, 15 Oct 2017 13:19:33 -0400 In-reply-to: (message from Stefan Monnier on Sun, 15 Oct 2017 12:41:18 -0400) 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:219555 Archived-At: > From: Stefan Monnier > Date: Sun, 15 Oct 2017 12:41:18 -0400 > > >> The malloc() and calloc() functions return a pointer to the allocated > >> memory, which is suitably aligned for any built-in type. > ^^^^^ > This implies it has to be at least aligned with max_align_t > IOW apparently on 64bit Windows malloc will return an object aligned on > a 16B boundary. I think you are right, as MSDN says about malloc: The storage space pointed to by the return value is guaranteed to be suitably aligned for storage of any type of object that has an alignment requirement less than or equal to that of the fundamental alignment. (In Visual C++, the fundamental alignment is the alignment that's required for a double, or 8 bytes. In code that targets 64-bit platforms, it’s 16 bytes.) So I guess this is the basis for GCC to assume 16-byte alignment. Thanks.