This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Compressed MOD files?

From: Paul Thomas <paulthomas2 at wanadoo dot fr>
To: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
Cc: Erik Edelmann <edelmann at csc dot fi>, FX Coudert <fxcoudert at gmail dot com>, Warren Turkal <wt at atmos dot colostate dot edu>, fortran at gcc dot gnu dot org
Date: Mon, 30 Oct 2006 23:35:25 +0100
Subject: Re: Compressed MOD files?
References: <19c433eb0610300207v3a2afa8cx83ed675677ceadd5@mail.gmail.com> <200610301123.59282.wt@atmos.colostate.edu> <D3E845FA-FCC3-414C-84EC-859AB681F6AB@gmail.com> <Pine.LNX.4.63.0610302057220.3566@sepeli.csc.fi> <20061030210528.GA7761@troutmask.apl.washington.edu>

Steve,

Module B will be read twice, and hence, it would be decompressed twice. How much overhead is added by the decompression phase?

I have proposed, as a 4.3.0 project, to store a symtree for each module, when it is USED for the first time. Subsequent USEs would then take from this symtree. Maybe compression could be added at the same time? Alternatively, we could write modules in binary, as do the commercial compilers. Come to that, a more abreviated form would do the same; eg. why write INTEGER each time, when a type is expected - "I" would do.

Huummphh - I do like being able to read the .mod files.

Paul

References:
- Compressed MOD files?
  - From: François-Xavier Coudert
- Re: Compressed MOD files?
  - From: Warren Turkal
- Re: Compressed MOD files?
  - From: FX Coudert
- Re: Compressed MOD files?
  - From: Erik Edelmann
- Re: Compressed MOD files?
  - From: Steve Kargl

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]