From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11369 invoked by alias); 17 Mar 2012 10:22:47 -0000 Received: (qmail 11355 invoked by uid 22791); 17 Mar 2012 10:22:46 -0000 X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL,TW_NW,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from granite2.mail.cornell.edu (HELO authusersmtp.mail.cornell.edu) (128.253.83.142) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 17 Mar 2012 10:22:33 +0000 Received: from [192.168.1.3] (cpe-67-249-194-47.twcny.res.rr.com [67.249.194.47]) (authenticated bits=0) by authusersmtp.mail.cornell.edu (8.14.4/8.12.10) with ESMTP id q2HAMV83026605 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sat, 17 Mar 2012 06:22:32 -0400 (EDT) Message-ID: <4F6465E2.3040707@cornell.edu> Date: Sat, 17 Mar 2012 10:22:00 -0000 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Status of large address awareness? References: <4F63E5A7.5050806@cs.utoronto.ca> In-Reply-To: <4F63E5A7.5050806@cs.utoronto.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-CORNELL-SPAM-CHECKED: Pawpaw X-Original-Sender: kbrown@cornell.edu - Sat Mar 17 06:22:32 2012 X-PMX-CORNELL-REASON: CU_White_List_Override X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-03/txt/msg00502.txt.bz2 On 3/16/2012 9:15 PM, Ryan Johnson wrote: > Hi all, > > What's the current status of large address awareness for cygwin > binaries? I know at one point it seemed to be working well -- other than > an issue with emacs (fixed now?) -- and there was talk of making it the The emacs problem was fixed last August, as of the release of emacs-23.3-3. > default. However, this does not seem to be the case yet, based on > looking at peflags for a couple of binaries. It's the default for anything built with Cygwin's current gcc: $ gcc -dumpspecs | grep large-address-aware %{mwindows:--subsystem windows} %{mconsole:--subsystem console} %{!mno-cygwin:%{!mno-use-libstdc-wrappers: --wrap _Znwj --wrap _Znaj --wrap _ZdlPv --wrap _ZdaPv --wrap _ZnwjRKSt9nothrow_t --wrap _ZnajRKSt9nothrow_t --wrap _ZdlPvRKSt9nothrow_t --wrap _ZdaPvRKSt9nothrow_t }} %{shared: %{mdll: %eshared and mdll are not compatible}} %{shared: --shared} %{mdll:--dll} %{static:-Bstatic} %{!static:-Bdynamic} %{shared|mdll: --enable-auto-image-base -e %{mno-cygwin:_DllMainCRTStartup@12} %{!mno-cygwin:__cygwin_dll_entry@12}} %{!mno-cygwin:--dll-search-prefix=cyg %{!shared: %{!mdll: --large-address-aware --tsaware}}} Binaries built with earlier releases of gcc aren't changed. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple