From: Barry Fishman <barry_fishman@acm.org>
To: guile-devel@gnu.org
Subject: Unexpected srfi-4 C Interface Change in 2.0.10
Date: Wed, 19 Mar 2014 10:22:40 -0400 [thread overview]
Message-ID: <m37g7qxo7j.fsf@barry_fishman.acm.org> (raw)
When building C interface code using scm_f32vector_writable_elements()
in 2.0.10 and on the trunk I found:
For a vector generated in guile with:
(f32vector 0.25 0.25 0.25 1.0)
I found in the C interface:
scm_t_array_handle handle;
size_t vlen, vinc;
float *arrayp;
arrayp = scm_f32vector_writable_elements(s_uvec, &handle,
&vlen, &vinc)
When I test vlen it now seems to contain the number of bytes (16)
rather than the number of elements (4) in the f32vector.
It was 4 in 2.0.9 and the guile trunk I built on Jan 8.
It was 16 in 2.0.10 and the guile trunk I built on March 17.
I assume it relates to the Feb 8 changes, where:
(in commit dc65b88d839c326889618112c4870ad3a64e9446)
*lenp = scm_c_bytevector_length (uvec) / width;
and width is set to 1 in the macro:
DEFINE_SRFI_4_C_FUNCS (F32, f32, float, 1);
--
Barry Fishman
next reply other threads:[~2014-03-19 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 14:22 Barry Fishman [this message]
[not found] <mailman.201.1395244856.16207.guile-devel@gnu.org>
2014-03-19 17:04 ` Unexpected srfi-4 C Interface Change in 2.0.10 Daniel Llorens
2014-03-19 18:12 ` Mark H Weaver
2014-03-19 21:43 ` Andy Wingo
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=m37g7qxo7j.fsf@barry_fishman.acm.org \
--to=barry_fishman@acm.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).