[Numpy-discussion] Solaris Sparc build broken

Charles R Harris charlesr.harris@gmail....
Fri Nov 6 00:44:36 CST 2009


On Thu, Nov 5, 2009 at 10:35 PM, David Cournapeau <
david@ar.media.kyoto-u.ac.jp> wrote:

> Charles R Harris wrote:
> > So you are going to leave us all hanging here in curiosity? What is
> > your solution?
>
> I had to sleep :)
>
> The solution is based on parsing the generated binary code - that's how
> MPFR is doing it, so it has been tested in the wild. The code to compile
> is something like:
>
> /* "before" is 16 bytes to ensure there's no padding between it and "x".
>  *    We're not expecting any "long double" bigger than 16 bytes or with
>  *       alignment requirements stricter than 16 bytes.  */
> typedef long double test_type;
>
> struct {
>        char         before[16];
>        test_type    x;
>        char         after[8];
> } foo = {
>        { '\0', '\0', '\0', '\0', '\0', '\0', '\0', '\0',
>          '\001', '\043', '\105', '\147', '\211', '\253', '\315', '\357' },
>        -123456789.0,
>        { '\376', '\334', '\272', '\230', '\166', '\124', '\062', '\020' }
> };
>
> They compile it, parse with awk from the dump od -f.
>

So the before/after bits are tags that mark the beginning/end of the type
for the parse? Any particular reason not to use a string? "David Cournapeau"
should work :-)

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20091105/c988cbb5/attachment.html 


More information about the NumPy-Discussion mailing list