Please, read this small thread discussion:
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/413#note_518001
Hope GCC help Linux users.
Hi,
Le samedi 25 mai 2019 à 14:44 +0545, Prabesh bhattarai a écrit :
> Please, read this small thread discussion:
>
> https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/413#note_518001
>
> Hope GCC help Linux users.
In this comment, g-c-c is for GNOME Control Center. It's not related t
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
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
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,
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
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
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
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
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
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
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,
Snapshot gcc-9-20190525 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/9-20190525/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 9 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-9
13 matches
Mail list logo
