From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.emacs.devel Subject: Re: Dumper problems and a possible solutions Date: Wed, 25 Jun 2014 19:21:40 -0400 Message-ID: <20140625232140.GG179@brightrain.aerifal.cx> References: <53AB0EF8.4090608@yandex.ru> <831tucrguf.fsf@gnu.org> <20140625183241.GW179@brightrain.aerifal.cx> <83wqc4q0xl.fsf@gnu.org> <20140625190333.GZ179@brightrain.aerifal.cx> <20140625202403.GB179@brightrain.aerifal.cx> <20140625220758.GE179@brightrain.aerifal.cx> <53AB557A.30104@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1403738542 4935 80.91.229.3 (25 Jun 2014 23:22:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 25 Jun 2014 23:22:22 +0000 (UTC) Cc: emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 26 01:22:11 2014 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 1WzwW2-0005CD-B6 for ged-emacs-devel@m.gmane.org; Thu, 26 Jun 2014 01:22:10 +0200 Original-Received: from localhost ([::1]:41522 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WzwW1-0006Pi-T5 for ged-emacs-devel@m.gmane.org; Wed, 25 Jun 2014 19:22:09 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35974) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WzwVt-0006OE-KD for emacs-devel@gnu.org; Wed, 25 Jun 2014 19:22:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WzwVm-0002ux-Bs for emacs-devel@gnu.org; Wed, 25 Jun 2014 19:22:01 -0400 Original-Received: from 216-12-86-13.cv.mvl.ntelos.net ([216.12.86.13]:44454 helo=brightrain.aerifal.cx) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WzwVl-0002tg-Vd for emacs-devel@gnu.org; Wed, 25 Jun 2014 19:21:54 -0400 Original-Received: from dalias by brightrain.aerifal.cx with local (Exim 3.15 #2) id 1WzwVY-0005Sy-00; Wed, 25 Jun 2014 23:21:40 +0000 Content-Disposition: inline In-Reply-To: <53AB557A.30104@cs.ucla.edu> User-Agent: Mutt/1.5.21 (2010-09-15) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 216.12.86.13 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:172737 Archived-At: On Wed, Jun 25, 2014 at 04:04:26PM -0700, Paul Eggert wrote: > Rich Felker wrote: > >this model is also incompatible > >with PIE and with most modern systems where malloc may return "high" > >addresses, and thereby likely buggy even on the systems it's currently > >used on (if any). > > The model works just fine on a typical modern 32-bit host, so long > as you configure --with-wide-int. That's because the 32-bit > addresses fit comfortably in the low half of 64-bit integers. I see. I wasn't aware of that option. In any case it would work just fine with the proposed C static array output: for 32-bit pointers, the lower 32 bits would actually be the address constant reference and the upper 32 bits would be an integer constant expression. Rich