Re: binary of gcc and gfortran shapshot 20080125 for windows



On Mon, 28 Jan 2008 14:15:28 +0000, post wrote:


"none" <none@xxxxxxxx> wrote in message
news:pan.2008.01.27.18.22.02.342000@xxxxxxxxxxx

Fair enough. I took the snapshot date to be the date of *your*
compilation, not that of the associated gcc snapshot.


Richard Maine:

I know it is you. IP can tell. Take a look at the following, snapshot fated
20080125.

11/23/2007 11:07PM Directory 4.3-20071123
11/30/2007 11:07PM Directory 4.3-20071130
12/07/2007 11:07PM Directory 4.3-20071207
12/14/2007 11:07PM Directory 4.3-20071214
12/21/2007 11:07PM Directory 4.3-20071221
12/28/2007 11:07PM Directory 4.3-20071228
01/04/2008 11:07PM Directory 4.3-20080104
01/11/2008 11:07PM Directory 4.3-20080111
01/18/2008 11:07PM Directory 4.3-20080118
01/25/2008 11:07PM Directory 4.3-20080125

? You think 'none@xxxxxxxx' is Richard Maine? If only! The IP address is
in the UK, and my original reason for wanting some idea of what had
changed was that you were posting weekly, & I didn't know how you
tied in with gcc - you appeared to be making some unspecified
change to work with your parallel programming support, hence I
assumed that you weren't strictly tracking the gcc release dates. Because
you post your updates here I assumed that there was some significant
change - most people providing minor updates rely on 'pull' rather than
'push' to inform people outside the known customer base. (Main gfortran,
for example, seems to wait for a point update, and provides a link to a
'what has changed' page with the announcement. So I know that their
announcements are worth paying attention to. I'd assumed that your company
was of a similar level of gravitas.)

.



Relevant Pages

  • Re: HEADS UP: GCC 3.3.1 import in progress
    ... > I'll be importing a GCC 3.3.1 snapshot in a couple of minutes. ... > Please hold your updates until I post 'all clear' message. ...
    (freebsd-current)
  • HEADS UP: GCC 3.3.1 import in progress
    ... I'll be importing a GCC 3.3.1 snapshot in a couple of minutes. ... Please hold your updates until I post 'all clear' message. ... Alexander Kabaev ...
    (freebsd-current)
  • Re: Silent gcc 4.2.0 loop optimization bug with -O2
    ... gcc 4.2.1 snapshot provided by Kris a week back, compile stuff, and see ... So this doesn't seem to be fixed with Kris' snapshot. ...
    (freebsd-current)
  • Re: [AMD64] X.org build eats all the memory when compiled with GCC 4.2
    ... when compiler uses -O2 ... It's a known bug that isn't going to be fixed until gcc 4.2.1. ... scanpci now compiles in 0.47 seconds and casually glancing at top it appears that memory usage doesn't go over 50 MB. ... This was done on a P4 machine with 2GB RAM synced yesterday and recompiled today with the gcc snapshot. ...
    (freebsd-current)
  • Re: binary of gcc and gfortran shapshot 20080125 for windows
    ... Enjoy free compilers. ... Would you let us know what has changed between each snapshot that you ... as we can then look up on the gcc website. ... there is no reference to the gcc original, ...
    (comp.lang.fortran)