Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-pair-Authenticated: 217.4.27.104 Message-ID: <3D2EBFC2.6973@multimediaware.com> Date: Fri, 12 Jul 2002 13:38:42 +0200 From: Wolfgang Hesseler MIME-Version: 1.0 To: egor duda Subject: Re: Bug: BSS segment in COFF files References: <3D2EA2E2 DOT 2881 AT multimediaware DOT com> <8772121004 DOT 20020712145134 AT logos-m DOT ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > 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. This works, however only if the variables are non-static. If a variable is static the .comm directive is still used. > Not sure if it's all that needed to link gcc-produced object files > with watcom linker, though. For instance, for function 'func ()' gcc > uses _func as symbol name in object files while watcom uses 'func_'. The only problem is that some functions call external functions like _log10. Is the cygwin1.dll source code of that function available? I did a quick search in CVS but couldn't find it. -- 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/