From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 14:10:02 2003 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 AB8AA37B404 for ; Wed, 9 Jul 2003 14:10:02 -0700 (PDT) Received: from h132-197-179-27.gte.com (h132-197-179-27.gte.com [132.197.179.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 745B043FA3 for ; Wed, 9 Jul 2003 14:09:58 -0700 (PDT) (envelope-from ak03@gte.com) Received: from kanpc.gte.com (ak03@localhost [127.0.0.1]) h69L9vTO020768 for ; Wed, 9 Jul 2003 17:09:57 -0400 (EDT) (envelope-from ak03@kanpc.gte.com) Received: (from ak03@localhost) by kanpc.gte.com (8.12.9/8.12.9/Submit) id h69L9vHo020767; Wed, 9 Jul 2003 17:09:57 -0400 (EDT) Date: Wed, 9 Jul 2003 17:09:56 -0400 From: Alexander Kabaev To: current@FreeBSD.ORG Message-Id: <20030709170956.621dc901.ak03@gte.com> Organization: Verizon Data Services X-Mailer: Sylpheed version 0.9.0claws25 (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: The upcoming GCC 3.3+ upgrade 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: Wed, 09 Jul 2003 21:10:03 -0000 Hello everyone, Since GCC 3.2.x branch is closed in FSF repository and no further releases are planned off the 3.2 branch, it was decided that switching to a more recent and actively maintained GCC 3.3+ is necessary. The system compiler upgrade is in 5.2 TODO list. GCC 3.3+ will be a system compiler throughout RELENG_5 lifetime. Unfortunately, importing a newer GCC means that we'll have yet another ABI breakage on our hands. GCC 3.3 is more strict in C++ area and consequently some of the code that used to be OK with 3.2 will no longer compile. All C++ and C programs using old varargs.h interface will have to be changed to use stdarg.h instead. GCC 3.3 issues a lot more warnings and that will affect programs which were previously WARNS-free. I will commit fixes for most of the warnings in src tree when a new compiler will be imported. Exceptions are some contributed sources and the kernel. Warnings in contributed programs should be fixed in upstream sources and kernel warnings will need attention of people who know each respective kernel part better than me. I plan to disable -Werror for kernel for now. Once offending warnings are fixed, -Werror will be switched back on. -- Alexander Kabaev