Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 29 Mar 2001 17:56:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 29 Mar 2001 17:56:27 -0500 Received: from smtp.mountain.net ([198.77.1.35]:21515 "EHLO riker.mountain.net") by vger.kernel.org with ESMTP id ; Thu, 29 Mar 2001 17:56:19 -0500 Message-ID: <3AC3BD64.7702CD7B@mountain.net> Date: Thu, 29 Mar 2001 17:55:32 -0500 From: Tom Leete X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.4.2 i486) X-Accept-Language: en-US,en-GB,en,fr,es,it,de,ru MIME-Version: 1.0 To: Ulrich Drepper CC: dank@trellisinc.com, linux-kernel@vger.kernel.org, Eli Carter Subject: Re: [PATCH] pcnet32 compilation fix for 2.4.3pre6 In-Reply-To: <20010329210925.3161C6E099@fancypants.trellisinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Ulrich Drepper wrote: > > dank@trellisinc.com writes: > > > with the new ansi standard, this use of __inline__ is no longer > > necessary, > > This is not correct. Since the semantics of inline in C99 and gcc > differ all code which depends on the gcc semantics should continue to > use __inline__ since this keyword will hopefully forever signal the > gcc semantics. Unfortunately, it seems that gcc will define __inline__ as a synonym for inline, whatever inline is currently in use. I asked this on the gcc list a while ago. The archive there should have the replies. Regards, Tom -- The Daemons lurk and are dumb. -- Emerson - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/