From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14188 invoked by alias); 5 Jun 2008 05:43:33 -0000 Received: (qmail 14176 invoked by uid 22791); 5 Jun 2008 05:43:32 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 05 Jun 2008 05:43:13 +0000 Received: from zps38.corp.google.com (zps38.corp.google.com [172.25.146.38]) by smtp-out.google.com with ESMTP id m555gx6J024574; Thu, 5 Jun 2008 06:43:00 +0100 Received: from smtp.corp.google.com (spacemonkey2.corp.google.com [192.168.120.114]) by zps38.corp.google.com with ESMTP id m555gxRJ006014 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 4 Jun 2008 22:42:59 -0700 Received: from localhost.localdomain.google.com (adsl-71-133-8-30.dsl.pltn13.pacbell.net [71.133.8.30]) (authenticated bits=0) by smtp.corp.google.com (8.13.8/8.13.8) with ESMTP id m555dnNS003586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 4 Jun 2008 22:39:49 -0700 To: Devang Patel Cc: Nick Kledzik , GCC Mailing List Subject: Re: [whopr] Design/implementation alternatives for the driver and WPA References: <96A87E23-CD76-41E3-A4BD-DD399C847F17@apple.com> <48F70208-61C2-4D44-9531-E682C74647E6@apple.com> <0695A6FD-42D5-4045-9722-6C060979CEAC@apple.com> From: Ian Lance Taylor Date: Thu, 05 Jun 2008 05:43:00 -0000 In-Reply-To: <0695A6FD-42D5-4045-9722-6C060979CEAC@apple.com> (Devang Patel's message of "Wed\, 4 Jun 2008 22\:07\:20 -0700") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2008-06/txt/msg00099.txt.bz2 [ trimming the CC list ] Devang Patel writes: > If the optimizer can handle the symbol versioning case when one > definition with version is defined in the same source file as the > reference then you don't need new API. > > For example, > > a.o : refers to S and defines S at version V. > b.o : defines S. > > Is inliner, at compile time allowed to inline uses of S in a.o using > the definition it has ? The compiler doesn't know about symbol versions. The way they work is that you give the symbol a name like S_V, and then use an assembly level .symver directive to say that S_V is really S at version V. So false inlining doesn't really arise in a single source file, unless you do something rather odd. Ian