From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263768AbTLOSQe (ORCPT ); Mon, 15 Dec 2003 13:16:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263806AbTLOSQe (ORCPT ); Mon, 15 Dec 2003 13:16:34 -0500 Received: from louise.pinerecords.com ([213.168.176.16]:27560 "EHLO louise.pinerecords.com") by vger.kernel.org with ESMTP id S263768AbTLOSQd (ORCPT ); Mon, 15 Dec 2003 13:16:33 -0500 Date: Mon, 15 Dec 2003 19:15:43 +0100 From: Tomas Szepe To: "Richard B. Johnson" Cc: Vladimir Kondratiev , "Kevin P. Fleming" , Mark Hahn , Linux Kernel Mailing List , Martin Mares Subject: Re: PCI Express support for 2.4 kernel Message-ID: <20031215181543.GB11260@louise.pinerecords.com> References: <3FDDD8C6.3080804@intel.com> <3FDDDC68.80209@backtobasicsmgmt.com> <3FDDE39E.1050300@intel.com> <20031215170843.GA10857@louise.pinerecords.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Dec-15 2003, Mon, 13:03 -0500 Richard B. Johnson wrote: > Therefore you make data exist in the .data segment by initializing > it. If GCC decides to put this initialized data in the .bss segment, > then it is broken. FYI, it doesn't. Richard, stop denying reality, go check out what gcc 3.3.2 does. -- Tomas Szepe