From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31122 invoked by alias); 12 Jul 2002 12:06:33 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 31113 invoked from network); 12 Jul 2002 12:06:32 -0000 Received: from unknown (HELO relay.pair.com) (209.68.1.20) by sources.redhat.com with SMTP; 12 Jul 2002 12:06:32 -0000 Received: (qmail 24293 invoked from network); 12 Jul 2002 12:06:30 -0000 Received: from pd9041b15.dip.t-dialin.net (HELO pii) (217.4.27.21) by relay1.pair.com with SMTP; 12 Jul 2002 12:06:30 -0000 X-pair-Authenticated: 217.4.27.21 Message-ID: <3D2EC616.19DA@multimediaware.com> Date: Fri, 12 Jul 2002 07:05:00 -0000 From: Wolfgang Hesseler MIME-Version: 1.0 To: egor duda Subject: Re: Bug: BSS segment in COFF files References: <3D2EA2E2.2881@multimediaware.com> <8772121004.20020712145134@logos-m.ru> <3D2EBFC2.6973@multimediaware.com> <9975891676.20020712155424@logos-m.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-07/txt/msg01032.txt.bz2 > >> If you run gcc with '--save-temps' flag, and then look into > >> 'yourfile.s' file, you'll see that uninitialized data is tagged as > >> "common" (using '.comm' directive) and is put to bss only by linker > >> when final executable is created. To turn this feature off, use > >> '-fno-common' flag when compiling your object file. > > WH> This works, however only if the variables are non-static. If a > WH> variable is static the .comm directive is still used. > > .lcomm, to be precise. > > That's easy to work around. Just add 'int dummy;' to your source > file compiled with gcc, and you have 4 bytes in bss section. But how does this help? The other static variables still use the .lcomm directive. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/