GNU bug report logs - #14047
more aggressive inlining

Previous Next

Full log

Message #8 received at 14047 <at> debbugs.gnu.org (full text, mbox):

From: Andy Wingo <wingo <at> pobox.com>
To: Daniel Llorens <daniel.llorens <at> bluewin.ch>
Cc: 14047 <at> debbugs.gnu.org
Subject: Re: bug#14047: more aggressive inlining
Date: Wed, 27 Mar 2013 20:31:22 +0100

On Mon 25 Mar 2013 10:42, Daniel Llorens <daniel.llorens <at> bluewin.ch> writes:

>> On Fri 01 Mar 2013 10:01, Daniel Llorens <daniel.llorens <at> bluewin.ch> writes:
>> 
>>> scheme@(guile-user)> ,optimize (vector-ref #(1 2 3) 0)
>>> $1 = 1
>>> scheme@(guile-user)> ,optimize (array-ref #(1 2 3) 0)
>>> $2 = (array-ref '#(1 2 3) 0)
>> 
>> File a bug for this case, this sort of thing is totally fixable :)
>
> So I think this use of array-ref should be inlined.
>
> Same for other simple functions such as e.g.
>
> scheme@(guile-user)> ,optimize (real-part 1+1i)
> $1 = (real-part 1.0+1.0i)
> scheme@(guile-user)> 
>
> imag-part, magnitude, and so on.

If you would like to make a precise list, that would be helpful.

Cheers,

A
-- 
http://wingolog.org/

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.