[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] reachable top-level functions and variables
From: |
Sven Hartrumpf |
Subject: |
Re: [Chicken-users] reachable top-level functions and variables |
Date: |
Thu, 13 Jul 2017 09:19:55 +0200 (CEST) |
Hi Peter.
Peter Bex <address@hidden> schrieb am 2017-07-13 09:05:
> On Thu, Jul 13, 2017 at 08:52:31AM +0200, Sven Hartrumpf wrote:
>> Yes, functions that can never be called from the compiled program
>> are still there.
>> Will the profile output of the compiled program (-accumulate-profile)
>> be a reliable filter if I avoid inlining and make
>> sure that all possible input cases are seen by the program?
>
> Are you looking for a coverage/dead code elimination tool?
Exactly.
I have some compile time numbers (from bigloo) where I was able to
reduce compile time from 20 minutes to 4 minutes
by using dead code elimination as a preprocessing step.
Unfortunately, the analysis became too inaccurate over time
(I assume because the complexity in the user program source increased).
So, I am looking for alternatives.
> Something like that's been on my mind a few times, as a thing
> that would be nice to have.
Ciao
Sven
Re: [Chicken-users] reachable top-level functions and variables, Mario Domenech Goulart, 2017/07/13
Re: [Chicken-users] reachable top-level functions and variables, Marc Feeley, 2017/07/13