Date: Sun, 13 Apr 2003 12:46:26 -0400 From: Alexander Kabaev <kabaev@bellatlantic.net> To: hackers@freebsd.org Cc: rittle@latour.rsch.comm.mot.com Subject: Re: gcc iussue or ... ? 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 12 Apr 2003 18:26:36 -0700 "David O'Brien" <obrien@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030413124626.5e782421.kabaev>