From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: `SCM_MAKE_CHAR ()' signedness issue
Date: Mon, 17 Aug 2009 17:33:03 +0200 [thread overview]
Message-ID: <873a7qpia8.fsf@gnu.org> (raw)
In-Reply-To: 1250514351.18373.33.camel@localhost.localdomain
Mike Gran <spk121@yahoo.com> writes:
> On my system I ran a test with SCM_MAKE_CHAR as a macro, an an inline,
> and as a never inlined function. I ran ./check-guile twice for each.
You're cheating! ;-)
The test suite does lots of things besides calling `SCM_MAKE_CHAR ()',
so I'm not sure if it's a good benchmark.
I'm fairly confident that for such a small piece of code inlining is
always a good idea.
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-08-17 15:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 12:00 `SCM_MAKE_CHAR ()' signedness issue Ludovic Courtès
2009-08-16 21:58 ` Ken Raeburn
2009-08-16 22:13 ` Ludovic Courtès
2009-08-16 22:25 ` Ken Raeburn
2009-08-17 8:26 ` Ludovic Courtès
2009-08-17 13:05 ` Mike Gran
2009-08-17 15:33 ` Ludovic Courtès [this message]
2009-08-18 17:32 ` Mike Gran
-- strict thread matches above, loose matches on Subject: below --
2009-08-17 18:52 carlo.bramix
2009-08-17 19:41 ` Ken Raeburn
2009-08-18 18:39 carlo.bramix
2009-08-18 18:54 ` Mike Gran
2009-08-18 23:36 ` Greg Troxel
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=873a7qpia8.fsf@gnu.org \
--to=ludo@gnu.org \
--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).