From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 13 09:46:29 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C70B37B401; Sun, 13 Apr 2003 09:46:29 -0700 (PDT) Received: from pop018.verizon.net (pop018pub.verizon.net [206.46.170.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66FF743FD7; Sun, 13 Apr 2003 09:46:28 -0700 (PDT) (envelope-from kabaev@bellatlantic.net) Received: from kanhome ([151.203.222.111]) by pop018.verizon.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP id <20030413164627.FFJO1699.pop018.verizon.net@kanhome>; Sun, 13 Apr 2003 11:46:27 -0500 Date: Sun, 13 Apr 2003 12:46:26 -0400 From: Alexander Kabaev To: hackers@freebsd.org Message-Id: <20030413124626.5e782421.kabaev@bellatlantic.net> In-Reply-To: <20030413012636.GA76030@dragon.nuxi.com> References: <5.2.0.9.2.20030411082040.02604e90@194.184.65.4> <200304120241.h3C2fQCc061882@latour.rsch.comm.mot.com> <20030413012636.GA76030@dragon.nuxi.com> X-Mailer: Sylpheed version 0.8.10claws18 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at pop018.verizon.net from [151.203.222.111] at Sun, 13 Apr 2003 11:46:27 -0500 cc: gmarco@giovannelli.it cc: rittle@latour.rsch.comm.mot.com Subject: Re: gcc iussue or ... ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ak03@gte.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Apr 2003 16:46:29 -0000 On Sat, 12 Apr 2003 18:26:36 -0700 "David O'Brien" wrote: > I'm not sure we should change FreeBSD to do something that purposfully > produces wrong semantics. From your test it sounds like either GCC > 3.3 or Binutils 2.13.2.1 changes things for us. I haven't updated > FreeBSD to 2.13.2.1 as the changes from 2.13.2 don't really change any > of the FreeBSD architectures. The behavior change is probably due to > improved g++ utilization of ELF features, or your FreeBSD-related bug > fixes in 3.3. > I think there is a slight confusion here. It is -fconserve-space flag what introduces wrong semantics, not the addition of missing definition. -fconserve-space marks all uninitialized static variables as 'common' which can obviously lead to unwanted namespace collisions. -- Alexander Kabaev