unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: guile-devel <guile-devel@gnu.org>
Subject: unboxing floats in libguile procedures that always return floats?
Date: Wed, 5 Dec 2018 03:11:09 +0000	[thread overview]
Message-ID: <CAJ=RwfZX7AOAnsYqUxF_g_AEXb7+8vqZ3AkCMVuts_8kkwufzw@mail.gmail.com> (raw)

Hello all,

Guile's current floating point unboxing optimizations are great and
have helped me immensely, but they still leave something to be
desired. I often find myself often calling libguile procedures such as
sin, cos, and random:uniform.  These procedures always return floats,
yet Guile always boxes them, leaving me stuck with procedures that
make lots of garbage despite my best efforts to generate efficient
bytecode.  Would it be possible for the compiler to know that it can
safely unbox functions like sin and cos?  It would really help reduce
GC for realtime graphics rendering applications, for example.

Thanks,

- Dave



                 reply	other threads:[~2018-12-05  3:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAJ=RwfZX7AOAnsYqUxF_g_AEXb7+8vqZ3AkCMVuts_8kkwufzw@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=guile-devel@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).