On 5/26/19 8:11 PM, Thomas Koenig wrote:
> Hi Toon,
>
>> However, there *is* a Segmentation Fault when running one of its tests:
>>
>> cat nf_test/tst_f90.log
>>
>> Program received signal SIGSEGV: Segmentation fault - invalid memory
>> reference.
Thank you very much Toon, the segmentation fault
Hi Toon,
However, there *is* a Segmentation Fault when running one of its tests:
cat nf_test/tst_f90.log
Program received signal SIGSEGV: Segmentation fault - invalid memory
reference.
Thanks! Now I finally have (open) source to work with...
I think I have an idea what's wrong now.
Regar
On 5/25/19 7:43 PM, Toon Moene wrote:
On 5/25/19 7:31 PM, Thomas Koenig wrote:
Hi Toon,
On 5/25/19 7:01 PM, Steve Kargl wrote:
For WRF, I suppose you or Martin could be a good citizen and
contact the project to report a bug.
I have thought about this. As a person with experience building
On 5/25/19 7:31 PM, Thomas Koenig wrote:
Hi Toon,
On 5/25/19 7:01 PM, Steve Kargl wrote:
For WRF, I suppose you or Martin could be a good citizen and
contact the project to report a bug.
I have thought about this. As a person with experience building and
running weather forecasting codes,
Hi Toon,
On 5/25/19 7:01 PM, Steve Kargl wrote:
For WRF, I suppose you or Martin could be a good citizen and
contact the project to report a bug.
I have thought about this. As a person with experience building and
running weather forecasting codes, I would be first in line to try this.
But
Hi Gilles,
Several SPEC benchmarks are available at no cost for non commercial
usage.
See https://www.spec.org/order.html, you may qualify.
I checked, and I do not qualify - I am just a simple volunteer with
a day job which has nothing to do with maintaining gfortran, and
I do draw the line a
On 5/25/19 7:01 PM, Steve Kargl wrote:
For WRF, I suppose you or Martin could be a good citizen and
contact the project to report a bug.
I have thought about this. As a person with experience building and
running weather forecasting codes, I would be first in line to try this.
But the SPEC c
On Sat, May 25, 2019 at 02:52:53PM +0200, Thomas Koenig wrote:
>
> consider this: There is a bug, confirmed by several people. This occurs
> in closed-source, proprietary software, and appears to be due to one
> of my commits.
>
> Despite considerable help from somebody who has access to the sour
Thomas,
Several SPEC benchmarks are available at no cost for non commercial
usage.
See https://www.spec.org/order.html, you may qualify
Cheers,
Gilles
- Original Message -
> Hi,
>
> consider this: There is a bug, confirmed by several people. This
occurs
> in closed-source, proprieta
Am 25.05.19 um 15:16 schrieb Toon Moene:
On 5/25/19 2:52 PM, Thomas Koenig wrote:
Hi,
consider this: There is a bug, confirmed by several people. This occurs
in closed-source, proprietary software, and appears to be due to one
of my commits.
Despite considerable help from somebody who has acc
On May 25, 2019 2:52:53 PM GMT+02:00, Thomas Koenig
wrote:
>Hi,
>
>consider this: There is a bug, confirmed by several people. This occurs
>in closed-source, proprietary software, and appears to be due to one
>of my commits.
>
>Despite considerable help from somebody who has access to the source,
On 5/25/19 2:52 PM, Thomas Koenig wrote:
Hi,
consider this: There is a bug, confirmed by several people. This occurs
in closed-source, proprietary software, and appears to be due to one
of my commits.
Despite considerable help from somebody who has access to the source,
and putting in quite a
Hi,
consider this: There is a bug, confirmed by several people. This occurs
in closed-source, proprietary software, and appears to be due to one
of my commits.
Despite considerable help from somebody who has access to the source,
and putting in quite a few (volunteer) hours myself, there is no
t
13 matches
Mail list logo
