From owner-freebsd-current@FreeBSD.ORG Fri Jul 30 04:07:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C61816A4CF for ; Fri, 30 Jul 2004 04:07:48 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56D8643D5A; Fri, 30 Jul 2004 04:07:48 +0000 (GMT) (envelope-from kan@FreeBSD.org) Received: from freefall.freebsd.org (kan@localhost [127.0.0.1]) i6U47g01045961; Fri, 30 Jul 2004 04:07:42 GMT (envelope-from kan@freefall.freebsd.org) Received: (from kan@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i6U47fIF045960; Fri, 30 Jul 2004 04:07:41 GMT (envelope-from kan) Date: Fri, 30 Jul 2004 04:07:41 +0000 From: Alexander Kabaev To: Alexey Dokuchaev Message-ID: <20040730040741.GA42165@freefall.freebsd.org> References: <20040727021820.GA46021@freefall.freebsd.org> <20040727102021.GA73927@samodelkin.net> <20040729021919.GA47196@freefall.freebsd.org> <20040730035800.GA21238@regency.nsu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040730035800.GA21238@regency.nsu.ru> User-Agent: Mutt/1.4.1i cc: current@FreeBSD.ORG cc: Max Khon Subject: Re: HEADS-UP: GCC 3.4.2 snapshot import is imminent X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 04:07:48 -0000 On Fri, Jul 30, 2004 at 10:58:00AM +0700, Alexey Dokuchaev wrote: > On Thu, Jul 29, 2004 at 02:19:19AM +0000, Alexander Kabaev wrote: > > On Tue, Jul 27, 2004 at 05:20:21PM +0700, Max Khon wrote: > > > Hi, Alexander! > > > > > > On Tue, Jul 27, 2004 at 02:18:20AM +0000, Alexander Kabaev wrote: > > > > > > > I am going to do an import of GCC 3.4.x snapshot in approximately > > > > 24 hours. At this time I would like to request anyone planning any > > > > sweeping changes in the tree to pospone them until new GCC is in. > > > > The snapshot will be followed by GCC 3.4.2 release when it is available. > > > > > > Do you plan to enable HANDLE_PRAGMA_PACK_PUSH_POP feature? > > > > > > /fjoe > > Is was too late in the game for me to enable it in this snapshot. I will > > consider doing that in the next GCC update. I do not recall anyone ever > > mentioning this feature to me before, let alone aking me to enable it. > > Actually, I did, in private mails to both you and obrien@ few days ago. July 27th, to be exact. % gcc --version gcc (GCC) 3.4.2 [FreeBSD] 20040728 One day before import is what I call 'too late in the game'. > I encountered this problem when porting CPP code to FreeBSD recently. > #pragma pack (push/pop) feature is enabled with some major Linux > distributed gcc (Fedora Core is one of them), which increases chances > that we'd have to do something about it, since people tend to write > software, test it under MSVC and Fedora's gcc, see it works there, and > release it. Current solution of converting #pragma pack (push/pop) to > mere pack(n)/pack() could lead to potential problems (read: bugs) and > just isn't The Right Thing(tm). > > Since you asked, I also hope you (or someone else) will upgrade manual > page for gcc, since it's really outdated for -CURRENT at this moment. > If memory serves me right, all necessary patches are in existence, and > probably were submitted to our GCC maintainers already. Necessary patches, submitted to GCC maintainers are pretty much worthless. Let me repeat - new GCC man pages are automatically generated and applying patches to that is something I would never do. Whoever touches them automatically becomes new GCC documentation maintainer. You have been warned. -- Alexander Kabaev