From: Daniel Llorens <daniel.llorens@bluewin.ch>
To: 14047@debbugs.gnu.org
Subject: bug#14047: more aggressive inlining
Date: Mon, 25 Mar 2013 10:42:25 +0100 [thread overview]
Message-ID: <18DDEE8E-F660-4D33-82A6-5F51E75A967A@bluewin.ch> (raw)
In-Reply-To: <87k3prlai3.fsf@pobox.com>
On Mar 1, 2013, at 10:44, Andy Wingo wrote:
> On Fri 01 Mar 2013 10:01, Daniel Llorens <daniel.llorens@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.
next prev parent reply other threads:[~2013-03-25 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.153.1351958430.10005.guile-devel@gnu.org>
[not found] ` <0F432FA1-CFF8-4A22-A477-5291A1B9925D@bluewin.ch>
[not found] ` <87ip9mgzp4.fsf@gnu.org>
[not found] ` <878v7m5xdh.fsf@pobox.com>
[not found] ` <2E5FFE0D-9001-409C-BCD4-9EE3BF9883F0@bluewin.ch>
[not found] ` <87mww0nu8l.fsf@pobox.com>
[not found] ` <2D31D517-08F8-4D07-84DB-098E335AE0AD@bluewin.ch>
[not found] ` <874nh9boqe.fsf@pobox.com>
[not found] ` <87txp9nrmc.fsf_-_@tines.lan>
2013-02-19 8:18 ` bug#13757: Problems with Guile's number printer Andy Wingo
2013-03-17 23:47 ` bug#12216: " Mark H Weaver
2013-03-18 1:28 ` Mark H Weaver
2013-03-18 1:29 ` bug#13757: " Mark H Weaver
[not found] ` <96617E9F-D83C-48EE-B84D-7CD45C4181C2@bluewin.ch>
[not found] ` <CA+U71=Pj1Ywr1Ay+w-u1jWd4ZZ8Xk1b27YEg-ME8JRVchYRuCA@mail.gmail.com>
[not found] ` <441E015F-F545-48DF-AF96-E1FEA64F64A3@bluewin.ch>
[not found] ` <CA+U71=MvGqHWqLgF5BOUiVCmimwPChmRwehJ0VQhACEPBDLzTg@mail.gmail.com>
[not found] ` <14C63C7B-DEA6-4C0C-AB18-17695BC5FAD3@bluewin.ch>
[not found] ` <87k3prlai3.fsf@pobox.com>
2013-03-25 9:42 ` Daniel Llorens [this message]
2013-03-27 19:31 ` bug#14047: more aggressive inlining Andy Wingo
2013-03-27 20:40 ` Daniel Llorens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18DDEE8E-F660-4D33-82A6-5F51E75A967A@bluewin.ch \
--to=daniel.llorens@bluewin.ch \
--cc=14047@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).