On Wed, Mar 14, 2012 at 4:42 PM, Bastien ROUCARIES
wrote:
> On Wed, Mar 14, 2012 at 11:22 AM, Michael Goffioul
> wrote:
>> On Wed, Mar 14, 2012 at 9:48 AM, Bruno Haible wrote:
>>> Michael Goffioul wrote:
I encountered a compilation error with MSVC when compiling floor.c in
strict float
On Wed, Mar 14, 2012 at 11:22 AM, Michael Goffioul
wrote:
> On Wed, Mar 14, 2012 at 9:48 AM, Bruno Haible wrote:
>> Michael Goffioul wrote:
>>> I encountered a compilation error with MSVC when compiling floor.c in
>>> strict floating-point mode (-fp:strict).
>>
>> Note that the use of -fp:strict
On Wed, Mar 14, 2012 at 9:48 AM, Bruno Haible wrote:
> Michael Goffioul wrote:
>> I encountered a compilation error with MSVC when compiling floor.c in
>> strict floating-point mode (-fp:strict).
>
> Note that the use of -fp:strict also leads to test failures such as
>
> test-hypot.h:41: assertio
Michael Goffioul wrote:
> I encountered a compilation error with MSVC when compiling floor.c in
> strict floating-point mode (-fp:strict).
Note that the use of -fp:strict also leads to test failures such as
test-hypot.h:41: assertion failed
FAIL: test-hypotl.exe
MSVC appears to compile the t
Michael Goffioul wrote:
> Same problem occurs in cbrt.c and cbrtf.c.
Fixed. No other occurrences of this problem found so far.
2012-03-13 Bruno Haible
Avoid compilation errors with MSVC option -fp:strict.
* lib/cbrt.c: Use MSVC specific pragma fenv_access.
* lib/cbrtf
On Sun, Mar 11, 2012 at 4:16 PM, Bruno Haible wrote:
> Michael Goffioul wrote:
>> Same problem occurs in cbrt.c and cbrtf.c.
>
> ... and probably some others of newly added math function source files.
> This is an area with work in progress. Can you remind me about this issue
> once I'm done with
Michael Goffioul wrote:
> Same problem occurs in cbrt.c and cbrtf.c.
... and probably some others of newly added math function source files.
This is an area with work in progress. Can you remind me about this issue
once I'm done with the math functions, please?
Thanks.
Bruno
On Tue, Feb 28, 2012 at 10:52 AM, Bruno Haible wrote:
> Michael Goffioul wrote:
>> With the #pragma statement, the compilation error disappears, thanks.
>
> Thanks for verifying that we were on the right track.
>
>> I think the same
>> problem will appear in round.c and trunc.c (those are also use
Michael Goffioul wrote:
> With the #pragma statement, the compilation error disappears, thanks.
Thanks for verifying that we were on the right track.
> I think the same
> problem will appear in round.c and trunc.c (those are also used by
> octave).
Yes, and there are a few more. I'm applying thi
On Thu, Feb 23, 2012 at 10:12 AM, Bruno Haible wrote:
> Michael Goffioul wrote:
>> I encountered a compilation error with MSVC when compiling floor.c in
>> strict floating-point mode (-fp:strict). The error is:
>>
>> "error C2099: initializer is not a constant"
>>
>> The error is triggered by the
Michael Goffioul wrote:
> I encountered a compilation error with MSVC when compiling floor.c in
> strict floating-point mode (-fp:strict). The error is:
>
> "error C2099: initializer is not a constant"
>
> The error is triggered by the initializer for the constant variable
> TWO_MANT_DIG and is d
Hi,
I encountered a compilation error with MSVC when compiling floor.c in
strict floating-point mode (-fp:strict). The error is:
"error C2099: initializer is not a constant"
The error is triggered by the initializer for the constant variable
TWO_MANT_DIG and is documented here:
http://msdn.micr
12 matches
Mail list logo
