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 19:30:16 +0300 Message-ID: <83h8v0gyqv.fsf@gnu.org> References: <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> <0eb00b68-7ff9-1a07-b756-8cf6219faf93@cs.ucla.edu> <83mv4sh298.fsf@gnu.org> <874lr0zah1.fsf@linux-m68k.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1508085157 13891 195.159.176.226 (15 Oct 2017 16:32:37 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 15 Oct 2017 16:32:37 +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 Sun Oct 15 18:32:32 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 1e3lq2-0002pU-O8 for ged-emacs-devel@m.gmane.org; Sun, 15 Oct 2017 18:32:30 +0200 Original-Received: from localhost ([::1]:57815 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3lq9-0006vJ-VA for ged-emacs-devel@m.gmane.org; Sun, 15 Oct 2017 12:32:38 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34515) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3lo0-0005Yv-Kv for emacs-devel@gnu.org; Sun, 15 Oct 2017 12:30:25 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e3lnw-0000eD-En for emacs-devel@gnu.org; Sun, 15 Oct 2017 12:30:24 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39146) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3lnw-0000e7-AT; Sun, 15 Oct 2017 12:30:20 -0400 Original-Received: from [176.228.60.248] (port=1159 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1e3lnv-0001nV-Kd; Sun, 15 Oct 2017 12:30:20 -0400 In-reply-to: <874lr0zah1.fsf@linux-m68k.org> (message from Andreas Schwab on Sun, 15 Oct 2017 17:39:38 +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:219552 Archived-At: > From: Andreas Schwab > Cc: Paul Eggert , fabrice.popineau@gmail.com, emacs-devel@gnu.org > Date: Sun, 15 Oct 2017 17:39:38 +0200 > > > OOC, when a program does > > > > struct foo *ptr = malloc (sizeof struct foo); > > > > how is the alignment of the resulting pointer arranged to be "the > > maximum of the struct members"? > > RTFM: > > The malloc() and calloc() functions return a pointer to the allocated > memory, which is suitably aligned for any built-in type. I did, and thus my question: is GCC correct assuming movaps can be used on a member of an arbitrary struct, if allocating that struct is not guaranteed to produce the alignment expected by that instruction, unless the program used aligned_alloc? Sorry, this sounds like I'm right back to my first question, but Paul's response seemed to indicate that the required alignment is guaranteed, and you now seem to say it isn't. I'm probably missing something. Thanks.