Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> > Ah, that is clear: there is no interface definition for plctime. So
> the compiler was using the traditional F77 rules and could not check the
> correctness
> of the types. I will fix this.
>
>
On 2015-05-15 10:19- Arjen Markus wrote:
> Hi Alan, Hazen,
>
>
>> From: Arjen Markus [mailto:arjen.mar...@deltares.nl]
>> Sent: Friday, May 15, 2015 12:15 PM
>> To: Alan W. Irwin; Hazen Babcock
>> Cc: PLplot development list
>> Subject: Re: [Plplot-dev
Hi Alan, Hazen,
> From: Arjen Markus [mailto:arjen.mar...@deltares.nl]
> Sent: Friday, May 15, 2015 12:15 PM
> To: Alan W. Irwin; Hazen Babcock
> Cc: PLplot development list
> Subject: Re: [Plplot-devel] floating point exception in example 29
>
> Hi Alan, Hazen,
>
>
Hi Alan, Hazen,
-Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> Sent: Thursday, May 14, 2015 2:19 AM
>
> Hi Hazen:
>
> It turned out to be a fortran argument issue in Fortran example 29, where 0.
> had to
> be replaced by 0._plflt (see commit id=a0e51cd).
On 2015-05-13 15:18-0700 Alan W. Irwin wrote:
> On 2015-05-13 17:01-0400 Hazen Babcock wrote:
>
>> On 05/13/2015 03:58 PM, Alan W. Irwin wrote:
>>> In my case the only fortran compiler available is gfortran so I don't
>>> need to choose that. So instead of the above I set
>>>
>>> export FFLAGS='-
On 2015-05-13 17:01-0400 Hazen Babcock wrote:
> On 05/13/2015 03:58 PM, Alan W. Irwin wrote:
>> In my case the only fortran compiler available is gfortran so I don't
>> need to choose that. So instead of the above I set
>>
>> export FFLAGS='-g -ffpe-trap=invalid,zero,overflow,underflow'
>>
>> b
On Wed, May 13, 2015 at 5:01 PM, Hazen Babcock wrote:
> On 05/13/2015 03:58 PM, Alan W. Irwin wrote:
> > In my case the only fortran compiler available is gfortran so I don't
> > need to choose that. So instead of the above I set
> >
> > export FFLAGS='-g -ffpe-trap=invalid,zero,overflow,underfl
On 05/13/2015 03:58 PM, Alan W. Irwin wrote:
> In my case the only fortran compiler available is gfortran so I don't
> need to choose that. So instead of the above I set
>
> export FFLAGS='-g -ffpe-trap=invalid,zero,overflow,underflow'
>
> before calling cmake and building the x29f95 and ps target
On 2015-05-13 11:29-0400 Hazen Babcock wrote:
> On 05/12/2015 01:22 PM, Alan W. Irwin wrote:
>> [...]Of course, the fortran examples go through a lot of additional code
>> before finally calling our core C library so this method should detect
>> floating-point exceptions in the fortran example imp
On 05/12/2015 01:22 PM, Alan W. Irwin wrote:
> On 2015-05-12 09:41-0400 Hazen Babcock wrote:
>>
>> Hm.. example 21 also generates an FPE, but at least in this case it
>> looks like it is coming from the qhull library. And example 29 also
>> generates an FPE, but only the Fortran version not the C v
On 2015-05-12 09:41-0400 Hazen Babcock wrote:
>>
>> On 05/11/2015 06:05 PM, Alan W. Irwin wrote:
>>>
>>> Hi Hazen:
>>>
>>> I am glad to hear you have created a topic branch that catches
>>> floating point exceptions. However, I am not keen on pulling a PLplot
>>> topic branch from github for the
>
> On 05/11/2015 06:05 PM, Alan W. Irwin wrote:
>>
>> Hi Hazen:
>>
>> I am glad to hear you have created a topic branch that catches
>> floating point exceptions. However, I am not keen on pulling a PLplot
>> topic branch from github for the reasons discussed in
>> README.developers. So could yo
On 05/11/2015 06:05 PM, Alan W. Irwin wrote:
On 2015-05-11 16:23-0400 Hazen Babcock wrote:
Much time passes during which I never implement this branch as
promised, and it looks like some more floating point exceptions have
crept in. More specifically I'm seeing floating point exceptions in
x25,
On 2015-05-11 16:23-0400 Hazen Babcock wrote:
> On 04/15/2014 07:44 AM, Hazen Babcock wrote:
>> On 4/7/2014 11:08 PM, Alan W. Irwin wrote:
>>> I have just had a further idea. For comprehensive testing situations
>>> it might be good to have the option to call feenableexcept (the C
>>> library func
On 04/15/2014 07:44 AM, Hazen Babcock wrote:
> On 4/7/2014 11:08 PM, Alan W. Irwin wrote:
>> I have just had a further idea. For comprehensive testing situations
>> it might be good to have the option to call feenableexcept (the C
>> library function that you used to help debug x29c.c that should b
On 4/7/2014 11:08 PM, Alan W. Irwin wrote:
> I have just had a further idea. For comprehensive testing situations
> it might be good to have the option to call feenableexcept (the C
> library function that you used to help debug x29c.c that should be
> available for c99 according to its Linux man p
Hi Hazen:
I have just had a further idea. For comprehensive testing situations
it might be good to have the option to call feenableexcept (the C
library function that you used to help debug x29c.c that should be
available for c99 according to its Linux man page) from within the
PLplot library (say
On 2014-04-07 12:00-0700 Alan W. Irwin wrote:
> [...]I will take a look.
The GNU debugger (gdb) made this a really easy issue to solve. It
turned out the issue was an integer overflow in an unused (in the
plbox case) calculation of physical coordinates corresponding to the
default 0., 0., world c
On 2014-04-07 14:30-0400 Hazen Babcock wrote:
> On 4/6/2014 10:16 PM, Alan W. Irwin wrote:
>> On 2014-04-06 17:35-0400 Hazen Babcock wrote:
>>> In the process of converting some of the PLplot demos to Lisp as part of
>>> the cl-plplot project I found that example 29 triggers a floating point
>>> e
On 4/6/2014 10:16 PM, Alan W. Irwin wrote:
> On 2014-04-06 17:35-0400 Hazen Babcock wrote:
>> In the process of converting some of the PLplot demos to Lisp as part of
>> the cl-plplot project I found that example 29 triggers a floating point
>> exception. This is not something that a C compiler wil
On 2014-04-06 17:35-0400 Hazen Babcock wrote:
>
> Hello,
>
> In the process of converting some of the PLplot demos to Lisp as part of
> the cl-plplot project I found that example 29 triggers a floating point
> exception. This is not something that a C compiler will normally report,
> but you can m
Hello,
In the process of converting some of the PLplot demos to Lisp as part of
the cl-plplot project I found that example 29 triggers a floating point
exception. This is not something that a C compiler will normally report,
but you can make it (or at least gcc) more strict about this. I belie
22 matches
Mail list logo
