From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Antipov Newsgroups: gmane.emacs.devel Subject: Re: The --with-wide-int build and Lisp_Sub_Char_Table assertion Date: Mon, 12 Jan 2015 21:32:32 +0300 Message-ID: <54B41340.7080605@yandex.ru> References: <83wq4s3qtb.fsf@gnu.org> <54B3FE61.5090908@yandex.ru> <83siff52r8.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1421087582 10224 80.91.229.3 (12 Jan 2015 18:33:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 12 Jan 2015 18:33:02 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 12 19:32:57 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YAjnN-0003IC-5n for ged-emacs-devel@m.gmane.org; Mon, 12 Jan 2015 19:32:57 +0100 Original-Received: from localhost ([::1]:35891 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YAjnM-0004Xj-7n for ged-emacs-devel@m.gmane.org; Mon, 12 Jan 2015 13:32:56 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34484) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YAjnG-0004XV-1Y for emacs-devel@gnu.org; Mon, 12 Jan 2015 13:32:53 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YAjnA-0000Ij-0M for emacs-devel@gnu.org; Mon, 12 Jan 2015 13:32:49 -0500 Original-Received: from forward3l.mail.yandex.net ([84.201.143.136]:47328) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YAjn3-0000GX-FZ; Mon, 12 Jan 2015 13:32:37 -0500 Original-Received: from smtp3h.mail.yandex.net (smtp3h.mail.yandex.net [84.201.186.20]) by forward3l.mail.yandex.net (Yandex) with ESMTP id 28F981500FEC; Mon, 12 Jan 2015 21:32:34 +0300 (MSK) Original-Received: from smtp3h.mail.yandex.net (localhost [127.0.0.1]) by smtp3h.mail.yandex.net (Yandex) with ESMTP id 91BDC1B4666D; Mon, 12 Jan 2015 21:32:33 +0300 (MSK) Original-Received: from unknown (unknown [37.139.80.10]) by smtp3h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id W6172IkUbO-WXxmuK2s; Mon, 12 Jan 2015 21:32:33 +0300 (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1421087553; bh=x2YqaDc+DA4NqjLvki96xF8CrggXbmOrhBZlNyL2agk=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=LAM9xs7bfkbBMkWP/JfKp+J8zXuNQ4G6b/u4HIJxeV3LBB2xn53ksO4mbS5YzK00F sdHDA4aKHM0VnJgq6EvKeBP/kYnzzIFbb9EGiNByULCIspHAXB3HG/6jN14wVskHOU 3UZ+TDVNUKWfhfL9SLzncF4W4wEXO0kvBtAD89hg= Authentication-Results: smtp3h.mail.yandex.net; dkim=pass header.i=@yandex.ru User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 In-Reply-To: <83siff52r8.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] [fuzzy] X-Received-From: 84.201.143.136 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:181188 Archived-At: On 01/12/2015 08:26 PM, Eli Zaretskii wrote: > This is exactly the flaw: the assumption that if the size of 'struct > vectorlike_header' is 4, the offset of the next struct member is also > 4. In reality, a compiler can add padding, and evidently here it did, > probably to get that member aligned an a 8-byte boundary. For MinGW/32, 1) what happens if you use -m[no-]ms-bitfields? (See https://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html, section 6.38.5 i386 Variable Attributes). Or 2) what about using __attribute__((packed))? Stefan doesn't like it for an obvious reasons, but may be just for this particular case... Dmitry