Complete.Org: Mailing Lists: Archives: freeciv-dev: October 2002:
[Freeciv-Dev] Re: Making freeciv faster
Home

[Freeciv-Dev] Re: Making freeciv faster

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: freeciv development list <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: Making freeciv faster
From: Raimar Falke <rf13@xxxxxxxxxxxxxxxxx>
Date: Wed, 30 Oct 2002 12:47:24 +0100

On Tue, Oct 29, 2002 at 09:46:13PM +0100, Raimar Falke wrote:

It turns out that there is a way to know which functions are inlined:
look at the assembly output. The attached tarbal contains 

o2-o3.inline       GCC from -O2 to -O3
intel-ip.inline    INTEL from "" to -ip
ip-ipo.inline      INTEL from -ip to -ipo
intel-ipo.inline   INTEL from "" to -ipo

which describe which functions are inlined. Format:

  -- ai_military_findjob: unit_can_defend, unit_vulnerability_virtual

means that the function ai_military_findjob the functions
unit_can_defend and unit_vulnerability_virtual are inlined (are not
called anymore). There is also a long line:

  zzz__REMOVED__zzz: a_connection_exists, add_buildings_effect, add_clause, 
adjacent_river_tiles4, ...

which lists all functions which are not found in both assembly output
(i.e. removed in the second output).

Only ai/, common/ and server/ were compiled.

        Raimar

-- 
 email: rf13@xxxxxxxxxxxxxxxxx
 "Premature optimization is the root of all evil."
    -- D. E. Knuth in "Structured Programming with go to Statements"

Attachment: inlined-functions.tar.bz2
Description: Text document


[Prev in Thread] Current Thread [Next in Thread]