Skip to content

how to force the use of fast floating point support? #108

@joudinet

Description

@joudinet

Cross-compiling using the buildroot project, I found out that this project enables SPANDSP_USE_FIXED_POINT because the AX_FIXED_POINT_MACHINE rule believes my arm machine lacks fast hardware floating point, which is wrong.
I found out this issue due to another issue in v17rx.c, already reported in #18
According to #53 this was already broken and I believe the fix of this issue that defines the macro SPANDSP_USE_FIXED_POINTx in v17rx.c is wrong, which causes #18, but this is not my issue.

I would like to force the use of floating point, because I know my arm machine does support fast hardware floating point. Unfortunately, the configure does not offer this option. If I try --disable-fixed-point, it goes to the else part, which actually enable fixed point for any arm machines :-/

 if test "$enable_fixed_point" = "yes" ; then
    AC_DEFINE([SPANDSP_USE_FIXED_POINT], [1], [Enable fixed point processing, where possible, instead of floating point])
    SPANDSP_USE_FIXED_POINT="#define SPANDSP_USE_FIXED_POINT 1"
else
    AX_FIXED_POINT_MACHINE([$host],
        [AC_DEFINE([SPANDSP_USE_FIXED_POINT], [1], [Enable fixed point processing, where possible, instead of floating point])
        SPANDSP_USE_FIXED_POINT="#define SPANDSP_USE_FIXED_POINT 1"],
        [SPANDSP_USE_FIXED_POINT="#undef SPANDSP_USE_FIXED_POINT"])
fi

Would you agree to fix this test so if one asks for --disable-fixed-point, it does not enable it, or do you prefer to completely remove the fixed_point support, which seems broken at the moment anyway.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions