Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <15132.15459.386580.755198@spanky.love.edu> Date: Mon, 4 Jun 2001 20:56:51 -0500 X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: java@gcc.gnu.org Cc: cygwin@cygwin.com Subject: boehm-gc .comm problem X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id VAA18344 Here's a ball of confusion that I'm hoping a reader can help me unwind. I am inclined to blame the cygwin-target binutils gas for this problem. However, I'd like to work-around this for the nonce by not using commons. Questions: Would this be an ABI problem? Am I on the right track in blaming gas? With a cygwin target, linux host, win32 threads, building boehm-gc, allchblk.c, I get stuff like this: .comm _A, 16 # 4 .comm _A, 32 # 24 .comm _A, 16 # 4 which results in stuff like this: /usr/home/alk/tmp/ccZeLBab.s: Assembler messages: /usr/home/alk/tmp/ccZeLBab.s:4478: Error: Length of .comm "_A" is already 16. Not changed to 32. which is inconsistent with this (gas texinfo): .comm symbol , length .comm declares a named common area in the bss section. Normally reserves memory addresses for it during linking, so no partial program defines the location of the symbol. Use .comm to tell that it must be at least length bytes long. will allocate space for each .comm symbol that is at least as long as the longest .comm request in any of the partial programs linked. length is an absolute expression. The target linux version does not emit any .comms. My reasoning is that existing cygwin libs must use .comm in such circumstances, in order to get consistent storage for globals. If anyone can recommend pertinent reading, I would be appreciative.