Date: Mon, 19 Aug 2002 15:37:06 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: Alexander Kabaev <ak03@gte.com>, Scott_Long@adaptec.com, jesse_gross@yahoo.com, current@freebsd.org Subject: Re: GCC 3.2 Message-ID: <20020819223706.GA13032@dragon.nuxi.com> In-Reply-To: <3D614F67.769B9560@mindspring.com> References: <2C7CBDC6EA58D6119E4A00065B3A24CB046493@btcexc01.btc.adaptec.com> <20020815152703.2f0f23e1.ak03@gte.com> <3D5C21C3.7A848926@mindspring.com> <20020815180723.00a5a83d.ak03@gte.com> <3D5C2F93.BE3BE8B0@mindspring.com> <20020819171325.GA29577@dragon.nuxi.com> <3D614F67.769B9560@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 19, 2002 at 01:04:55PM -0700, Terry Lambert wrote: > > Blah Terry, TOTALLY 110% INCORRECT. The situation was the same as our > > FreeBSD 3.x users that still post PR's against RELENG_3 and want us to > > fix things. Even where there was complete patches against 2.94.3 > > available; the issue for the GCC people was one of not willing to spend > > the effort to re-test on all platforms. Same reason we don't upgrade > > RELENG_3 to the latest openssl (or any other lib) -- who knows what else > > would break that depended on version that is there now. > > I thought that this was true for the LD, but not true for the > GCC. I think this is a different problem here, since this > was a specific reference to GCC 2.95. It is more true for GCC than anything I maintain(ed) in src/contrib/ > > > The inability to get patches into 2.95 is totally unrelated > > > to the fact that it was an older GCC, and completely related > > > to the fact that the patches were not submitted in accordance > > > with the GCC maintainer's guidelines, > > > > WRONG, WRONG, WRONG, WRONG !!! > > It *was* an older GCC?!? Now I'm confused. We *are* talking > about the a.out shared library support, right? Nope. We are talking about various exception and code generation bugs. ELF format and sjlj method. Very mainstream things for FreeBSD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020819223706.GA13032>