This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: -frecord-marker
- From: Bud Davis <bdavis9659 at sbcglobal dot net>
- To: Janne Blomqvist <Janne dot Blomqvist at tkk dot fi>, Adrian Umpleby <apumpleby at yahoo dot co dot uk>
- Cc: fortran at gcc dot gnu dot org
- Date: Fri, 21 Jul 2006 04:45:07 -0700 (PDT)
- Subject: Re: -frecord-marker
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=WHHuXNrsINsjfUdeCjBv3yFdjtXQXfVPr6R9KuW89rWpr2YuYGWFYCHULWmQkj601pOt6yD7yuLqJ+bWLipBtlmmBUbn9tJp6lf6FZD6HBhRQ8R8YiFExn8Yk0MInSRjl0Mnjh53CEm6cLa7oT7icvL23hALK3DIlpOaUyi3czw= ;
just a couple of comments to add to the noise on this
topic:
>
> AFAICS it's not necessary to know the size of the
> record before
> writing it with the Intel scheme. When running out
> of space in one
> subrecord, just seek back and fix the first record
> marker, seek
> forwards and start the next one. Just like gfortran
> does it today. It
> does cause some extra seeking, but changing that is
> unfortunately
> rather complicated.
>
on some file systems those seeks will be slow. very
slow. and of course they will be worse the bigger the
records :)
but, everything is a tradeoff...the world would be
grand if we knew how big the record was going to be on
the first library call.
--bud