public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 3.0.3
Date: Sat, 24 Nov 2001 21:15:00 -0000	[thread overview]
Message-ID: <3C08012E.361450B8@moene.indiv.nluug.nl> (raw)
In-Reply-To: <13880000.1007057994@warlock.codesourcery.com>

Mark Mitchell wrote:

> Please remember that Dec 1. is the freeze date for changes going into
> GCC 3.0.3.  Non-documentation changes will require my approval after
> that point.
> 
> I have received some important bug reports from people.  I will be
> posting a list of those shortly.  We will try to fix these before the
> release if possible.

I definitely want to fix fortran/4885.  It's a regression from gcc-2.95
(actually a libf2c problem that's probably introduced by the ftruncate
change requested by the GAMESS developers).

I work on it tomorrow (1st of Dec.).

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)

WARNING: multiple messages have this Message-ID
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 3.0.3
Date: Fri, 30 Nov 2001 23:39:00 -0000	[thread overview]
Message-ID: <3C08012E.361450B8@moene.indiv.nluug.nl> (raw)
Message-ID: <20011130233900.GNlPaoc-JPrr7DEs0OcN0chd1HFrHMSDX64_kfaV01M@z> (raw)
In-Reply-To: <13880000.1007057994@warlock.codesourcery.com>

Mark Mitchell wrote:

> Please remember that Dec 1. is the freeze date for changes going into
> GCC 3.0.3.  Non-documentation changes will require my approval after
> that point.
> 
> I have received some important bug reports from people.  I will be
> posting a list of those shortly.  We will try to fix these before the
> release if possible.

I definitely want to fix fortran/4885.  It's a regression from gcc-2.95
(actually a libf2c problem that's probably introduced by the ftruncate
change requested by the GAMESS developers).

I work on it tomorrow (1st of Dec.).

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)

  parent reply	other threads:[~2001-12-01  7:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 18:24 Mark Mitchell
2001-11-21 22:25 ` Joe Buck
2001-11-21 23:26   ` Mark Mitchell
2001-11-22  0:04     ` Joe Buck
2001-11-22  0:14       ` Mark Mitchell
2001-11-22  2:58         ` Joe Buck
2001-11-22  7:35           ` Mark Mitchell
2001-11-29 17:16             ` Mark Mitchell
2001-11-29 16:15           ` Joe Buck
2001-11-29 14:25         ` Mark Mitchell
2001-11-29 13:51       ` Joe Buck
2001-11-29 12:28     ` Mark Mitchell
2001-11-23 14:47   ` fix for PR 4447: is this really correct? Joe Buck
2001-11-24 20:36     ` Kriang Lerdsuwanakij
2001-11-30 23:02       ` Kriang Lerdsuwanakij
2001-12-01 16:08       ` Joe Buck
2001-12-02  3:12         ` Kriang Lerdsuwanakij
2001-12-03  9:42           ` Mark Mitchell
2001-12-01 17:32       ` Alexandre Oliva
2001-11-30 11:20     ` Joe Buck
2001-11-29 11:51   ` GCC 3.0.3 Joe Buck
2001-11-23 14:48 ` Stephane Carrez
2001-11-23 15:52   ` Jakub Jelinek
2001-11-30 11:47     ` Jakub Jelinek
2001-11-30 11:27   ` Stephane Carrez
2001-12-03  8:34   ` Mark Mitchell
2001-11-24 21:15 ` Toon Moene [this message]
2001-11-30 23:39   ` Toon Moene
2001-11-29 10:24 ` Mark Mitchell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C08012E.361450B8@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).